Skip to content
Skills Library
Programming · Conversion & formats

migrate-code-page

/migrate-code-page

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.

Licence
MIT
Last repository change
14.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
10
Deprecation

No signals detected. Repository changed on 14.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Arguments

/migrate-code-page [page-name] [legacy-page-url]
Original author 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.

How it works

  1. Input Parameters
  2. Structure of the projects
  3. Important
  4. Useful Documentation
  5. Migration Steps
  6. Output format
Original SKILL.md headings · 61 lines, 481 words
SKILL.md preview
---
name: "migrate-code-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: "[page-name] [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](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-walkthrough/display-an-upgraded-page)
  - [Adjust your code and adapt](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/adjust-your-code-and-adapt)
  - [Upgrade content retrieval code](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-deep-dives/upgrade-content-retrieval)
  - [Content Retrieval](https://docs.kentico.com/documentation/developers-and-admins/development/content-retrieval)
  - [Content Retriever API](https://docs.kentico.com/documentation/developers-and-admins/api/content-item-api/content-retriever-api)
  - [Page Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder)
  - [Widgets for Page Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/widgets-for-page-builder)
  - [Sections for Page Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/sections-for-page-builder)
- Use web fetch to read the following pages:
  - [Migration Tool README - Pages](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/blob/master/Migration.Tool.CLI/README.md#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):

```markdown
# 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-code-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-code-page-widgets and migrate-code-page. To migrate shared components such as layouts, headers, footers, use migrate-code-component.
```

Versions

The database has no other skills named migrate-code-page.

Database snapshot: 13.11.2026 · package version 0c08702b1e31 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100migrate-code-page-widgets
    Migrates Page Builder widgets and sections from a Kentico Xperience 13 page to Xperience by Kentico. Identifies and converts all widget and section components used by the specified page. Use when migrating Page Builder features for a specific page before migrating the page logic itself.
  • 100migrate-code-global
    Migrates global code from a Kentico Xperience 13 project to Xperience by Kentico. Sets up the target project structure, generates code files, and migrates shared code including localization, styles, business logic, and project startup configuration. Use when starting a KX13 to…
  • 100update-xperience
    Update Xperience by Kentico to a newer version - regenerate the DancingGoat example from the new project template, keeping this repository's changes, bump its Kentico packages, and optionally raise the libraries' minimum Xperience version (Kentico NuGet and npm packages). Use…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.