---
title: "WordPress to Xperience by Kentico Migration | ClonePartner"
description: "WordPress to Xperience by Kentico: Categories → Taxonomy Tags: Map to tags within a dedicated Taxonomies group. Engineer-led, zero downtime."
source: WordPress
target: Xperience by Kentico
canonical: "https://clonepartner.com/migrate/wordpress-to-xperience-by-kentico"
---

# WordPress → Xperience by Kentico migration

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

## Entity mappings

- **Posts** (WordPress) → **Content Items** (Xperience by Kentico)
- **Pages** (WordPress) → **Pages (Web Pages)** (Xperience by Kentico)
- **Custom Post Types** (WordPress) → **Content Types (Page Types)** (Xperience by Kentico)
- **Media** (WordPress) → **Media Library Files** (Xperience by Kentico)
- **Categories** (WordPress) → **Taxonomy Tags** (Xperience by Kentico)
- **Tags** (WordPress) → **Taxonomy Tags** (Xperience by Kentico)
- **Custom Taxonomies** (WordPress) → **Taxonomies (Tag Groups)** (Xperience by Kentico)
- **Users** (WordPress) → **Roles** (Xperience by Kentico)
- **Post Meta** (WordPress) → **Custom Module Data (Object Instances)** (Xperience by Kentico)
- **Options / Site Settings** (WordPress) → **Custom Module Data (Object Instances)** (Xperience by Kentico)
- **Blocks (Reusable)** (WordPress) → **Content Items** (Xperience by Kentico)
- **Templates** (WordPress) → **Email Channel Templates** (Xperience by Kentico)
- **Menus** (WordPress) → **Web Page Items** (Xperience by Kentico)
- **WooCommerce Products** (WordPress) → **Custom Modules / Module Classes** (Xperience by Kentico)

## Frequently asked questions

### What happens to my WordPress categories during the migration?

WordPress categories do not have a direct equivalent in Xperience by Kentico, so they are migrated as Taxonomy Tags within a dedicated Taxonomies group rather than as a separate category hierarchy. Tags migrate directly as Taxonomy Tags, and custom taxonomies become Taxonomy Tag Groups. The structural distinction between categories and tags collapses into a flat tag model, so if your content relies on category hierarchy for navigation or filtering, that hierarchy logic will need to be reconfigured in Xperience by Kentico after the data lands.

### Will my ACF fields, WooCommerce products, or page builder data come across?

Plugin-specific data from tools like Advanced Custom Fields or WooCommerce requires a workaround on both sides. ACF field values sit in post meta, which must be explicitly registered with show_in_rest=true before our tooling can read them, and the destination fields must be modelled as custom content type fields or custom module data in Xperience by Kentico before import. WooCommerce products have no native commerce equivalent in Xperience by Kentico and are modelled as custom module classes. Page builder data stored as serialized PHP in post meta can corrupt silently during migration if not handled carefully, so we identify and flag all serialized fields during scoping.

### Do my WordPress navigation menus migrate to Xperience by Kentico?

WordPress menus have limited write support via the REST API, and Xperience by Kentico has no direct menu object — navigation is expressed through the web page tree structure instead. We use WXR XML export as the more reliable source for menu data, then rebuild the navigation as Web Page Items in the content tree. The visual menu configuration and any mega-menu or plugin-driven layout will need to be reconstructed manually in the Xperience by Kentico admin after the structural items are in place.

### What happens to WordPress user accounts and passwords?

WordPress passwords are hashed and cannot be exported or migrated via the REST API, and Xperience by Kentico independently prohibits importing password hashes, so all users must reset their passwords after migration. User roles are mapped to their Xperience by Kentico role equivalents, but individual user accounts are handled separately from the main content migration. We recommend preparing a post-migration communication to affected users before cutover so they are not surprised by the password reset requirement.

### Will my migrated content be live in Xperience by Kentico immediately after import?

No — content items imported into Xperience by Kentico default to Draft state and must be explicitly published before they are accessible on the live channel. This applies to every content item, including those migrated from WordPress posts and pages. We include a publish step in the migration runbook, but your team should verify that scheduled or embargo content is handled intentionally rather than published automatically during cutover.

### Is this migration the same as upgrading from Kentico Xperience 13 to Xperience by Kentico?

No, and the distinction matters: Xperience by Kentico is an entirely different product, not a version increment of Kentico Xperience 13. The APIs and data formats are not shared between the two, so there is no in-place upgrade path and existing application code does not transfer. ClonePartner moves your content and data from WordPress into Xperience by Kentico; the associated work of rebuilding the admin UI in React, converting widgets from WidgetController to ViewComponent, and re-implementing application logic is a separate development project that falls outside our 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 WordPress → Xperience by Kentico migration.