How do TYPO3 content elements migrate to Xperience by Kentico?
TYPO3 content elements (CTypes such as text, image, textpic, and custom plugin types) have no direct equivalent in Xperience by Kentico, which uses structured content items with defined content types. Each CType must be mapped to a corresponding Xperience content type before migration begins, and any TYPO3-specific RTE link syntax (t3://page?uid=X) inside rich-text fields must be rewritten to valid Xperience URLs during the migration process. If you have custom CTypes from third-party extensions, those require bespoke field mapping decisions; ClonePartner's scoping call will surface exactly which types are in your dataset and what each maps to.
What happens to TYPO3 frontend users (fe_users) when moving to Xperience by Kentico?
There is no 1-to-1 equivalent for TYPO3 fe_users in Xperience by Kentico, so the migration path depends on how your site uses them: users who authenticate on the front end are best migrated to Xperience Members (ASP.NET Identity-based), while users used primarily for marketing or personalization are better migrated to Kentico Contacts. In either case, passwords cannot be carried over because TYPO3's bcrypt or MD5 hashes are incompatible with ASP.NET Identity, so a forced password-reset flow must be in place before cutover. Frontend user groups map to Xperience Roles with limited fidelity, so any group-based permission logic will need to be reviewed and reconfigured in Xperience after the data lands.
Does TYPO3's redirect module migrate into Xperience by Kentico?
Xperience by Kentico has no native redirect management feature, so TYPO3's sys_redirect table records cannot be dropped into a matching UI on the other side. ClonePartner exports the redirect records and delivers them in a format ready for your preferred implementation: web-server rules (IIS URL Rewrite, Nginx rewrite, or Apache mod_rewrite), a CDN/proxy layer such as Azure Front Door or Cloudflare, or a seeded custom Xperience module backed by ASP.NET Core middleware. Choosing the wrong approach here is the most common cause of silent SEO damage post-launch, so this mapping decision should be confirmed during scoping.
Does TYPO3 have an API ClonePartner can use to extract data, or does it need direct database access?
TYPO3 core ships with no REST API; REST access requires either the EXT:headless or EXT:restler extension to be installed and configured on your instance. When those extensions are absent, ClonePartner extracts data via TYPO3's DataHandler, the Impexp extension (.xml/.t3d format), or direct database queries against the TYPO3 MySQL/MariaDB schema. File assets stored in FAL (File Abstraction Layer) are migrated separately, because file UIDs are local to the TYPO3 instance and any reference remapping must happen during import rather than at extraction time.
Will multilingual content and page translations survive the migration intact?
TYPO3 stores translations using an overlay pattern keyed on l10n_parent, which references the default-language record by its numeric PID. Xperience by Kentico stores the equivalent as content item language variants, which is structurally compatible, making this a direct mapping. However, because TYPO3 PIDs are auto-incremented integers that are local to the instance, every parent reference must be remapped to the new Xperience content item identifiers during import, and each language variant must be created individually via the Management API since Xperience has no batch language-variant endpoint. Languages themselves migrate directly, so the language configuration carries over without manual reconstruction.
What has to be manually rebuilt in Xperience by Kentico after ClonePartner delivers the migrated data?
ClonePartner moves content and data; it does not rebuild your application or templates. On the Xperience side, items imported via the Management API land in Draft state and must be published, so a publish step is part of the cutover plan. TypoScript and TYPO3 site configuration are environment-specific and not portable, so channel settings, routing, and any equivalent Xperience configuration must be set up by your development team. Workspaces migrate to Xperience Workflows only loosely, so workflow states and approval rules need to be reconfigured by hand, and any TYPO3 custom extension data requires a bespoke migration script because Xperience has no generic endpoint for custom module records.
How long does the TYPO3 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 TYPO3 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 TYPO3 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
