Which Kentico content types migrate directly to MODX and which need workarounds?
Pages, users, and categories migrate directly to MODX Resources, Users, and Categories. Everything else—custom page types, roles, media files, forms, web parts, site settings, languages, and page attachments—requires a workaround: page types map to Templates with Template Variables (TVs), roles map to User Groups with manually reconfigured permissions, and forms must be rebuilt using a snippet-based solution such as FormIt because Kentico BizForms have no equivalent native structure in MODX.
Do Kentico web parts and widgets come across to MODX?
Web part and widget configurations cannot be ported because they are tightly coupled to .NET assemblies that do not exist in MODX. We migrate the associated content and map widgets to MODX Chunks where possible, but any dynamic logic those widgets performed must be re-implemented as MODX Snippets by your development team after the data lands—this is application rebuild work that falls outside the data migration.
What happens to Template Variables when Kentico page type fields are migrated?
Kentico custom page type fields map to MODX Template Variables, but TV values are stored in a separate join table in MODX, so they require a two-step import: the TV definition must exist on the target before the values are written, and the resource-TV relationship must be established in the correct order. We handle this sequencing during the migration, but any field-level logic embedded in Kentico page type defaults—particularly macro expressions—will not carry over and must be reconfigured in MODX.
What API or version requirements do I need to meet on the Kentico side before migration can start?
The usable API surface depends heavily on which Kentico version you are running. Xperience by Kentico (the current SaaS-first product) has the most complete Management API; Kentico Xperience 13 and earlier rely on the .NET CMS.DataEngine rather than REST for bulk operations, which requires a different extraction approach. If you are on Kentico Xperience 13, note that Kentico's own technical support ends 31 December 2026 and all support, maintenance, and security repairs cease from 1 January 2027, so scoping the migration now avoids operating on an unsupported platform.
Will my Kentico form submission data and workflow history come across to MODX?
Form submission data cannot be imported via Kentico's standard API—extracting it requires direct database access or custom endpoints, which we scope during the pre-migration call. Workflow history and audit logs are generally not portable via the public API and are not migrated. If retaining submission records is a compliance or business requirement, raise it during scoping so the correct extraction method can be planned.
What do I need to do in MODX after the data migration is finished?
Several items require manual attention after the data lands: all users must reset their passwords because neither Kentico nor MODX allows plaintext password transfer; role-based permissions must be reconfigured by hand because Kentico Roles map only approximately to MODX User Groups and ACL interdependencies are complex to automate; any third-party MODX extras (such as getResources or Collections) must be reinstalled on the target instance rather than migrated; and media source configuration must be verified because MODX file assets live on the filesystem and require separate transfer via FTP or rsync, with the media source settings configured to match your target environment.
How long does the Kentico to MODX 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 MODX?
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.
Is migration pricing a flat fee, or does it scale with data volume?
It's a flat fee based on the scope estimate you give us — small variances in actual volume (a bit more or less) don't change the price.
Can we whitelist a single IP instead of opening our network to your migration tool?
Yes — all migration traffic runs through a centralized system using one fixed IP, which your IT team can whitelist instead of opening broader network access.
Will original ownership and authorship on tickets and articles be preserved?
Yes — ownership, author, and created-time metadata are preserved. Where the target doesn't have a native owner field (e.g. tickets becoming list items), this is carried as embedded metadata on the migrated record.
What support do you provide after the migration goes live?
At ClonePartner, we consider ourselves your partners in this journey. We take full accountability for your migration's success. Once your migration goes live, we provide 30 days of comprehensive post-migration support. During this period, we will assist with everything needed to ensure your transition is a complete success.
Will we get a migration report and a ticket-mapping sheet linking old ticket IDs to new ones?
Yes. We provide a comprehensive migration report along with a ticket-mapping sheet that links each old ticket ID to its corresponding new ticket ID. This ensures full traceability, simplifies post-migration verification, and helps your team validate that tickets have been migrated accurately.
After migration, do I contact ClonePartner or the platform's own support if something looks wrong?
ClonePartner is the contact for anything about the migrated data itself. Platform-level behavior — call routing, compose-window UI, and similar configuration — is handled by the destination platform's own support.
If the new system can't natively support an old record type, what are my options?
We handle it case by case: map it to the closest native object, create a custom field or object, fold it into the parent record as text or an internal note, attach it as a file, or keep it in a read-only archive. You see how your chosen approach looks in a sample migration before we run the full set.
Will we get a report showing exactly what migrated versus what didn't?
Yes. You get a final reconciliation report comparing source and target counts for every object.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
