migrate-shared-component

Migrating shared layout components from Kentico Xperience 13 involves porting controllers, content, and layouts while preserving dynamic data retrieval. You locate the component in the legacy project, port its dependencies, build the target project, and validate rendering via Playwright.

To preserve dynamic content behavior during a Kentico migration, you must ensure that dynamically fetched data in the legacy project remains dynamically fetched in the new project. This prevents incorrect hardcoding of values that should be retrieved at runtime.

Yes, migrating a shared component to Xperience by Kentico includes dependency-aware migration. The process locates the target component in the source project and migrates it along with relevant dependent components, pages, and services to maintain functionality.

The best way to verify visual parity after migrating a navigation component is using Playwright MCP. This validates that the migrated UI matches the legacy rendering, confirming that styling, content, and text appear correctly in the new project.

Yes, you can use Playwright to validate cross-page UI elements migrated from Kentico Xperience 13. The migration process uses Playwright MCP specifically to confirm that shared layout elements like breadcrumbs and headers render correctly.

To start migrating a shared header component, you need the shared component name and the legacy page URL where that component appears. You also need access to Xperience upgrade documentation to analyze and execute the porting process.