Page tree and records
Page hierarchy, content ownership, visibility, dates, ordering, route context, and stable uid/pid identity.
Available migration objects and capabilities depend on the selected source and target systems. Check current integration status before using this planning guide.
What the migration covers
TYPO3 is stable and source-only in the capability catalog. The app contains version-aware Bridge families from TYPO3 4.5 through modern installations, with configured coverage for content, taxonomy, authors, comments, attachments, menus, and menu items where supported by the source version.
Content elements
tt_content types, columns, headers, body values, relations, FlexForm or custom-element review, and assembly rules.
Files and references
Pre-FAL or FAL storage, file metadata, usage records, originals, crops, links, language context, and destination media.
Languages and extensions
Overlays, translations, fallbacks, categories, news or custom tables, redirects, and extension-specific scope.
What requires separate scope
TypoScript, Fluid templates, sitepackages, backend configuration, frontend users, permissions, forms, search, plugins, schedulers, integrations, custom PHP, and extension behavior do not migrate as generic content. They require destination implementation or a dedicated data adapter.
Choose the extraction path by TYPO3 generation
TYPO3 storage, localization, routing, and files changed across major versions, so the source connector must match the actual schema.
Confirm core and extensions
Record TYPO3 version, database, composer state, installed extensions, overrides, custom tables, workspaces, languages, and site configuration.
Select the Bridge family
Use the compatible versioned adapter only after its expected tables, fields, FAL generation, routing, and access path are verified.
Profile content types
Count every CType, plugin, list type, container, IRRE relation, FlexForm, custom element, and extension-owned record.
Capture rendered evidence
Crawl public routes and languages so database records can be reconciled with what users and search engines can reach.
Assemble pages from ordered elements
A TYPO3 page is a container for records in columns and languages; it is not a direct equivalent of one destination body field.
Define element transformations
Route each CType into a block, field, child record, reusable component, normalized body fragment, rebuild task, or exclusion.
Preserve page context
Keep pid, colPos, sorting, language, visibility, workspace, and stable IDs while elements are transformed.
Resolve dependencies first
Load authors, categories, files, translations, and referenced records before dependent content resolves destination IDs.
Handle extensions explicitly
Map news, events, directories, and custom tables through their schemas rather than flattening them into generic pages.
Validate routes, languages, and FAL evidence
Acceptance combines record reconciliation with rendered route and media checks across every approved locale.
Reconcile per locale
Compare source, extracted, transformed, loaded, skipped, failed, visible, hidden, and accepted totals by page and CType.
Inspect complex pages
Review mixed columns, nested elements, custom records, translations, categories, files, links, visibility, and destination rendering.
Audit file references
Verify original availability, metadata, usage, crops, rewritten URLs, duplicates, and reported missing or rejected assets.
Crawl route variants
Test aliases, slugs, language prefixes, redirects, canonicals, hreflang, sitemap entries, internal links, and priority pages.
How the workflow works
- 1. Discover: Confirm TYPO3 version, Bridge access, page tree, languages, workspaces, content types, extensions, FAL, routes, and destination readiness.
- 2. Map: Approve destination types, page assembly, element transforms, files, translations, taxonomy, users, URLs, rebuild work, and exclusions.
- 3. Pilot: Transfer representative standard and custom pages across languages into staging and correct systematic rules.
- 4. Validate: Reconcile records and inspect elements, relationships, files, routes, metadata, language behavior, rendering, and exceptions.
- 5. Cut over: Execute the final or delta plan, implement redirects, complete locale-aware launch checks, and retain the approved evidence.
Technical references
Scope is reviewed against the source and destination documentation available for the project.