lp-hero-t3
Move TYPO3 forward in one pass, not six.
The supported route to a current TYPO3 climbs every release in between, and each hop is a chance for an extension to break. We read your existing install directly — without booting it — and write a clean 14.3 LTS: the page tree, the content elements, the inline items, the files and their alt text. The versions in the middle never have to exist.
Round-trip verified on TYPO3 12 → 14.3 LTS. Older installs are read the same way; we confirm your version in the free assessment.
Landing: TYPO3 version ladder
Already on TYPO3? The upgrade is a migration too.
Moving a TYPO3 site forward normally means climbing every release in between, and every hop is a chance for an extension to break. We read the old install once and write a current one — the tree, the content elements, the files and their alt text — so the versions in the middle never have to exist.
Verified end to end on TYPO3 12 → 14.3 LTS: the round trip returns identical page, tree and content-element counts, with titles, body text and every file byte-identical. Older sources are read the same way; we confirm your version during the free assessment. Templates and extensions are rebuilt, not carried — that part is a rewrite on any path.
lp-prose-t3
What crosses — and what doesn’t
An upgrade is a migration, so the honest answer has two halves.
Carried, and checked
- The page tree — hierarchy intact, every parent edge written as TYPO3’s own
pid. - Content elements in their column and order, with their rich text.
- Inline items — accordions, carousels, tabs, timelines — still inline items, not flattened.
- Files as real FAL references, with the alt text that belongs to each usage.
- Categories and their assignments.
- Unpublished stays unpublished. Hidden pages arrive hidden.
- Stable identity — every record keeps a key, so a re-run updates in place instead of duplicating.
Rebuilt, and told to you first
- Templates and TypoScript. A current TYPO3 renders differently; the front end is rebuilt, on any upgrade path.
- Extensions. Replaced or rewritten — the free assessment lists yours and what each one would take.
- Translations and workspaces. Not carried today. Translated rows are counted and named in the report rather than quietly dropped.
That second list is the point. The question that matters before an upgrade is not “can it be done” — it is what will be missing afterwards, and you get that answer before you commit, not after go-live.
Landing: verification
How we know it worked
Every route is gated on a check that compares the two ends — your old system and your new one — and a migration ships only when the numbers agree.
| What we check | Estate | Result |
|---|---|---|
| Drupal 7 → Drupal 7 the integrity check: we rebuild your site into the same platform, where any difference at all is a defect rather than a consequence of a different data model | 3,000 nodes 120 terms | node ids, titles, 3,000 body values and their text formats, 3,691 taxonomy references, 1,472 image references, 24 files — identical, 0 references dropped |
| TYPO3 12 → TYPO3 14.3 LTS the upgrade, in one pass instead of six | 83 pages 222 content elements | 82 of 82 page-tree edges, 60 inline items re-owned, body text and all 32 files byte-identical; re-running updates in place rather than duplicating |
| Drupal 7 → TYPO3 14.3 LTS a cross-platform move | content, taxonomy, menus | content items, taxonomy terms and menus all matched end to end; differences that remain are the target's own conventions, and are named |
These are our own test estates, not customer migrations. We have no case studies to show you yet, and inventing them would contradict the only thing we are selling. What we publish instead is the method and the numbers it produces — and your assessment runs the same checks against your estate, so you get this table about your own content before you commit to anything.
Landing: proof band
Landing: how it works
Three stages, no leap of faith
Each stage is small enough to say yes to, and each one pays for itself.
Assess — free
We scan your estate and hand you a map of it: every module bucketed, content counts, real field-mapping verdicts, attention flags. Nobody else gives you this measurement of your own site.
Evaluate — fixed fee, credited
A representative slice of your real content stands up in 2–4 candidates. You get working previews, a written recommendation and a migration plan for each. The fee credits in full against the migration — you never pay twice.
Migrate — to whichever you pick
The estate moves to the winner, losslessly — ids, fields, permissions, designs. Your source stays live until cutover day, and cutover is reversible. If you pick something we don't build, we still get you there.
Landing: pricing
Priced like the decision it is
Start free. Pay a small fixed fee to see your content in every candidate — credited in full when you migrate.
- A map of your own estate
- Every module bucketed, real field-mapping verdicts
- Content counts & attention flags
- No obligation
- Your real content standing in 2–4 candidates
- Working previews — not slide decks
- A written recommendation & per-target migration plan
- Credited in full against the migration
- The estate moved to the target you chose
- Ids, fields, permissions & designs preserved
- Round-trip verification report
- Managed transition hosting while you switch
Landing: contact / request an assessment
Start with the free assessment
Tell us about your estate — platforms, number of sites, timeline. You'll get back a measured map of your own site (modules bucketed, field-mapping verdicts, attention flags) and a fixed quote for the evaluation. No obligation, no sales pressure.
Prefer email? Everything here just reaches a real inbox.