WordPress hosting for sites migrating from TYPO3.
There is no importer for this one. TYPO3 stores a page as a tree node with a list of content elements attached, and nothing in WordPress corresponds to that until somebody decides what it should become.
A content model that has to be translated.
TYPO3 and WordPress disagree about what a page is. Every decision below has to be made before the first record is transferred, not after.
Pages are trees of elements, not documents
A TYPO3 page is a node with content elements attached to columns. WordPress expects a single body. Each element type needs a destination — a block, a field or a component — chosen up front.
Routed URLs kept exactly
TYPO3's routing produces paths built from the page tree and its slug configuration. WordPress would generate something different for the same content, changing every address that currently ranks.
Media held by reference, not by path
The File Abstraction Layer stores files once and points at them through reference records. Copying the files alone produces a media library that no page is actually using.
Languages are columns, not sites
TYPO3 keeps translations as language overlays of the same record. WordPress needs a plugin and a structural decision — separate posts, or connected translations — before anything is imported.
Extbase extensions have no counterpart
Custom extensions are application code with their own tables. Nothing imports them; each is a functional gap to be filled by a plugin, a custom post type or a rebuild.
Map the model, then move the content.
TYPO3 migrations go wrong in the planning, not the transfer. Once the element types and the URL structure are agreed, moving the records is the straightforward part.
- Page tree and element types mapped to blocks
- Routing configuration reproduced as redirects
- FAL references resolved to real files
- Translation strategy chosen before import
An enterprise site, without the enterprise stack.
Most TYPO3 installations being moved carry years of extensions and a caching framework nobody still has the documentation for. Leaving that behind is much of the speed gain.
What we change moving from TYPO3
These differ from a standard WordPress site on the same plan, and each follows from a content model that is genuinely more structured than the one it is moving into.
| Setting | What we do | Why |
|---|---|---|
| Page tree mapping | Tree depth and content element types agreed before any record is transferred | A TYPO3 page is a node carrying content elements in named columns rather than a document with a body, so without an agreed destination for each element type there is nothing sensible to import into. |
| URL preservation | Routing configuration reproduced with rewrites and redirects | Paths are assembled from the position of a node in the tree and its slug configuration, so letting WordPress generate its own permalinks silently changes every address the site has accumulated authority on. |
| FAL media references | Reference records resolved to files, then rewritten into the media library | The File Abstraction Layer deliberately separates a file from the records that point at it, so moving the files alone produces a full library that no page on the new site actually references. |
| Translation handling | Language overlays converted to a chosen plugin structure before import | TYPO3 stores a translation as an overlay row against the original record, and WordPress has no native equivalent, so the choice between separate posts and linked translations determines the shape of the import itself. |
| Extension replacements | Each Extbase extension matched to a plugin, a custom post type or a rebuild, before launch | Custom extensions are application code with their own database tables rather than content, so nothing about them can be imported and each one is missing functionality on day one unless it was planned for. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Is there a TYPO3 to WordPress importer?
What happens to my content elements?
Do TYPO3's routed paths survive the move?
My images came across but pages show nothing. Why?
How do multilingual TYPO3 sites transfer?
Move from TYPO3 with the tree and the URLs intact.
Free migration, a content model mapped by a person, and every routed address preserved.