migrate-page

Migrate Kentico Xperience 13 pages to Xperience by Kentico with dependency conversion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you migrate a specific legacy Kentico Xperience 13 page into Xperience by Kentico without breaking its dynamic behavior or dependencies.

Core Features & Use Cases

  • End-to-end page migration: Converts controllers, views, layouts, and content retrieval for a selected page.
  • Dependency-aware conversion: Identifies and migrates shared components, repositories, and services the page relies on.
  • Visual and functional verification: Uses Playwright-based checks to match styling, content, and texts from the legacy page image.

Quick Start

Run migrate-page and provide the page name and the legacy page URL so the Skill can research, migrate, and verify the page end-to-end.

Frequently Asked Questions about migrate-page

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

FAQPage Schema
How do I migrate Kentico Xperience 13 pages to Xperience by Kentico?

Migrate Kentico Xperience 13 pages to Xperience by Kentico by converting controllers, views, and layouts, while preserving dynamic content retrieval and migrating shared dependencies to ensure the new project builds cleanly.

What does page migration do with legacy dynamic content retrieval and dependencies?

Page migration identifies and migrates shared components, repositories, and services the legacy page relies on, ensuring dynamic content retrieval and dependencies are preserved during the Kentico Xperience 13 to Xperience by Kentico conversion.

How to verify visual and functional behavior when converting Kentico pages?

Verify visual and functional behavior during Kentico page conversion by using Playwright-based checks to match styling, content, and texts from the legacy page image against the newly migrated Xperience by Kentico rendering.

Can I use Playwright to validate Xperience by Kentico page rendering against the legacy site?

Playwright is used to validate Xperience by Kentico page rendering by comparing the new project's visual output and functional behavior against the legacy Kentico Xperience 13 page image.

What do I need to start migrating a specific page to Xperience by Kentico?

To start migrating a specific page to Xperience by Kentico, provide the page name and the legacy page URL so the Skill can research implementation details, migrate dependencies, and verify the page end-to-end.

When should I run page migration after converting Page Builder widgets?

Run page migration after Page Builder widgets are migrated, as the workflow applies to controller, view, and layout conversion and handles dependency migration for the selected legacy Kentico Xperience 13 page.