migrate-run

Executes Kentico Migration Tool CLI to migrate KX13 content to XbyK.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you execute a Kentico Migration Tool content migration from KX13 to Xperience by Kentico (XbyK) and reliably capture results so you can diagnose and fix failures instead of guessing.

Core Features & Use Cases

  • One combined CLI execution: Builds a single dotnet run -- migrate ... command from the migration plan’s Execution Plan section, ensuring dependency ordering is handled internally by the tool.
  • Pre-flight validation and guardrails: Verifies the CLI project, appsettings.json correctness, build health, NuGet version compatibility, and that required prerequisites (migration plan, appsettings, compiled extensions) are ready before migration starts.
  • Deterministic logging + re-run strategy: Always captures stdout/stderr to the migration protocol directory, supports re-runs with --bypass-dependency-check, and triggers post-run SQL validation to detect missing or orphaned migrated content.

Quick Start

Use migrate-run to run your prepared KX13-to-XbyK migration plan via the migration tool CLI, producing a protocol log and running post-migration SQL validations.

Frequently Asked Questions about migrate-run

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

FAQPage Schema
How do I run a KX13 to Xperience by Kentico content migration using the CLI?

To run a KX13 to XbyK content migration, execute the Kentico Migration Tool CLI using a single dependency-aware command with combined flags for sites, page-types, pages, taxonomies, and assets. The tool internally handles dependency ordering when using the --nowait flag.

What prerequisites do I need to validate before running a Kentico content migration?

Before running a Kentico content migration, you need a validated appsettings.json file, a compiled migration extensions project, and a defined migration plan. Pre-flight checks verify CLI project health, NuGet version compatibility, and build status to ensure migration readiness.

How does logging work during a Kentico Migration Tool CLI execution?

Logging during Kentico Migration Tool CLI execution captures complete stdout and stderr console output, saving it to the MigrationProtocolPath directory. This deterministic logging ensures you can diagnose and fix migration failures instead of guessing what went wrong.

Can I rerun a failed Kentico content migration after fixing issues?

Yes, you can rerun a failed Kentico content migration after applying fixes. The workflow supports rerun strategies using the --bypass-dependency-check flag, allowing you to resume migration without re-evaluating previously completed dependency steps.

How do I validate migrated content in Xperience by Kentico after a CLI migration run?

Post-run validation of migrated content in XbyK is performed using sqlcmd validation queries. After the migration CLI execution completes, these SQL queries run automatically to detect any missing or orphaned migrated content in the target database.

Why is my KX13 content migration not working when I run separate commands for pages and taxonomies?

KX13 content migration may fail when run as separate commands because dependencies between data types are not resolved. You should construct a single combined CLI execution with all required flags, letting the Kentico Migration Tool handle dependency ordering internally.