---
title: "Contentful to Xperience by Kentico Migration | ClonePartner"
description: "Contentful to Xperience by Kentico: Spaces → Channels (Websites): Spaces are broader; map to closest channel concept. Engineer-led, zero downtime."
source: Contentful
target: Xperience by Kentico
canonical: "https://clonepartner.com/migrate/contentful-to-xperience-by-kentico"
---

# Contentful → Xperience by Kentico migration

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

## Entity mappings

- **Content Types** (Contentful) → **Content Types (Page Types)** (Xperience by Kentico)
- **Entries** (Contentful) → **Content Items** (Xperience by Kentico)
- **Assets** (Contentful) → **Media Library Files** (Xperience by Kentico)
- **Locales** (Contentful) → **Languages** (Xperience by Kentico)
- **Spaces** (Contentful) → **Channels (Websites)** (Xperience by Kentico)
- **Tags** (Contentful) → **Taxonomy Tags** (Xperience by Kentico)
- **Webhooks** (Contentful) → **Custom Module / Event Handler Configuration** (Xperience by Kentico)
- **Roles** (Contentful) → **Roles** (Xperience by Kentico)
- **Environment Aliases** (Contentful) → **Custom Module / Custom Table or Not Directly Available** (Xperience by Kentico)
- **Scheduled Actions** (Contentful) → **Workflows** (Xperience by Kentico)
- **Editor Interfaces** (Contentful) → **Content Type Field Configuration (UI Form Layout)** (Xperience by Kentico)
- **App Installations** (Contentful) → **Custom Module / Custom Table in Xperience by Kentico** (Xperience by Kentico)

## Frequently asked questions

### What happens to my Contentful webhooks when I migrate to Xperience by Kentico?

Contentful webhooks have no native equivalent in Xperience by Kentico, so they cannot be lifted and shifted. ClonePartner exports all webhook definitions (endpoints, triggers, headers, secrets) to JSON for documentation, then creates a Custom Module in Xperience to store the configuration records. Outbound HTTP calls must be re-implemented using Xperience Global Event Handlers in C# or routed through middleware such as Azure Logic Apps — this is a rebuild effort on your team's side, not a data migration.

### How do Contentful Tags migrate, and do I need to set anything up in Xperience by Kentico first?

Contentful Tags are flat labels; Xperience by Kentico requires them to sit inside named Taxonomy groups, so a direct import is not possible without preparation. Before migration, the target Taxonomy structure must be created in Xperience — either manually in the admin UI or via CI/CD serialization files — so ClonePartner has valid parent groups to map each tag into. Any tag that cannot be matched to an existing Taxonomy will stall unless a default group is agreed on during scoping.

### Will my content be live in Xperience by Kentico immediately after migration, or do I need to publish it again?

Xperience by Kentico defaults all imported content items to Draft state; published or archived status from Contentful is not preserved during import. After the data lands, your team must publish items through the Xperience admin UI or via Management API calls — ClonePartner flags this during handover so you can plan a publish workflow before cutover. For large content sets, building a bulk-publish script in C# ahead of launch day is worth considering.

### What happens to Contentful Environment Aliases during the migration?

Environment Aliases are a Contentful-specific DevOps concept with no counterpart in Xperience by Kentico; they are treated as infrastructure metadata, not migratable content. ClonePartner can preserve the alias definitions in a lightweight Custom Table in Xperience for audit or documentation purposes, but the functional equivalent — staged publishing and environment branching — must be re-implemented using Xperience's own CI/CD Continuous Integration module and separate DEV/STAGE/PROD database instances.

### Do Rich Text fields with embedded entries migrate safely, and is there anything that can break silently?

Rich Text fields that embed other Contentful entries must be migrated in dependency order: the embedded entries must exist in Xperience before the fields that reference them are written, otherwise the references break silently with no import error. ClonePartner resolves the dependency graph before writing records to avoid this. Separately, circular references between content types — where Type A embeds Type B and Type B embeds Type A — can cause import failures and are identified during scoping so the structure can be flattened or sequenced correctly.

### Does my Contentful version history or snapshot data come across to Xperience by Kentico?

No — only the current published state of each entry and asset can be migrated; Contentful snapshots and version history have no import path and are not carried over. If audit history matters for compliance, export and archive the snapshot data from Contentful before migration and store it externally, since it will not exist in Xperience after cutover. This is a hard platform limitation, not something ClonePartner can work around.

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