skills.rest
Kentico
KenticoOFFICIAL
Explore all skills by this author →
Website𝕏@KenticoGitHub

migrate-page-widgets

Convert Kentico Xperience 13 Page Builder widgets and sections to Xperience by Kentico.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating Page Builder pages from Kentico Xperience 13 to Xperience by Kentico can break layouts and features if widgets and sections aren’t converted correctly.

Core Features & Use Cases

  • Widget & Section Discovery: Identifies all Page Builder widgets and sections used by a specified legacy page before migrating anything else.
  • Dependency-Aware Migration: Converts widgets and sections together with their dependencies to keep runtime behavior consistent.
  • Dynamic Data Preservation: Ensures anything that was fetched dynamically in the legacy project remains dynamic in the new project, avoiding hardcoded regressions.

Quick Start

Ask the AI to migrate the widgets and sections for the page “home” from the legacy URL https://localhost:5001/en-us/home, then validate that the new project builds successfully.

Frequently Asked Questions about migrate-page-widgets

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

FAQPage Schema
How do I migrate Page Builder widgets and sections from Kentico Xperience 13 to Xperience by Kentico?▼

Migrating Page Builder widgets and sections requires analyzing the legacy page composition, converting all widgets and their dependencies, and preserving dynamic data retrieval behavior to maintain runtime consistency in the new project.

What happens to dynamically fetched data when I upgrade Kentico Xperience 13 page widgets?▼

Dynamic data retrieval behavior is preserved during migration to ensure that anything fetched dynamically in the legacy project remains dynamic in the new project, avoiding hardcoded regressions and maintaining runtime functionality.

Can I migrate page widgets and sections independently of page logic?▼

Widget and section conversion applies to page-specific migration workflows where the structure must be converted prior to migrating page logic, ensuring dependencies are mapped together to keep runtime behavior consistent.

How do I identify which Page Builder widgets need conversion before migrating a Kentico page?▼

Widget and section discovery identifies all Page Builder widgets and sections used by a specified legacy page by analyzing the page composition before migration, ensuring all components and dependencies are accounted for.

Do I need to read Kentico documentation before migrating Page Builder widgets?▼

The migration process requires reading relevant Kentico Docs MCP references to properly analyze the legacy page composition, convert all widgets and sections with their dependencies, and preserve dynamic data retrieval behavior.

Related Skills

Explore More Software Engineering Skills→
KenticoKentico
14

migrate-page

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

Official
Advanced
KenticoKentico
14

migrate-global-code

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

Official
Advanced
i3ringiti3ringit
3

compound-docs

Document solved problems into categorized Markdown files with YAML frontmatter.

Community
Intermediate
KenticoKentico
14

migrate-shared-component

Migrate shared UI components from Kentico Xperience 13 to Xperience by Kentico.

Official
Advanced