---
title: "Umbraco to Xperience by Kentico Migration | ClonePartner"
description: "Umbraco to Xperience by Kentico: Media Types → Media Libraries: Media types map loosely to library organization, not types. Engineer-led, zero downtime."
source: Umbraco
target: Xperience by Kentico
canonical: "https://clonepartner.com/migrate/umbraco-to-xperience-by-kentico"
---

# Umbraco → Xperience by Kentico migration

Umbraco to Xperience by Kentico migration — pages, media, and taxonomies moved with content fidelity.

## Entity mappings

- **Content** (Umbraco) → **Pages (Web Pages)** (Xperience by Kentico)
- **Media** (Umbraco) → **Media Library Files** (Xperience by Kentico)
- **Document Types** (Umbraco) → **Content Types (Page Types)** (Xperience by Kentico)
- **Media Types** (Umbraco) → **Media Libraries** (Xperience by Kentico)
- **Data Types** (Umbraco) → **Custom Modules / Module Classes** (Xperience by Kentico)
- **Members** (Umbraco) → **MemberProfiles (Contact + Custom Member Module)** (Xperience by Kentico)
- **Member Types** (Umbraco) → **Contact Groups / Custom Member Data via Member Custom Fields** (Xperience by Kentico)
- **Languages** (Umbraco) → **Languages** (Xperience by Kentico)
- **Dictionary Items** (Umbraco) → **Content Items** (Xperience by Kentico)
- **Users** (Umbraco) → **Roles** (Xperience by Kentico)
- **User Groups** (Umbraco) → **Roles** (Xperience by Kentico)
- **Templates** (Umbraco) → **Email Channel Templates** (Xperience by Kentico)
- **Content Versions** (Umbraco) → **Workflows** (Xperience by Kentico)
- **Partial Views** (Umbraco) → **Page Templates / View Components / Custom Module Classes** (Xperience by Kentico)

## Frequently asked questions

### What happens to Umbraco Members during the migration to Xperience by Kentico?

Xperience by Kentico does not have a Members concept that maps directly to Umbraco's. Depending on how your site uses Members, we migrate them into one or more destinations: XbyK's ASP.NET Identity-based Member accounts for authenticated front-end users, native Contact records for CRM-style data, or a Custom Module Object for richer profile fields like membership tiers or loyalty data. Passwords cannot be migrated from either platform due to one-way hashing, so all members will need to reset their passwords after cutover.

### Do Umbraco Member Types survive the migration, or is that schema lost?

Umbraco Member Types are schema definitions, and Xperience by Kentico does not have an equivalent — all members share a single flat object. During migration, each unique property across all your Member Types is mapped to a custom field on the unified XbyK Member or Contact object, and if your types represent distinct segments or roles, the type distinction is preserved as a Member Role or Contact Group. No data values are lost, but the structural separation between types dissolves, so we recommend agreeing on the target schema before migration begins.

### Can Umbraco Nested Content and Block List editor data be migrated into Xperience by Kentico?

Umbraco stores Nested Content and Block List data as raw JSON inside content properties, so the values are present in the source but have no direct structural equivalent in XbyK's content model. We extract that JSON and map it to the closest available XbyK structure — typically Reusable Content Items or custom fields on a Content Type — but the target schema must be defined in XbyK before migration runs. Any Block List items whose inner types have not been mapped to an XbyK Content Type will not migrate, so a field mapping review is a required step in the scoping process.

### Which version of Umbraco do I need, and are there any API prerequisites before the migration can start?

The Umbraco Management API v1, which ClonePartner uses for structured content extraction, is only available in Umbraco 14 and later. Sites on Umbraco 13 or older require migration through legacy endpoints or direct database access, which we handle, but it must be confirmed at scoping. On the XbyK side, all writes go through the Management API using scoped API keys, and the target environment must be a provisioned, running Xperience by Kentico instance — XbyK shares no APIs or data formats with Kentico Xperience 13, so an existing KX13 environment cannot be used as the destination.

### What content or settings have to be manually rebuilt in Xperience by Kentico after the data lands?

Several things do not arrive as ready-to-use data. Partial Views are Razor files that must be ported into the XbyK codebase by a developer as ASP.NET Core Partial Views or View Components — no automated import path exists for view logic. All imported content items land in Draft state and must be explicitly published. Page templates are a code-first concern in XbyK and are not carried over from Umbraco. Umbraco's Examine/Lucene search indexes are not migrated and will rebuild automatically, and multisite domain and hostname bindings must be reconfigured in the XbyK admin after cutover.

### Will my Umbraco Forms submissions and form definitions be included in the migration?

Umbraco Forms data — both form definitions and submission records — sits outside the standard Content Delivery and Management APIs and requires either the separate Umbraco Forms API or direct database access to extract. On the XbyK side, form submission records have no REST endpoint and must be inserted via direct database access or the C# API, meaning this portion of the migration requires a custom scripting step. If your project includes Forms data, flag it at scoping so we can confirm access levels on both ends and include it in the project scope.

## 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 Umbraco → Xperience by Kentico migration.