What happens to my Kentico user accounts and passwords during migration?
Front-end site members (CMS_User) are migrated to Xperience by Kentico's MemberInfo table, preserving email addresses, usernames, and password hashes where the hashing algorithm is bcrypt-compatible. If your Kentico instance used SHA2 password hashing, those hashes cannot be reused and a forced password-reset email flow is required post-migration. Back-end administrator accounts have no supported bulk import path in Xperience by Kentico and must be recreated manually through the Administration UI. Contact and profile data is migrated separately to ContactInfo in the Digital Marketing module and linked to the corresponding Member record.
Do my Kentico Contact Groups migrate to Xperience by Kentico?
There is no direct equivalent to Kentico's Contact Groups in Xperience by Kentico. Dynamic contact groups can be partially replaced by recreating their conditions as Contact Segments in the Segmentation UI, but the historical group membership itself is not migrated — it is recalculated at runtime against the new rules. Static (manually assigned) contact groups have no native home; the standard workaround is to create a custom module object to store group definitions and encode membership as a custom contact field, which requires custom development in your Xperience by Kentico project after the data lands. If you rely on contact groups for email campaigns or personalization, you should plan this workaround before cutover.
How do URL aliases and redirects from Kentico transfer to Xperience by Kentico?
Xperience by Kentico has no native URL Aliases or Redirects object, so there is no direct mapping from Kentico's CMS_PageAlias and CMS_UrlAlias tables. ClonePartner extracts all source alias data and normalizes it to source path, destination URL, and HTTP status code; it then loads it into your chosen target mechanism — typically IIS URL Rewrite rules in web.config, an ASP.NET Core middleware redirect map, or a custom Redirect module object in Xperience by Kentico. Whichever approach your development team chooses must be configured and deployed in your Xperience by Kentico project before the migration data is applied, or redirects will be silently absent at cutover. Missing this step is one of the most common causes of SEO rank loss after a Kentico-to-XbyK replatform.
What source version of Kentico do I need before ClonePartner can migrate my data?
For migrations targeting the Kentico Migration Toolkit pipeline, Kentico requires the source to be on version 13.0.64 (Refresh 5) or newer; earlier 13.x patch levels are not compatible. Kentico 12.x, 11.x, and earlier versions are already out of support and are not supported by the official toolkit, though ClonePartner can extract data directly via the database and Kentico's .NET DataEngine for those versions. Portal Engine projects on any version must be moved to the MVC model before content can be migrated to Xperience by Kentico, as Portal Engine page templates and web part configurations are not portable and have no equivalent in XbyK. Kentico Xperience 13 itself reaches end of support on 31 December 2026, so projects still on 13 have a firm deadline for completing this transition.
Will my Kentico categories and tags come across into Xperience by Kentico automatically?
Both require workarounds rather than direct object-to-object mapping. Kentico's flat category tree maps loosely to Xperience by Kentico's hierarchical Taxonomy Tag Groups, and existing page-category relationships must be re-established after both sides are migrated, because the link records reference IDs that change during migration. Kentico tags are restructured under Xperience by Kentico's unified taxonomy system, which means tag data is importable but the taxonomy group structure must be created first as a prerequisite before tag records can be loaded. If category or tag data is migrated out of sequence — content before taxonomy structure — the relationship records will have nothing to point to and the associations will be silently lost.
What structural objects in Xperience by Kentico have to be set up before content records can be loaded?
Xperience by Kentico has no single bulk import API; structural definitions must exist before their associated content records arrive. This means custom Content Types (migrated from Kentico's Document Types / Page Types), Taxonomy Tag Groups, Languages, and any custom module class definitions must all be deployed — typically via Xperience by Kentico's CI/CD file-based serialization — before ClonePartner begins loading pages, content items, or form definitions. Additionally, content items imported via the Management API arrive in Draft state and must be explicitly published; any items not published will not appear on the live site after cutover. Form submission records have no REST endpoint in Xperience by Kentico, so those require direct database access or a custom C# endpoint and cannot be loaded through the standard Management API pipeline.
How long does the Kentico to Xperience by Kentico migration take?
Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.
Will my team lose access to Kentico during the migration?
No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.
Will there be downtime when migrating from Kentico to Xperience by Kentico?
No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.
How do I validate that everything migrated correctly?
Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.
Do I need professional help for this migration?
While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.
Does ClonePartner provide guidance before committing?
Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
