KentiCopilot content audit and migration

✖
Copy to clipboard

The Kentico Migration Tool migrates a wide range of content and data from Kentico Xperience 13 (KX13) to Xperience by Kentico (XbyK). However, project requirements often vary. Mapping KX13 features to XbyK, and optionally remodeling content to support a more modern architecture, require significant analysis and development effort.

Thankfully, KentiCopilot includes many migration-related skills that help you rapidly implement extensions to transform your content according to your needs.

Before watching, we recommend familiarizing yourself with:

This page gives a practical overview of KentiCopilot-assisted migration from KX13 to XbyK. Watch the video for a real example, then use the sections below to understand the stages and find the GitHub documentation for detailed setup and execution.

This video showcases a migration of the Medio Clinic training site from Kentico Xperience 13. We used GitHub Copilot with the Claude Opus 4.6 language model.

Choosing a language model

Many KentiCopilot skills are designed for high-intelligence language models.

We recommend using models with strong reasoning capabilities for KentiCopilot migration skills, especially those related to migration planning and troubleshooting.

Install and configure the tools

By pointing your agentic coding assistant to the documentation for the KentiCopilot and Kentico Migration Tool repositories, you can quickly install and configure the necessary components to start your migration.

Just remember to structure your source and target projects alongside the migration tool in a single workspace, as described in the plugin documentation.

Create a migration plan

The first step when migrating with KentiCopilot is to audit your KX13 content and create a plan.

Your agent will analyze your existing content and suggest data transformations to help it work with XbyK features, along with recommendations for improving your content model.

If the migration requires any manual work before or after execution, such as creating objects in the Xperience admin UI, the migration plan will include instructions. In many cases, the Management MCP server allows your agentic coding assistant to implement these changes for you.

Back up your manual changes

If you manually add objects to the database before migration, we recommend running a continuous integration store and backing up the repository. This allows you to quickly restore objects with the same code names and GUIDs if you decide to start over with a fresh target database.

Otherwise, you may need to adjust GUIDs in the migration plan and/or code files before running another migration attempt against a fresh database.

Extend the migration tool

Once you have a migration plan, you can use KentiCopilot’s skills designed to extend the migration tool with the following components:

In minutes, KentiCopilot can write custom code that might otherwise take hours or days, tailored to fit your content into XbyK.

Execute, evaluate, and iterate

Once all extensions are in place, use the run and eval skills to run the migration and evaluate the results against the migration plan.

The agent will evaluate the migrated site to determine whether the data aligns with the plan established at the start of the process.

If anything does not migrate according to plan, it will troubleshoot issues, make adjustments, and let you know which skills you may need to rerun.

It may also use the migration tool documentation to implement other types of customization that are not covered by dedicated skills, such as pipeline behaviors.

Get started with KentiCopilot

You can find detailed instructions for using the migration functionality in the KentiCopilot repository.