migrate-content-items

Generate ContentItemDirectorBase C# code for KX13 to XbyK migration strategies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill generates the C# ContentItemDirectorBase extension code needed to implement per-page and per-linked-page migration behavior so your Kentico Xperience 13 content migrates correctly into Xperience by Kentico.

Core Features & Use Cases

  • Content item director code generation: Produces ready-to-use C# classes that override Direct() to apply child linking, template overrides, page-to-widget conversion, and page dropping for utility paths.
  • Linked page handling generation: Produces DirectLinkedNode() overrides to Materialize linked pages, Drop linked pages, or StoreReferenceInAncestor for controlled reference mapping.
  • Plan-driven and safeguard-aware behavior: Reads a migration plan to extract explicit “linked page handling” and “code extensions to implement,” and only queries the source database for linked pages when the plan is silent.

Quick Start

Use the migrate-content-items skill to generate ContentItemDirectorBase code for your KX13 → XbyK Migration.Tool.Extensions project using your migration plan file at /path/to/migration-plan.json.

Frequently Asked Questions about migrate-content-items

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

FAQPage Schema
How do I generate C# code for linked page materialization during Kentico migration?

Generate C# code for linked page materialization by creating ContentItemDirectorBase extension classes that override DirectLinkedNode(). This enforces explicit directives to either Materialize, Drop, or StoreReferenceInAncestor for controlled reference mapping during KX13 to XbyK migration.

What is the best way to handle page-to-widget conversion in a Kentico Xperience migration?

Page-to-widget conversion is handled by generating ContentItemDirectorBase extension code that overrides the Direct() method. This applies specific migration strategies to transform pages into widgets within your Migration.Tool.Extensions project.

How do I prevent silent duplication of linked pages when migrating to Xperience by Kentico?

Prevent silent duplication of linked pages by ensuring explicit directives are generated in your ContentItemDirectorBase extensions. The tool reads your migration plan for explicit handling instructions and only queries the source database when the plan is silent on the matter.

Does the content migration director code support conditional page dropping based on node paths?

Yes, the generated content migration director code supports conditional drop logic based on node paths and class identifiers. This allows you to automatically drop utility pages and apply template overrides during the Xperience by Kentico migration process.

How do I implement child page linking and template overrides for Kentico content items?

Implement child page linking and template overrides by generating ready-to-use C# classes that override the Direct() method. These extensions apply the required migration strategies directly within the Migration.Tool.Extensions project for your content items.

What dependencies do I need to compile migration tool extensions for Xperience by Kentico?

You need to compile the generated ContentItemDirectorBase extension code within the Migration.Tool.Extensions project. The generated C# code uses only ContentItemDirectorBase extension points and requires compilation verification to ensure correct per-page migration behavior.