--- title: "Xperience by Kentico to Umbraco Migration | ClonePartner" description: "Xperience by Kentico to Umbraco: Headless content items map loosely; Umbraco content is page-centric. Engineer-led, zero downtime." source: Xperience by Kentico target: Umbraco canonical: "https://clonepartner.com/migrate/xperience-by-kentico-to-umbraco" --- # Xperience by Kentico → Umbraco migration Xperience by Kentico to Umbraco migration — content items, media, and taxonomies moved with content fidelity. ## Entity mappings - **Pages (Web Pages)** (Xperience by Kentico) → **Content** (Umbraco) - **Content Types (Page Types)** (Xperience by Kentico) → **Document Types** (Umbraco) - **Media Library Files** (Xperience by Kentico) → **Media** (Umbraco) - **Languages** (Xperience by Kentico) → **Languages** (Umbraco) - **Users** (Xperience by Kentico) → **Users** (Umbraco) - **Roles** (Xperience by Kentico) → **User Groups** (Umbraco) - **Content Items** (Xperience by Kentico) → **Content** (Umbraco) - **Media Libraries** (Xperience by Kentico) → **Media** (Umbraco) - **Content Item Language Variants** (Xperience by Kentico) → **Languages** (Umbraco) - **Taxonomies (Tag Groups)** (Xperience by Kentico) → **Data Types** (Umbraco) - **Taxonomy Tags** (Xperience by Kentico) → **Data Types** (Umbraco) - **Form Definitions** (Xperience by Kentico) → **Umbraco Forms (Third-Party Package)** (Umbraco) - **Form Submissions (Records)** (Xperience by Kentico) → **Umbraco Forms / Custom Document Type Records / External Database Table** (Umbraco) - **Workflows** (Xperience by Kentico) → **Umbraco Content Review / Custom Workflow Implementation** (Umbraco) - **Contacts** (Xperience by Kentico) → **Members** (Umbraco) ## Frequently asked questions ### What happens to Kentico Form Definitions and form submission records when they move to Umbraco? Umbraco has no native form builder in its core CMS, so Form Definitions target the licensed Umbraco Forms add-on (included with Umbraco Cloud or purchased separately); without that licence, forms must be rebuilt as custom Document Types or routed to a third-party tool such as HubSpot Forms. Submission records stored in Kentico's dynamically named BizForm tables (e.g., BizForm_ContactUs) have no REST endpoint, so migration requires direct database access and a custom SQL script to insert records into Umbraco Forms' UFRecords and UFRecordFields tables. Field type mappings are not one-to-one between platforms, so complex or custom Kentico field types need explicit transformation logic or they will be lost. Confirming whether Umbraco Forms is licensed on the target environment is the first step before scoping this part of the migration. ### Does ClonePartner need direct database access to Xperience by Kentico, or does it use the API? Both access methods are used depending on the entity type. The Xperience by Kentico Management API covers pages, content types, media, languages, users, and roles, but requires API keys scoped per object type and is subject to rate limiting and payload size limits. Contacts, form submission records, and custom module data have no public REST endpoints, so those objects require either direct database access or custom .NET code to extract. Umbraco Cloud deployments also restrict direct database and file system access on the target side, which affects how media binaries and Umbraco Forms records are written and must be discussed during the scoping call. ### What has to be reconfigured manually in Umbraco after the data has been imported? Several things require hands-on work after import. All content nodes imported via the Umbraco Management API arrive in Draft state and must be published individually or in bulk. Umbraco GUIDs (UDIs) must be preserved during import or internal links and references will break. Linked content references that existed in Xperience by Kentico must be resolved and re-mapped to the corresponding Umbraco node GUIDs, and any property editor aliases that differ between platforms will silently drop data if not reconciled beforehand. In multisite setups, domain and hostname bindings also need to be reconfigured in the Umbraco backoffice after the content lands. ### Will user passwords come across, and does the Umbraco Management API version matter? Passwords cannot be migrated from either platform: Xperience by Kentico does not expose password hashes for export, and Umbraco does not accept them for import due to hashing. All migrated users will need to reset their passwords after cutover, which should be communicated to your team before go-live. On the Umbraco side, the Management API v1 is only available in Umbraco 14 and later; if your target environment is on an older version, legacy endpoints must be used instead, so confirming the Umbraco version is a prerequisite before migration work begins. ### 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 Umbraco, 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 Umbraco before the full migration is committed. ### Can we see a sample of our Xperience by Kentico data migrated to Umbraco 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 Umbraco 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 Umbraco. Where Umbraco 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 Umbraco, review sample records from it and propose how it can be represented, based on what Umbraco 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 Umbraco? 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 Umbraco will send messages about the migrated data: we import with notifications switched off wherever Umbraco 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 Umbraco can't take in through an API? In many cases, yes. Where something can't be written through an API, we recreate it through Umbraco'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 Umbraco 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 Umbraco 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. ### Can you change our URL structure when we move from Xperience by Kentico to Umbraco, such as moving a blog or docs from a subdomain onto our main domain? Yes, where Umbraco and your site's front end support the structure you want. Each page is created in Umbraco 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 Umbraco 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 Umbraco? 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 Umbraco. 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 Umbraco? 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 Umbraco, 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 → Umbraco migration.