migrate-plan

Create a structured Kentico Xperience 13 to Xperience by Kentico migration plan.

14|7|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill migrate-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-plan
Source: https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kx13-content-migration/skills/migrate-plan
Command: npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill migrate-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It removes guesswork from Kentico Xperience 13 content migrations by producing a clear, structured migration plan tailored to the user’s source content model and goals.

Core Features & Use Cases

  • Source-to-target planning: Turns source content model inputs (file paths or descriptions) into a Migration Overview and a Migration Detail document.
  • Deep mapping guidance: Guides content type mapping, field mapping, taxonomy planning, widget transformations, and page relationship handling.
  • Actionable execution strategy: Produces an execution summary with the appropriate migrate CLI parameters and operational notes for iterative runs.

Quick Start

Use the migrate-plan skill to create migration-overview.md and migration-detail.md for a KX13→XbyK migration when you provide the source and (optionally) target content model descriptions or paths.

Frequently Asked Questions about migrate-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a Kentico Xperience 13 to Xperience by Kentico content migration?

To plan a KX13 to XbyK content migration, generate a structured plan mapping source page types and content models to the new target system. This creates a concise overview and an AI-consumable detail document covering field mapping and widget transformations.

What is the best way to map content types and widgets when migrating to Xperience by Kentico?

The best way to map content types and widgets during a KX13 migration is to analyze source page types with ClassID inheritance and CMS_Relationship document relationships. This provides deep mapping guidance for taxonomy planning and widget transformations.

How do I prepare my source content model for a KX13 migration plan?

Prepare your source content model for a KX13 migration plan by providing file paths or free-text descriptions of your content structure. The system reads shared migration references to analyze source page types and select appropriate migration approach categories.

Can I generate an executable CLI checklist for my Xperience by Kentico migration?

Yes, you can generate an executable CLI checklist for your Xperience by Kentico migration. The plan produces an execution summary with appropriate migrate CLI parameters and operational notes for iterative runs.

How are linked pages and page relationships handled during a KX13 to XbyK migration?

Linked pages and page relationships are handled during a KX13 to XbyK migration by auditing CMS_Relationship document relationships alongside ClassID inheritance. The migration plan includes specific sections for linked page auditing and page relationship handling.