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

migrate-fields

Generate C# IFieldMigration code for KX13 to XbyK field transformations.

14|7|Updated Nov 25, 2025
Search Tags:#csharp#data transformation#field migration#kenti co-xperience#xbyk#kentico kx13#xml patching
One-click install
npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill migrate-fields
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-fields
Source: https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kx13-content-migration/skills/migrate-fields
Command: npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill migrate-fields

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill generates C# IFieldMigration extension code to migrate custom KX13 field values and definitions into Xperience by Kentico, handling cases where simple configuration is not enough.

Core Features & Use Cases

  • Field definition transformation: Patches XML field definitions (form control, data type, and settings) using System.Xml.Linq so the target XbyK schema matches the migrated data.
  • Value conversion with context awareness: Safely transforms field values (null-safe, type-safe) including conditional behavior across pages, custom tables, and forms via SourceObjectContext.
  • Cross-class, form-control-driven migrations: Supports transformations that apply globally across multiple classes when the same source form control and/or data type requires consistent handling.
  • Recommended generation workflow: Reads a migration plan to identify Custom Form Control Fields and Field Mappings, then generates DI registration and a DI-ready ServiceCollectionExtensions setup.

Quick Start

Use the migrate-fields skill to generate IFieldMigration C# code for a KX13→XbyK migration plan stored at the path provided in your command.

Frequently Asked Questions about migrate-fields

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

FAQPage Schema
How do I migrate custom form control fields from KX13 to Xperience by Kentico?▼

Field value transformation during KX13 to XbyK migration is handled by generating IFieldMigration implementations that safely convert values using SourceObjectContext. These generated migrations provide null-safe, type-safe conditional transformations across pages, custom tables, and forms for consistent cross-class field handling.

How do I convert field values across pages and custom tables during a Kentico migration?▼

Field value transformation during KX13 to XbyK migration is handled by generating IFieldMigration implementations that safely convert values using SourceObjectContext. These generated migrations provide null-safe, type-safe conditional transformations across pages, custom tables, and forms for consistent cross-class field handling.

What is the best way to patch XML field definitions when migrating to Xperience by Kentico?▼

Patching XML field definitions during migration involves using System.Xml.Linq to update form controls, data types, and settings within the XML. The generated IFieldMigration code modifies the target XbyK schema directly, ensuring the field definitions match the converted data structure.

Can I handle HTML sanitization and URL rewriting as part of a Kentico field migration?▼

HTML sanitization and URL or media path rewriting are supported within the generated IFieldMigration code for KX13 to XbyK migrations. The generated implementations apply these transformations conditionally based on the source form control and data type, ensuring data integrity across the migrated classes.

Do I need to manually register field migrations in dependency injection for XbyK?▼

Manual DI registration is not required because the generated code includes a DI-ready ServiceCollectionExtensions setup. It reads the migration plan to identify field mappings and custom form controls, then produces DI-registered Migration.Tool.Extensions.FieldMigrations implementations that compile successfully.

When do I need custom IFieldMigration code instead of standard configuration for a Kentico migration?▼

Manual DI registration is not required because the generated code includes a DI-ready ServiceCollectionExtensions setup. It reads the migration plan to identify field mappings and custom form controls, then produces DI-registered Migration.Tool.Extensions.FieldMigrations implementations that compile successfully.

Related Skills

Explore More Software Engineering Skills→
KenticoKentico
14

migrate-widgets

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

Official
Advanced
KenticoKentico
14

migrate-classes

Generate C# IClassMapping and IReusableSchemaBuilder code from a KX13 to XbyK migration plan.

Official
Advanced
KenticoKentico
14

migrate-content-items

Generate ContentItemDirectorBase C# code for KX13 to XbyK migration strategies.

Official
Advanced
wilfriedagowilfriedago
2

unit-test-mapper-converter

Test MapStruct mappers and custom converters with JUnit 5 and AssertJ.

Community
Intermediate