---
title: Plan your strategy for migrating features
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

Upgrading from **Kentico Xperience 13 (KX13) to Xperience by Kentico (XbyK)** involves varying levels of effort depending on the features you choose to carry over.

Our [Upgrade overview](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/upgrade-from-kx13-overview.md) outlines the full process consisting of strategic planning, configuring the environment, running the data migration using the [Kentico Migration Tool](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool), and subsequent adjustments. As part of the [planning phase](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/upgrade-from-kx13-overview.md#plan-your-upgrade-approach), you should familiarize yourself with XbyK's feature set to understand what has changed and what new capabilities are available.

This guide breaks down the upgrade process **by feature**, offering insights into which areas are relatively straightforward and which ones may demand more time and resources.

It is NOT our goal to provide exact feature parity between KX13 and XbyK, but rather to offer more modern, faster, and more composable tools to deliver value to your customers. Therefore, in addition to notes about the effort, we highlight the benefits your customers gain after the upgrade.

So you can evaluate and plan your upgrade most effectively, we also provide information about features currently on the roadmap.

> **Tip:** If you prefer to learn hands-on, follow along with our [walkthrough](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-walkthrough.md), which showcases the upgrade of the Dancing Goat sample site from KX13 to XbyK.

> **Info:** We've released a [Kentico Xperience 13 library on Context7](https://context7.com/websites/kentico_13) that you can use to look up KX13 API references and code samples when planning your migration. Note that Context7 is a third-party service not maintained or supported by Kentico, so your experience may vary.

## Legend

We've categorized the amount of feature migration effort into three levels: low, medium, and high.
These levels offer a general benchmark to help you estimate the time and resources needed for each feature:

**LOW** - The Kentico Migration Tool (with proper configuration) transfers all data one-to-one into the target XbyK instance. Minor code adjustments may be required, such as generating new code files.

**MEDIUM** - The migration tool will transfer data, but a significant amount of developer work is needed for the feature to function as before. For example, implementing a new way of content retrieval or recreating/reconfiguring parts of the feature.

**HIGH** - Your team will need to rebuild this feature in XbyK, as it is either very different, not supported by the migration tool or not available out-of-the-box in XbyK. We recommend using one of our integrations or opting for a custom implementation. This level includes features that are on the roadmap.

## Content management

### Page Builder

**XbyK feature:** Page Builder

**LOW**

**MEDIUM**

By default, the Kentico migration tool ensures all Page Builder content and custom page templates transfer into the target instance without modifications.

We recommend taking advantage of the option to [configure conversion to the new Page Builder format](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#source-instance-api-discovery). See more details in the migration tool's [README file](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#page-builder-content).

The widget code needs minor adjustments and Custom page templates migrate as [Preset page templates](https://docs.kentico.com/documentation/business-users/website-content/page-templates.md#page-template-types).

> **Tip:** The new Page Builder in XbyK features bigger widget editing side-panel, providing easier and more intuitive experience to your customer's content editors.

To benefit from the new Page Builder, you can [transform widget properties](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-deep-dives/transform-widget-properties.md) to fit the new content model.

### Sites and pages

**XbyK feature:** Website channels and pages

**LOW**

The Kentico migration tool migrates each _Site_ on the KX13 source to a _Website channel_ in XbyK target instance. Page URLs may need adjustments. Page attachments migrate as content item assets into the Content hub. See more details in the migration tool's [README file](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#attachments).

### Structured content (Page types)

**XbyK feature:** Content hub (Content types)

**LOW**

**MEDIUM**

Content migrates into the target database. _Page types_ become _Page content types_ in XbyK. Developers need to adjust content retrieval implementation to utilize content query API and check/adjust content type fields.

With [additional configuration](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#reusable-field-schemas) of the Kentico Migration Tool, there's an option to address inheritance using the _reusable field schemas_ in specific scenarios.

In XbyK, we introduced the [Content hub](https://docs.kentico.com/documentation/business-users/content-hub.md), a central place to store reusable content that can be referenced across channels in your solution. As a future improvement, we recommend adjusting your content model, identifying reusable pieces of content, and storing them in the Content Hub, although this (currently manual) step is not mandatory for the target solution to run.

> **Tip:** With the Content hub in XbyK, editors no longer need to store reusable content in the website content tree, and developers don't have to customize the solution heavily to make content available across channels.
>
> As opposed to content trees, XbyK's Content hub offers a filter-based interface and a flat data structure, eliminating the need for custom tables. The [Content reuse locator](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md#track-usage-of-content-items) shows where structured content is reused. Editors can use [Content folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md#content-folders) to organize their data in the Content hub, or [Smart folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md#smart-folders) to dynamically deliver content from the Content hub to website channels.

By default the migration tool migrates all structured content into a website channel. It supports migrating some web page content types to reusable content types if [configured](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI#convert-pages-or-custom-tables-to-content-hub).

Using the migration tool's [custom class mappings](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/docs/customization/Class-Mappings.md#create-custom-class-mappings), you can change the structure of your migrated content model. You can [remodel your page types](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-deep-dives/remodel-page-types-as-reusable-field-schemas.md) to leverage [reusable field schemas](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md). These schemas help you transfer _inheritance_ into the _composition_ pattern preferred in Xperience. You can even [speed up remodeling](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-deep-dives/speed-up-remodeling-with-ai.md) your migration project using AI.

> **Tip:** To improve content governance, we recommend remodeling page types during migration into Xperience as _semantic content types_ that represent real-world concepts, such as an _article_, _product_, or _case study_, instead of generic _Text with image_. When the same attributes appears across many content types, use _reusable field schemas_ to keep data easier to maintain. You can also migrate data that don’t represent complete ideas on their own into content _fragments_, such as a _Product feature_. These fragments can be combined into larger structures or grouped into _content blocks_, like a set of FAQs. We recommend going through the [content modeling guide](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-guide.md) to learn more about these concepts.

### Digital asset management (Media libraries)

**XbyK feature:** Content hub

**LOW**

The migration tool will transfer [all media files as asset content items](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#media-libraries) to the Content hub in the target instance.

The [Media libraries](https://docs.kentico.com/documentation/business-users/media-libraries.md) feature in Xperience is no longer supported and will be removed in the September 2026 Refresh. Instead, [Content Hub](https://docs.kentico.com/documentation/business-users/content-hub.md) is the place to keep reusable content including files, which are stored as [content item assets](https://docs.kentico.com/documentation/business-users/content-hub/content-item-assets.md).

> **Tip:** Storing assets in the Content hub offers your customers a multitude of benefits, including:
>
> - [AIRA image processing features](https://docs.kentico.com/documentation/business-users/aira.md#image-processing),
> - [localization of content assets](https://docs.kentico.com/guides/digital-marketing/work-with-multilingual/multilingual-variant-of-content.md),
> - [workflow availability](https://docs.kentico.com/guides/digital-marketing/work-with-workflows/workflows.md) to improve approval processes,
> - customization through custom [content type fields](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-guide/store-files.md#define-content-types-for-media-assets),
> - [restricting access](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md#secure-content-items) behind sign-in.

### Multilingual and localization

**XbyK feature:** Languages

**MEDIUM**

The migration tool will map _Cultures_ from KX13 to _Languages_ in the target XbyK instance, and the localized content will also migrate.

XbyK does not natively allow editors to manage resource strings in the administration UI. Our recommendation is to use a dedicated content type to store the string and the label. Then create a content item for each value in the Content hub (e.g., in a dedicated folder) to allow editors to utilize the language versions of the content items.

If there's a requirement for editors to manipulate resource strings the way they used to in KX13, your team can consider the [Xperience community localization](https://github.com/nittin-cz/xperience-community-localization) module by Nittin. This module is not developed or supported by Kentico; use it as a reference and tailor the implementation to your project’s needs.

> **Tip:** Xperience by Kentico features automatic _Language fallbacks_ (covering cases when a translation in the requested language does not exist), which will help editors in poly-lingual situations (e.g., Netherlands-Belgium, DACH region, etc.).

### Workflows and versioning

**XbyK feature:** Workflows and versioning

**LOW**

**MEDIUM**

For pages, the migration tool transfers the _Published_, _Draft_ and _Archived_ states. See **Pages** section in the migration tool [GitHub documentation](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/docs/Supported-Data.md) for more details.

Your team needs to manually recreate any custom workflows from KX13 in the XbyK instance. In XbyK, you can replicate many linear workflows from KX13.
However, your team will need to implement custom behaviors of any custom steps from scratch, including some previously built-in steps (e.g., publishing to social media, translation workflows). See an [example in our documentation](https://docs.kentico.com/documentation/developers-and-admins/customization/handle-global-events/set-up-custom-workflow-notifications.md) about setting up custom workflow notifications.

> **Tip:** The editors in XbyK benefit from the new, basic workflow (New/Draft-Published-Archived) that is always automatically enforced.

### Content locking

**XbyK feature:** Roadmap

**HIGH** The [content locking](https://docs.kentico.com/13/configuring-xperience/configuring-the-environment-for-content-editors/configuring-and-using-page-versioning/content-locking.md) feature is evolving in Xperience by Kentico, and the [Kentico Migration Tool](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool) does not process content locking state. For this reason, we recommend avoiding migrating pages that are checked out. Such pages may not transfer correctly, leading to missing or inconsistent content after migration. To ensure a smooth, reliable migration, check all pages in before migrating to ensure their latest changes are fully saved and available.

If content locking is important for your workflow, watch the _Product roadmap_ for [future updates](https://roadmap.kentico.com/c/167-content-locking-for-pages-and-reusable-content-items).

## Customizations

### Custom modules and classes

**XbyK feature:** Custom modules and classes

**MEDIUM**

The migration tool transfers modules, classes, data, and some custom fields on system classes. Developers need to re-implement the UI. Read more in the migration tool's [README file](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#custom-modules-and-classes) or the [Modules and classes](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/docs/Supported-Data.md) section in the migration toolkit documentation on GitHub.

### Custom tables

**XbyK feature:** Custom modules

**MEDIUM**

The Kentico Migration Tool migrates all content from custom tables to custom module table in the target database. Your developer team will need to implement the necessary UI, with the option to leverage any UI components XbyK comes with out of the box.

See details in the migration tool's [README file](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#custom-tables) or the [Custom tables](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/docs/Supported-Data.md) section in the migration toolkit documentation on GitHub.

> **Tip:** To simplify your development work, you can use [KentiCopilot](https://docs.kentico.com/guides/development/kenticopilot.md) to accelerate the creation or migration of custom UI components. For a practical, step‑by‑step example you can follow when building your own custom module, see [Dream and Experiment: Building a Component Registry Dashboard with AI](https://community.kentico.com/blog/dream-and-experiment-building-a-component-registry-dashboard-with-ai).

### Settings

**XbyK feature:** Settings

**MEDIUM**

All [settings supported by XbyK](https://docs.kentico.com/documentation/developers-and-admins/configuration/settings.md) will migrate into the target instance.
To accommodate custom settings we recommend that your developers [implement a custom module](https://docs.kentico.com/guides/development/customizations-and-integrations/create-basic-module.md).

Any website-specific settings will also require a custom module. [This guide](https://docs.kentico.com/guides/development/customizations-and-integrations/add-channels-to-module.md) provides an example.

### Admin UI customization

**XbyK feature:** Admin UI components

**MEDIUM**

The Xperience by Kentico\* Admin UI\* is built with _React_, which means its interface is completely based on modern JavaScript components. The old KX13 technology stack is not compatible with the new one, so any _custom Admin UI components_ created in KX13, whether you extended existing controls or built your own, must be [reimplemented](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/admin-ui-customization-model-overview.md) in the new React‑based framework. This applies to _custom form components_, or _Page Builder_ and _Form Builder_ UI elements.

To make development easier, you can use [KentiCopilot](https://docs.kentico.com/guides/development/kenticopilot.md) to speed up creating or converting custom UI components. See a step-by-step example of building a custom module as a starting point for your own customizations [Dream and Experiment: Building a Component Registry Dashboard with AI](https://community.kentico.com/blog/dream-and-experiment-building-a-component-registry-dashboard-with-ai).

## Data protection

### Consents and consent agreements

**XbyK feature:** Consents and consent agreements

**LOW**

Consents and agreements migrate into the target instance. We recommend verifying the result. Depending on your implementation, your team may need to perform minor adjustments, e.g., in the presentation layer.

> **Tip:** In XbyK marketers can easily see all contact’s consent agreements in the contact profile out-of-the-box. They are no longer required to have the permission to the Data protection application.

## Activities and Digital Marketing

### Contact management

**XbyK feature:** Contact management

**LOW**

The migration tool transfers contacts seamlessly to the target instance. If you are using custom contact fields, your development team will have to make minor adjustments.

### Contact groups

**XbyK feature:** Contact groups

**MEDIUM**

**HIGH**

While Contact groups do exist in XbyK, they work differently than they used to in the KX13 implementation. They are not supported by the Kentico migration tool at this time. After migrating contacts, your team will have to reconstruct the contact groups in the XbyK instance. XbyK supports dynamic condition-based groups.

> **Tip:** We improved the UI of the condition builder for contact groups in XbyK to provide marketers with more intuitive tools for segmentation.

### Activity tracking

**XbyK feature:** Activities

**LOW**

The migration tool transfers custom activities into the target XbyK instance. Depending on your implementation, your team may need to perform minor adjustments, e.g., in the presentation layer.

### Marketing automation

**XbyK feature:** Marketing automation

**HIGH**

Xperience by Kentico supports the most common automation scenarios. The [automation feature](https://docs.kentico.com/documentation/business-users/digital-marketing/automation.md) is available with the Xperience by Kentico Advanced license. However the automation processes have to be set up from scratch when upgrading from KX13 to XbyK.

### Content personalization

**XbyK feature:** Content personalization

**HIGH**

Content personalization does not migrate and your team will need to reimplement it in the target XbyK version. See an example of [personalization utilizing Contact groups](https://docs.kentico.com/guides/development/advanced-content/work-with-reusable-field-schemas.md#add-content-personalization) in XbyK.

> **Tip:** In Xperience by Kentico, marketers can create different content variants in the Content hub, which they can reuse across channels. They can then display these variants dynamically, e.g., through personalized widget or email content.
>
> Additionally, the editors have the ability to preview personalized pages.

### Email marketing

**XbyK feature:** Email marketing

**HIGH**

Email feeds in KX13 are similar to [Email channels](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-channel-management.md) in XbyK.

At this time, the Kentico migration tool will not automatically transfer this data. You can migrate form auto-responders to XbyK manually by copying your HTML code and content into Email templates and Emails. See available email marketing features in [our documentation](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md).

[Email Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/email-builder.md) is fully supported in Xperience by Kentico. However, email components, like widgets and templates, from KX13 will need manual code adjustments, as the XbyK Email Builder uses a different format.

A/B testing for emails is not available in XbyK out-of-the-box at the moment. We recommend that you follow [our roadmap](https://roadmap.kentico.com/tabs/4-planned) for updates.

> **Tip:** XbyK Email Builder allows developers to create and manage templates and other components in the application code without the need to sign in to the administration interface. This provides a better debugging experience and makes it easier to manage components with source control.
>
> For email content in XbyK, marketers can use AIRA to generate data from existing content in Content hub, URLs, or custom prompts.

### Search

**XbyK feature:** Integrations

**MEDIUM**

To implement search in XbyK, we offer three existing integrations you can take advantage of: [Lucene](https://github.com/Kentico/xperience-by-kentico-lucene), [Azure AI Search](https://github.com/Kentico/xperience-by-kentico-azure-ai-search), and [Algolia](https://github.com/Kentico/xperience-by-kentico-algolia)

> **Info:** Despite the search functionality not being present natively in XbyK, the migration effort is ranked as **MEDIUM** because implementing it with the listed integrations is very straightforward and fast, especially for smaller projects.

### Forms

**XbyK feature:** Forms

**LOW**

**MEDIUM**

Forms from KX13 will migrate into the target XbyK instance. All out-of-the-box KX13 form controls will map to XbyK controls [as outlined here](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#migration-details-for-specific-object-types). However, we recommend taking a closer look and adjusting some form components as needed. Your team will have to reimplement all custom controls.

### Personas, and lead scoring

**XbyK feature:** Roadmap

**HIGH**

At the moment, these features are not available in XbyK. For deterministic segmentation, you can utilize [contact groups](#contact-groups). If your team requires advanced segmentation or personas and lead scoring as you knew them from KX13, your developer team needs to build a custom implementation. If this is not an immediate need, we recommend waiting and following our XbyK [roadmap](https://roadmap.kentico.com/tabs/6-next-refreshes).

Upcoming enhancements to marketing automation – including custom [triggers](https://roadmap.kentico.com/c/387-marketing-automation-extensibility-custom-triggers), [conditions](https://roadmap.kentico.com/c/388-marketing-automation-extensibility-custom-conditions), and [actions](https://roadmap.kentico.com/c/386-marketing-automation-extensibility-custom-actions) – will unlock a significantly broader range of scenarios, covering many lead scoring and persona use cases that aren't fully achievable today. While some highly specific requirements may still need a custom implementation, these building blocks provide a strong foundation for advanced segmentation workflows.

### Social marketing

**XbyK feature:** Roadmap

**HIGH**

At the moment, this feature is not available in XbyK, but it is one of our goals to build a way for customers to use our API to feed data from Xperience into any channel - including social media. If this is not an immediate need, we recommend to wait and follow [our roadmap](https://roadmap.kentico.com/c/225-custom-channel-types?\&utm_medium=social\&utm_source=starter_share).

## Digital commerce

**XbyK feature:** Digital commerce, integrations

**MEDIUM**

**HIGH**

[Commerce](https://www.kentico.com/discover/blog/experience-first-commerce) is available in XbyK, and has been developed entirely from scratch. Because of this fresh start, the [commerce features](https://docs.kentico.com/documentation/business-users/manage-commerce-stores.md) and entities in XbyK don’t have a direct one-to-one match with the KX13 [E-commerce module](https://docs.kentico.com/13/e-commerce-features.md). You can [overview the commerce features](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/upgrade-commerce-features-overview.md) in Xperience and define strategy for upgrading your existing commerce features and workflows.

As of **January 2026**, the [Kentico Migration Tool](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool) now supports migrating commerce entities (customers, orders) from Kentico Xperience 13. While the migration tool handles data transfer, you'll still need to [set up commerce functionality](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/commerce-config.md) in XbyK, [model your product catalog](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/model-product-catalog.md), and [tailor the solution](https://docs.kentico.com/guides/development/commerce.md) according to your project's requirements.

If you're missing a specific commerce capability, check the [product roadmap](https://roadmap.kentico.com/tabs/6-next-refreshes) to see what's planned. If you don't find what you're looking for, submit the idea to help us prioritize future development.

Alternatively, your development team can take advantage of our existing [Shopify integration](https://github.com/Kentico/xperience-by-kentico-shopify).

## Analytics

### A/B testing and Web analytics

**XbyK feature:** Integrations

**HIGH**

Your development team can implement these features through our [tag manager integration](https://github.com/Kentico/xperience-by-kentico-tag-manager). For A/B testing we recommend the integration with [VWO](https://vwo.com/). For web analytics you can use Google Analytics, Google Tag Manager or Microsoft Clarity. Additionally, we plan to leverage AI to help optimize and automate several tasks, including A/B testing. Follow [our roadmap](https://roadmap.kentico.com/c/325-ai-experiments-and-optimization) for details.

### Reporting

**XbyK feature:** Customer journey, Custom module

**HIGH**

To analyze how customers interact across channels and touchpoints, marketers can set up [customer journeys](https://docs.kentico.com/guides/customer-journeys.md), leveraging standard and custom contact activities. To perform advanced analytics across different aspects of the Xperience application, your development team can implement reporting using XbyK Custom modules. The feature is not present out of the box.

Alternatively, you may want to consider tools outside of XbyK, that you can fill with data using SQL queries, such as the [Microsoft Report Builder](https://learn.microsoft.com/en-us/sql/reporting-services/install-windows/install-report-builder?view=sql-server-ver16) for SQL server.

## Configuration

### Settings

**XbyK feature:** Settings, configuration keys

**LOW** Many of the settings you configured for features in older versions [also exist in Xperience by Kentico](https://docs.kentico.com/documentation/developers-and-admins/configuration/settings.md). The Kentico migration tool [automatically transfers](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/docs/Supported-Data.md#setting-values) the values of these settings. The migration excludes site-specific settings that do not have a corresponding website channel-specific alternative in Xperience by Kentico.

> **Note:** The migration does not transfer settings configured in application files, like **web.config** and **appsettings.json**. Manually move these setting values to the corresponding settings in the Xperience by Kentico admin UI where possible, and set applicable [configuration keys](https://docs.kentico.com/documentation/developers-and-admins/configuration/reference-configuration-keys.md) when no admin setting is available.
>
> In the case of `CMSForbiddenURLValues`, we specifically recommend migrating its value to the `CMSForbiddenURLCharacters` setting in Xperience, to avoid issues with migrated URLs during content sync.

### User management

**XbyK feature:** Users, Memberships

**LOW**

**MEDIUM**

The Kentico migration tool will seamlessly migrate all users with _Privilege level “Editor”_ and above as **Users** in XbyK.
All external users (visitors, customers, members) migrate as **Members**. External sign-in information (e.g., Facebook, Google) will NOT migrate. See the [README file](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#members) of the migration tool for more details. Depending on your implementation, your team may need to perform some adjustments to the code after the data migration. We cover this in more detail in our [Adjust your code and adapt your project](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/adjust-your-code-and-adapt.md) guide.

### Role management

**XbyK feature:** Role management

**LOW**

**MEDIUM**

The Kentico Migration Tool transfers roles that have at least one user with _Privilege level “Editor”_ and above.
Note that XbyK uses a different permission model, therefore your team has to reconfigure role permissions or any UI personalization settings.

Editors can organize members into [member roles](https://docs.kentico.com/documentation/business-users/members.md#member-roles) and use these roles to restrict access to pages or content items.

> **Tip:** In XbyK, we have made significant UX improvements so administrators can more easily define which parts of the admin UI a user can access, and what operations they are authorized to do.

### Categories

**XbyK feature:** Taxonomies and reusable field schemas

**LOW**

All _Categories_ from KX13 instance will migrate as _Taxonomies_ in XbyK. Note that XbyK uses different approach to categorization – see details in the migration tool's [README file](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#categories).

> **Tip:** Taxonomy in XbyK is no longer tied to the Document, it’s an independent object and editors can translate the tags and categories into different languages.

### Multi-factor authentication

**XbyK feature:** Multi-factor authentication

**MEDIUM**

Xperience currently supports [Multi-factor authentication](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/user-management.md#multi-factor-authentication) in the administration interface. Alternatively, your team can build a custom implementation or integration.

### Integration bus

**XbyK feature:** Roadmap

**HIGH**

At the moment this feature is not available out-of-the-box in XbyK. We recommend that you follow [our roadmap](https://roadmap.kentico.com/tabs/4-planned) for updates.

### Admin localization

**XbyK feature:** Admin UI localization

**LOW**

[Admin UI Localization](https://docs.kentico.com/documentation/developers-and-admins/customization/admin-ui-localization.md) is available out-of-the-box in Xperience by Kentico. XbyK uses different resource string keys than older Kentico versions, so new translations may be necessary. AI tools can help speed up this process.

### Content staging

**XbyK feature:** Content sync

**LOW**

[Content sync](https://docs.kentico.com/documentation/business-users/content-sync.md) is available out of the box in Xperience by Kentico. It replaces the [Content staging](https://docs.kentico.com/13/deploying-websites/content-staging.md) and brings in advanced features for synchronizing content. Compared to content staging that helped you bi-directionally transfer changes made to page and objects, Xperience [content sync](https://docs.kentico.com/documentation/developers-and-admins/configuration/content-sync-configuration.md) is one directional (test -> stage -> production) and focuses solely on content. Find more information of what [content is synchronized](https://docs.kentico.com/documentation/business-users/content-sync.md#supported-content) in the documentation.

## Now that you’ve got the big picture…

The goal of this article was to provide you with high-level information about KX13 to XbyK upgrade complexity from a feature perspective. We realize that the actual effort needed will vary from project to project. Let's continue to get a clearer picture of what an upgrade could look like in practice.

## What's next?

If you want a deeper technical understanding of how these features fit into the upgrade process from beginning to end—as outlined in the [Overview](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/upgrade-from-kx13-overview.md)—check out the next two guides: [Prep for the upgrade and transfer data](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/prep-for-upgrade-and-transfer-data.md) and [Adjust your code and adapt your project](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/adjust-your-code-and-adapt.md).

If you are interested in a concrete example of migrating a specific feature, let us know your feedback and stay tuned for future guides.