migrate-global-code

Migrate global code from Kentico Xperience 13 to Xperience by Kentico.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating global code from Kentico Xperience 13 to Xperience by Kentico is complex because it must be reorganized and regenerated to match the XbyK project conventions, while preserving shared logic like localization, shared views, styles/scripts, and services.

Core Features & Use Cases

  • Project-structure setup: Guides you to compare the legacy KX13 and target XbyK folder layouts before generating migration output.
  • Docs-driven code generation: Uses Kentico Docs MCP to follow the upgrade walkthrough and generate the required code files using the kxp-codegen workflow.
  • Global code migration checklist: Covers copying shared concerns such as localization, shared views, styles/scripts, identifiers, and services registration, then verifies that the new project displays content and builds successfully.
  • Migration guardrails: Emphasizes not changing unrelated files/settings and includes troubleshooting by aligning fixes with the referenced documentation.

Quick Start

Start by running the migration steps in order: review both project structures, follow the Kentico Docs MCP guide for adjusting global code, generate code files with the --kxp-codegen command using --skip-confirmation, then copy the specified global code pieces from KX13 to XbyK and confirm the solution builds cleanly.

Frequently Asked Questions about migrate-global-code

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

FAQPage Schema
How do I migrate global code from Kentico Xperience 13 to Xperience by Kentico?

To migrate global code from Kentico Xperience 13 to Xperience by Kentico, follow the Kentico upgrade walkthrough via Docs MCP, generate code files using the kxp-codegen workflow, and copy shared concerns like localization, views, styles, and services to the target project.

What shared components need to be preserved when migrating code to Xperience by Kentico?

Migrating code to Xperience by Kentico requires preserving localization resources, shared views, styles and scripts, identifiers, and services registration to ensure the upgraded site functions end-to-end.

How do I generate migration code files for an Xperience by Kentico project?

Generate migration code files for an Xperience by Kentico project by running the kxp-codegen command with the skip-confirmation flag, guided by the Kentico Docs MCP upgrade walkthrough.

What precautions are needed when reorganizing global code for an Xperience by Kentico migration?

When reorganizing global code for an Xperience by Kentico migration, avoid changing unrelated files or settings, compare legacy KX13 and target XbyK folder layouts, and verify the target project builds successfully without errors or warnings.

Do I need to enable Page Builder when migrating global code to Xperience by Kentico?

Yes, migrating global code to Xperience by Kentico requires enabling content routing and Page Builder so the newly generated site displays content and functions end-to-end after the upgrade.

What should I do if my migrated Xperience by Kentico project has build errors?

If your migrated Xperience by Kentico project has build errors, align your troubleshooting fixes with the referenced Kentico upgrade documentation and ensure all global code pieces were copied correctly without altering unrelated settings.