---
title: "Kontent.ai to Xperience by Kentico Migration | ClonePartner"
description: "Kontent.ai to Xperience by Kentico: Asset Folders → Media Libraries: Folders map loosely to Media Libraries; hierarchy may be lost. Engineer-led, zero downtime."
source: Kontent.ai
target: Xperience by Kentico
canonical: "https://clonepartner.com/migrate/kontent-ai-to-xperience-by-kentico"
---

# Kontent.ai → Xperience by Kentico migration

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

## Entity mappings

- **Content Items** (Kontent.ai) → **Content Items** (Xperience by Kentico)
- **Language Variants** (Kontent.ai) → **Content Item Language Variants** (Xperience by Kentico)
- **Content Types** (Kontent.ai) → **Content Types (Page Types)** (Xperience by Kentico)
- **Content Type Snippets** (Kontent.ai) → **Custom Modules / Module Classes** (Xperience by Kentico)
- **Taxonomies** (Kontent.ai) → **Taxonomies (Tag Groups)** (Xperience by Kentico)
- **Assets** (Kontent.ai) → **Media Library Files** (Xperience by Kentico)
- **Asset Folders** (Kontent.ai) → **Media Libraries** (Xperience by Kentico)
- **Languages** (Kontent.ai) → **Languages** (Xperience by Kentico)
- **Workflows** (Kontent.ai) → **Workflows** (Xperience by Kentico)
- **Roles** (Kontent.ai) → **Roles** (Xperience by Kentico)
- **Spaces** (Kontent.ai) → **Channels (Websites)** (Xperience by Kentico)
- **Collections** (Kontent.ai) → **Custom Module Class (custom table) or Content Type with relationship fields** (Xperience by Kentico)
- **Webhooks** (Kontent.ai) → **Custom Module / Event Handler Implementation** (Xperience by Kentico)
- **Users** (Kontent.ai) → **CMS_User / Member / Custom Contact Fields** (Xperience by Kentico)

## Frequently asked questions

### Which Kontent.ai entities don't have a direct equivalent in Xperience by Kentico?

Seven of the fourteen entities we migrate require workarounds rather than direct mapping: Content Type Snippets, Asset Folders, Spaces, Collections, Webhooks, Users, and Content Types (some of which map to Page Types rather than reusable content). For each, we apply a documented structural mapping — for example, Snippets become Custom Module Classes with fields merged manually, and Asset Folders map to Media Libraries with hierarchy potentially flattened. Your team should review these mappings before cutover so the XbyK content model reflects your intended architecture, since some decisions (like how Collections are represented) affect how editors find and filter content after launch.

### What happens to my Kontent.ai Collections when the data moves to Xperience by Kentico?

Xperience by Kentico has no native Collections object, so we map each item's collection metadata during migration to one of several XbyK constructs depending on your use case: separate Channels if Collections represent distinct sites or brands, a Taxonomy tag group if they are used for filtering, or a custom module table with a foreign-key field on each content type if you need to preserve the grouping relationship explicitly. We read collection membership from the Kontent.ai Management API and write the mapped value to XbyK via its Content Management API or direct database seeding. You should decide which approach fits your content model before migration begins, because changing the structure afterward requires a schema change in XbyK.

### Can my Kontent.ai roles and permissions be imported into Xperience by Kentico automatically?

No — neither platform supports programmatic role import for this path. Kontent.ai roles cannot be exported and re-imported via the Management API, and Xperience by Kentico's permission model is structured differently, so role names alone do not translate to equivalent access rules. We document every role and its Kontent.ai permissions during the migration, but your administrators must manually recreate and assign roles in the XbyK admin after the data lands. User passwords also cannot be migrated; all users will need to reset their passwords on first login to Xperience by Kentico.

### What do I need to do with content items after ClonePartner loads them into Xperience by Kentico?

Content items imported into Xperience by Kentico default to Draft state regardless of their published status in Kontent.ai, so your team must publish items through the XbyK admin or Management API after migration. Linked content references — such as related items or linked modular content — are resolved and re-mapped during our migration process, but you should verify relational integrity using the field-level and referential integrity checks included in our validation stage. Workflow step states must also be manually transitioned if your content needs to sit at a specific workflow stage other than Draft.

### How are Kontent.ai Webhooks handled — do they move over to Xperience by Kentico?

There is no direct import path for Kontent.ai Webhooks into Xperience by Kentico because XbyK has no native webhook registry UI. We export all webhook endpoint URLs, trigger events, and secret keys from the Kontent.ai Management API and deliver them as structured documentation. The equivalent functionality in XbyK is implemented through custom C# Global Event Handlers registered in a custom module class — this is a code artifact your development team must build as part of the XbyK implementation, not something ClonePartner migrates as data.

### Does Xperience by Kentico share any APIs or data formats with Kentico Xperience 13, and does that affect this migration?

Xperience by Kentico is a completely separate product from Kentico Xperience 13 and shares neither APIs nor data formats with it. This migration runs entirely between the Kontent.ai Management API on the source side and the Xperience by Kentico Content Management API (plus direct database access via .NET for entities like Contacts and custom modules) on the destination side. Any custom admin UI, widgets, or application code from Kontent.ai-connected applications must be rebuilt for XbyK's React-based admin and ViewComponent architecture — that rebuild is outside the scope of what ClonePartner does; we move the content and structural data only.

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