What happens to my Sitefinity News Items, Blog Posts, and Events during migration?
Xperience by Kentico has no native News, Blog Post, or Events content types, so these are migrated as custom Content Items using a workaround mapping. Before the migration runs, the corresponding content type schemas must be defined in XbyK, and after data lands, each item will arrive in Draft state and must be published. ClonePartner handles the data movement and field mapping; the content type definitions in XbyK need to be in place on your instance beforehand.
Can my Sitefinity registered users log in to the new Xperience by Kentico site after migration?
Not immediately without a password reset. XbyK uses ASP.NET Core Identity for front-end members (CMS_Member table, available from v28+), which is incompatible with Sitefinity's SHA-256/PBKDF2 password hashes, so direct hash migration is not possible. ClonePartner migrates user records by mapping Sitefinity users to XbyK Members for authentication and simultaneously creating linked Contact records for CRM data, but a forced password-reset email to all affected users is a required step after cutover. Custom profile fields are carried into either Contact custom attributes or a linked Custom Module object depending on your XbyK data model.
Do my Sitefinity Dynamic Content (Custom Module) records migrate automatically?
No — this is one of the most preparation-dependent parts of the migration. XbyK has no generic REST endpoint for custom module data, and each custom module requires its own migration script targeting the module's specific database table; additionally, the module schema must be manually recreated in XbyK before any data can be inserted. ClonePartner writes those per-module scripts as part of the project, but your team must supply the target schema definitions or recreate the modules in XbyK admin first. Without the schema in place, there is nowhere for the records to land.
Will my Sitefinity form submissions (responses) be migrated, or just the form definitions?
Both can be migrated, but form responses require more work than definitions. Each form must first exist in XbyK as a BizForm, which dynamically generates its own database table (BizForm_[sitename]_[formname]); ClonePartner then bulk-inserts historical response rows via SQL or the BizFormItemProvider API, adding required XbyK system columns such as FormInserted, FormUpdated, and FormGUID. If your target is a cloud/SaaS XbyK tier without direct database access, all inserts must flow through the .NET API, which adds complexity but remains achievable. Clarify at scoping whether response history is in scope, because some teams choose to treat it as out-of-scope and document that decision explicitly.
What breaks silently if internal Sitefinity content GUIDs are not remapped during migration?
Sitefinity assigns internal GUIDs to content items, and those GUIDs change when records are imported into XbyK, which breaks any cross-content references that were stored by ID — for example, page widgets that reference a specific content item or related-content fields that point to another record. ClonePartner builds a GUID remap table during the migration and uses it to resolve references before the data is committed, but page widget configurations that hard-code content IDs must also be reviewed and updated in XbyK after cutover, since widget rendering logic does not transfer as part of the data migration.
Does the official Kentico Migration Tool handle Sitefinity as a source?
No. The official Kentico Migration Tool on GitHub (xperience-by-kentico-migration-tool) is built to migrate from Kentico Xperience 13 and does not support Sitefinity as a source. Sitefinity-to-XbyK migrations require custom ETL scripts that extract data via Sitefinity's OData REST API or direct database queries and load into XbyK through the Management API or database seeding — which is the approach ClonePartner uses. Additionally, Sitefinity's Content Delivery API is read-only and cannot be used for export in a migration context, so API authentication via a Sitefinity OAuth service account must be configured before extraction begins.
How long does the Sitefinity 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 Sitefinity 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 Sitefinity 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
