migrate-page

name	migrate-page
description	Migrates a page from a Kentico Xperience 13 project to Xperience by Kentico. Converts controllers, views, layouts, content retrieval, and all dependencies for the specified page. Use when migrating the business and presentation logic of a specific page after its Page Builder widgets have been migrated.
argument-hint	Name of the page in the content tree and the legacy page URL
compatibility	Requires Kentico Docs MCP and Playwright MCP

You are tasked with the process of migrating a page from the legacy project to the new one.

Input Parameters

• Page Name - The name of the page to migrate (e.g., 'home', 'doctors').
• Legacy Page URL - The URL of the page in the KX13 project (e.g., 'https://localhost:5001/en-us/home').

Structure of the projects

You are currently located in the root folder, which contains two subfolders:

• KX13/ - This folder contains the Kentico Xperience 13 project files. This is the legacy/source project.
• XbyK/ - This folder contains the Xperience by Kentico project files. This is the new project.

Important

When migrating a page, ensure that everything that was fetched dynamically from the database will still be dynamically fetched from the database. Nothing can be statically hardcoded in the new project if it was dynamic in the legacy project.

Useful Documentation

• Use Kentico Docs MCP to read the following pages:
  • Display an upgraded page
  • Adjust your code and adapt
  • Upgrade content retrieval code
  • Content Retrieval
  • Content Retriever API
  • Page Builder
  • Widgets for Page Builder
  • Sections for Page Builder
• Use web fetch to read the following pages:
  • Migration Tool README - Pages

Migration Steps

1. Read all documentation links mentioned above.
2. Review how the legacy page looks using the provided URL and identify all parts it consists of.
3. Go through pages in the legacy project and identify the provided page.
4. When you know the page, research how this page works and identify all other shared pages, components, or whatever this page relies on.
5. If present, check how other pages are implemented in the new project.
6. Migrate page's controller, content, layout, and relevant components, repositories, and services to the new project, together with all dependencies identified.
7. When done with implementation, ensure that the new project builds successfully without errors and warnings. If not, fix the issues until none are present.
8. Using the Playwright MCP, check that the migrated page is displayed correctly and functions as expected, exactly matching styling, content, and texts as in the image of the legacy page. If not, make necessary adjustments until it does (this can also include changes in dependencies).

Whenever unsure about anything, you can use Kentico Docs MCP to search for relevant information.

Output format

When done, provide the user with this exact output (without any additional text):

# Migration Complete
Page migration from the legacy project to the new one has been successfully completed.

**Next steps:**
- Review the changes to ensure everything looks as expected.
- You can use the migrate-page-visual skill to fix visual issues caused by the migration.

The page migration is now complete. Continue migrating other pages by repeatedly running migrate-page-widgets and migrate-page. To migrate shared components such as layouts, headers, footers, use migrate-shared-component.