Upgrades that don't become a gamble.
A TYPO3 major upgrade can cost weeks and still go wrong. Not with us. We've built a well-rehearsed, script-driven process — tested, reproducible and plannable. You focus on the client, we safely bring your system into the present.
Why now? The clock is ticking.
TYPO3 v12 lost regular support on 30 April 2026 — staying on it means paid ELTS or being unprotected. v13 runs until the end of 2027, the new v14 LTS (since April 2026) until June 2029. The longer you wait, the bigger the version jump — and the more expensive catching up. A planned upgrade now is cheaper and safer than an emergency later.
How long your version stays safe.
Remaining free community support from 2026, in years. v12 has already expired — after that, only paid ELTS helps.
Script-driven, not a gamble.
We've built a reproducible process for TYPO3 upgrades that cuts risk and effort dramatically — even across multiple major versions.
Analysis & inventory
Extensions, custom code and TCA captured automatically — extension scanner and deprecation log included. We know up front what's coming.
Extension compatibility
We check every extension for a compatible version for the target version — and replace or port what doesn't fit.
Script-driven migration
Rector for TYPO3 and our own scripts replace deprecations automatically. Repeatable steps instead of manual click-by-click.
Automated tests
Visual regression tests (e.g. BackstopJS) make sure nothing breaks — before anything goes live.
Upgrade wizards & schema
Database migrations and upgrade wizards run in a controlled, documented way — no blind flying in the install tool.
Clean cut-over
Plannable, documented, no surprises at night. Operations keep running while we switch over.
Deprecations, extensions, Composer — our problem.
The three most common reasons upgrades fail: untreated deprecations, incompatible extensions and Composer constraints that won't resolve. That's exactly our daily business. We know the pitfalls — and clear them away before they become a problem.
Discuss an upgradeGo deeper on TYPO3 upgrades.
Upgrade or relaunch?
Why the real decision has nothing to do with TYPO3 versions.
Separating code & database migration
For predictable, low-risk and repeatable projects.
Automating TYPO3 upgrades
With Rector, automated tests and a reproducible process.
Fixed-price TYPO3 upgrades
Thanks to a reproducible engineering process instead of guesswork.
Questions about the TYPO3 upgrade.
The essentials up front — and if something's missing, just ask us.
Which version should we upgrade to?
What does an upgrade cost?
Upgrade or rather relaunch?
What happens with incompatible extensions?
Will something break during the upgrade?
What about ELTS?
How big is your upgrade?
Get a first estimate in a few minutes — or tell us about your system directly.