Service 06
TYPO3 Upgrades (new)
Seamless version upgrades: with a migration plan, backup strategy and roll-out during normal operations.
Our upgrade process
No flying blind — every step planned.
Inventory & risk analysis
Inventory of all extensions (TER, custom, third-party), PHP version, database schema, server environment. Assessment: what migrates automatically, and what needs manual work?
Migration plan
Order of steps, schedule, resource requirements, rollback triggers. Everything documented and agreed with your IT and operations teams.
Staging migration
Full migration on an identical staging system. Functional and regression tests, BITV spot check, performance comparison.
Acceptance & approval
Formal acceptance by your IT and editorial team. Checklist, test report, approval documentation.
Production migration
Migration within the scheduled maintenance window, live monitoring straight after go-live, rollback ready. Post-migration support for 4 weeks included.
0+
TYPO3 upgrades
v8 → v13
0
Production outages
in scheduled upgrades
0 wks
Post-migration support
always included
What we bring
Experience that makes the difference.
Extension migration
Migrating custom extensions to the new API — or checking whether a TER alternative makes more sense.
Security audit
The upgrade as an opportunity: review the security configuration and clean up outdated settings.
PHP upgrade
Coordinated PHP version jump (e.g. 7.4 → 8.2) — aligned with your hosting.
Content migration
Database migrations, converting RTE content, optimising image formats.
Editor training
What changes for editors? A short training session and an updated manual.
Upgrade documentation
A complete record of all changes — for your IT documentation and future upgrades.
That depends heavily on the number of custom extensions and the size of the version jump. A typical upgrade (e.g. v11 → v12) with 3–5 custom extensions takes 3–6 weeks, including the staging phase and acceptance. More complex installations (v8 → v12, many custom extensions, legacy code) can take 3–6 months.
No — the preparatory work takes place on the staging system. The actual production migration happens in a short maintenance window (typically 2–4 hours), which we schedule for times with little editorial activity (e.g. Sunday night).
Every upgrade migration has a defined rollback trigger: if critical errors occur within the first hour after go-live, we restore the last backup and go back to the old version. This rollback plan is part of the migration plan and is agreed in advance.