--- title: "Xperience by Kentico to Webflow Migration | ClonePartner" description: "Xperience by Kentico to Webflow: Media Libraries → Asset Folders: Libraries map to folders but structure may differ. Engineer-led, zero downtime." source: Xperience by Kentico target: Webflow canonical: "https://clonepartner.com/migrate/xperience-by-kentico-to-webflow" --- # Xperience by Kentico → Webflow migration Xperience by Kentico to Webflow migration — content items, media, and taxonomies moved with content fidelity. ## Entity mappings - **Pages (Web Pages)** (Xperience by Kentico) → **Collection Items** (Webflow) - **Content Types (Page Types)** (Xperience by Kentico) → **Collections** (Webflow) - **Content Items** (Xperience by Kentico) → **Collection Items** (Webflow) - **Media Library Files** (Xperience by Kentico) → **Assets** (Webflow) - **Media Libraries** (Xperience by Kentico) → **Asset Folders** (Webflow) - **Users** (Xperience by Kentico) → **Members** (Webflow) - **Roles** (Xperience by Kentico) → **Access Groups** (Webflow) - **Taxonomies (Tag Groups)** (Xperience by Kentico) → **Collections** (Webflow) - **Taxonomy Tags** (Xperience by Kentico) → **Collection Items** (Webflow) - **Form Definitions** (Xperience by Kentico) → **Third-Party Form Tool + Webflow Embed / CMS Collection** (Webflow) - **Form Submissions (Records)** (Xperience by Kentico) → **Webflow CMS Collection Items (Custom Collection) or External Storage** (Webflow) - **Channels (Websites)** (Xperience by Kentico) → **NotAvailable (Architectural Concept — No Direct Equivalent)** (Webflow) - **Workflows** (Xperience by Kentico) → **NotAvailable (Native Equivalent)** (Webflow) ## Frequently asked questions ### Which Xperience by Kentico objects migrate cleanly to Webflow and which ones don't? Pages, content items, content types, media library files, and users all have direct equivalents in Webflow as collection items, collections, assets, and members respectively. Taxonomies, roles, form definitions, form submissions, workflows, and channels have no native Webflow equivalent and require workarounds, meaning those objects either land as repurposed CMS collections, get moved to third-party tools, or must be manually reconfigured. Of the 13 entity types ClonePartner handles for this pair, 8 are workaround or unavailable mappings, so scoping which of those objects your site depends on is the first step before migration starts. ### What happens to my Kentico form definitions and submission records when moving to Webflow? Webflow has no native form definition object, so Kentico form schemas (including field lists, validation rules, and submission mappings stored in CMS_Form and CMS_FormField) cannot be imported into Webflow directly. ClonePartner exports those definitions and historical submission records from Kentico via direct database access or the C# API (there is no REST endpoint for either), then routes them to a third-party form platform such as Typeform, Jotform, or HubSpot Forms for the live forms, and to an external store or a custom Webflow CMS collection for historical submission data. Webflow's built-in form element supports only statically-defined fields and does not store submissions in an accessible CMS, so any historical records preserved in a Webflow collection will be passive data, not functional form storage. ### Can ClonePartner migrate my Xperience by Kentico workflows to Webflow? Webflow has no content approval or workflow system, so workflow logic (approval steps, state transitions, and permissions defined in Xperience by Kentico) cannot be imported into Webflow in any executable form. ClonePartner can extract workflow state metadata (current step, status, approver) from Kentico and store it as static custom fields on the corresponding Webflow CMS collection items, which preserves a record of where each piece of content stood at cutover. The approval logic itself must be re-architected outside Webflow, typically using Webflow Webhooks connected to a tool like Zapier, Make, or Slack; that re-implementation is outside ClonePartner's scope. ### Does it matter that Xperience by Kentico is a different product from Kentico Xperience 13? Yes, Xperience by Kentico is a ground-up rewrite and shares neither the API format nor the database schema with Kentico Xperience 13 or earlier Kentico CMS versions. ClonePartner's migration scripts for this pair are written against the Xperience by Kentico Management API and CI/CD serialization layer, and will not work against an Xperience 13 or KX12 source without a separate engagement. If you are still on an older Kentico version and have not yet moved to Xperience by Kentico, let us know on the scoping call so we can route you to the correct migration path. ### Do I need professional help for this migration? Yes. Professional help ensures proper field mapping and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss. ### Does ClonePartner provide guidance before committing? Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything. ### Do you use an off-the-shelf tool to migrate from Xperience by Kentico to Webflow, or is this built for our data? It is built for your data. Each migration is a set of custom scripts written for your data model, not a generic import tool. That is also why we start with a sample migration: you see your own records in Webflow before the full migration is committed. ### Can we see a sample of our Xperience by Kentico data migrated to Webflow before the full migration runs? Yes. We run a sample migration on your own data first, so you can review how your records look in Webflow before the full migration goes ahead. We run validation scripts to confirm the record counts match your source, and you check the sample against your source records; if a field is missing or mapped wrong, or anything else needs adjusting, we fix it in the migration scripts and re-run the sample as many times as you need. The full migration only runs after you've approved the sample. On projects delivered in phases, each phase gets its own sample migration for you to approve. ### Will original ownership, authorship and created dates be preserved? Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in Webflow. Where Webflow cannot store one of them natively, it is kept as embedded metadata on the migrated record. ### If the new system can't natively support an old record type, what are my options? We handle it case by case. While mapping your data, we identify every record type without a direct counterpart in Webflow, review sample records from it and propose how it can be represented, based on what Webflow supports: map it to the closest native object, create a custom field or object, fold it into the parent record as text or a note, attach it as a file, or keep it in a read-only archive. You choose the approach, we write the migration scripts to place the data there, so it comes across in the form you choose instead of being left behind, and you see how it looks in a sample migration before we run the full set. ### We've built custom modules and integrations on Xperience by Kentico. Can you migrate their content to Webflow? We migrate the content and data your custom modules hold, as long as it can be read from Xperience by Kentico programmatically. Every migration we run is written as custom code for that project rather than pushed through an off-the-shelf tool, so unusual module data is not a blocker. During scoping we review each custom module and integration with you and agree how it will be handled before any work is committed. ### Will the migration set off automations or send emails or notifications to customers, our team or anyone else? No. Before the sample or full migration starts, we confirm with you that nothing in Webflow will send messages about the migrated data: we import with notifications switched off wherever Webflow allows it, and either pause any automation that could send them for the migration window or give it a condition, such as a suppression tag, that skips migrated records, which lets your live automations keep running for new records. We only proceed once you have confirmed it. If you want anyone told about the move, that message is sent separately, once the migrated data has been checked. ### Can you migrate data that Webflow can't take in through an API? In many cases, yes. Where something can't be written through an API, we recreate it through Webflow's user interface where the interface allows it, and where that work is repetitive we script and automate it. We tell you up front which items are handled this way, because recreating them through the interface can add time to the schedule. ### What happens if Webflow requires fields our Xperience by Kentico data doesn't have? We check the destination for required fields your source data cannot fill and bring each one to you before those records are migrated. Together we agree how each one is handled, such as a mapping from an existing field, a default value, or, where Webflow lets that field be made optional, setting it to not required for the migration so you can make it required again once the migration is complete. The migration then runs with that rule applied, so no records are rejected or left behind. ### How will we tell migrated records apart from the ones already in Webflow? We can mark every migrated record in Webflow, for example with a custom checkbox field such as "Migrated from Xperience by Kentico", so your team can tell migrated data apart from records created there. We agree the marker with you during scoping so it fits how your team uses Webflow. ### Can you change our URL structure when we move from Xperience by Kentico to Webflow, such as moving a blog or docs from a subdomain onto our main domain? Yes, where Webflow and your site's front end support the structure you want. Each page is created in Webflow by the migration, so it can be given its new address, for example a blog moved from a subdomain to a path on your main domain, and you get a map of every old URL to its new one so redirects can be set up from the old addresses wherever they are served. ### How long does the Xperience by Kentico to Webflow migration take? Most migrations complete within 1–5 business days, depending on data volume and complexity; very large migrations, such as several hundred thousand records, take longer. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours. ### Will there be downtime when migrating from Xperience by Kentico to Webflow? No. Our migration process is designed for zero downtime. Xperience by Kentico stays fully operational throughout: the bulk migration runs in the background and the cutover is fast, so there is no disruption to your live business operations. ### Can we whitelist a single IP instead of opening our network to your migration tool? Yes. All migration traffic runs through a centralized system using one fixed IP, which your IT team can whitelist instead of opening broader network access. ### Is migration pricing a flat fee, or does it scale with data volume? It's a flat fee with no hidden costs. The price we agree with you for your scope is the price you pay, and small variances in the final volume, a bit more or less, are included. ### How do I validate that everything migrated correctly? Every client receives a Migration Validation Report with comprehensive metrics including record-count comparison, attachment integrity verification via checksum, and full audit logs of the migration run, showing every record created, skipped or failed. If any item didn't come across, the report names each one, the specific reason, and how to bring it across if you want it there. We also offer unlimited sample migrations, so you can check your data before the full migration runs. ### What support do you provide after the migration goes live? At ClonePartner, we consider ourselves your partners in this journey. We take full accountability for your migration's success. Once your migration goes live, we provide 30 days of comprehensive post-migration support as standard, and longer support, such as 60 or 90 days, can be agreed for your project. During this period, we help with anything related to your migrated data, so your migration is a complete success. ### Will we get a migration report and a mapping sheet linking old record IDs to new ones? Yes. We provide a comprehensive migration report along with an ID-mapping sheet that links each old Xperience by Kentico record ID to its new ID in Webflow. This ensures full traceability, simplifies post-migration verification, and helps your team validate that records have been migrated accurately. ### After migration, do I contact ClonePartner or the platform's own support if something looks wrong? ClonePartner is the contact for anything about the migrated data itself. Questions about the platform itself, such as how its features and settings work, go to the platform's own support or to whoever administers it for you. ### Will our existing Xperience by Kentico page URLs and links keep working after we move to Webflow? They can, through redirects and link rewriting. Links between your own pages are updated to point at their new URLs as part of the migration, and the files and images your pages use are re-hosted on Webflow, wherever it can host them, with their links rewritten. For every old URL we give you a map to its new address, so redirects can be set up where your site is served and old bookmarks, search results and external links open the right page. ## Get a fixed-price quote [Talk to an engineer](https://clonepartner.com/talk-to-us?duration=30&utm_source=xtoy&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click) about your Xperience by Kentico → Webflow migration.