migrate-widgets

Generate C# widget migration code for KX13-to-XbyK content transformations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

It eliminates the manual effort of writing C# migration code to transform KX13 widget/section configurations into Xperience by Kentico (XbyK) equivalents.

Core Features & Use Cases

  • Generates IWidgetMigration code to rename widget and section type identifiers and restructure widget JSON variants/properties.
  • Generates IWidgetPropertyMigration code or delegates to built-ins to convert specific property values (including overrides for defaults like page selectors).
  • Supports migration-plan-driven and text-driven inputs, producing DI registration-ready code for the Migration.Tool.Extensions project.

Quick Start

Ask the AI to generate migrations by providing the migration plan path to migrate-widgets, including the widget transformations and property conversions you need for KX13→XbyK.

Frequently Asked Questions about migrate-widgets

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

FAQPage Schema
How do I migrate Kentico KX13 widgets to Xperience by Kentico?

To migrate Kentico KX13 widgets to Xperience by Kentico, you need C# widget and widget property migration implementations that transform KX13 widget JSON into XbyK-ready structures, handling type identifier renaming and property restructuring automatically.

What is the best way to convert KX13 widget property values during a content migration?

The best way to convert KX13 widget property values is by generating IWidgetPropertyMigration code or delegating to built-in conversion migrations, which handle specific property value transformations including overrides for defaults like page selectors.

Can I generate dependency injection safe code for Kentico widget migrations?

Yes, generating dependency injection safe code for Kentico widget migrations produces DI-safe transient registrations specifically designed for the Migration.Tool.Extensions project, ensuring your IWidgetMigration and IWidgetPropertyMigration classes integrate cleanly.

Do I need a migration plan to restructure widget JSON for Xperience by Kentico?

You do not strictly need a formal migration plan to restructure widget JSON for Xperience by Kentico, because the generation process supports both migration-plan-driven inputs and free-text descriptions of widget transformations and property conversions.

Why does my KX13 to XbyK content migration require widget type renaming?

KX13 to XbyK content migration requires widget type renaming because Xperience by Kentico uses different type identifiers for widgets and sections, necessitating C# migration implementations to map and transform the legacy JSON structures correctly.