From TYPO3 v9/10/11/12 to v14 LTS —
safely, predictably, with no data loss.
Outdated TYPO3 versions are a security risk and block new features. We migrate your site to the current LTS — with a Composer-based setup, an extension compatibility audit, clean template porting and editor training on the new backend.
Outdated TYPO3 versions are not “it still kind of works”.
Once a TYPO3 version drops out of long-term support, security patches stop. Known vulnerabilities stay open and are actively scanned. PHP version requirements add up: current hosting environments roll out old PHP versions, which leaves outdated TYPO3 sites stranded.
The good news: TYPO3 is built for upgrade paths. With the right tool stack (Composer, Rector, automated tests), a major upgrade is predictable — even across two or three versions.
EOL reached
No more support. Security patches are only available through paid ELTS.
EOL October 2024
Out of regular support. Migration recommended; ELTS available if needed.
LTS until April 2026
Still in support, but plan the v14 migration now.
Current LTS
Site Sets, new backend, native form framework, Composer-centric.
Update stack — from audit to go-live.
Pre-update audit
We analyse your installation: TYPO3 version, extensions, custom code, PHP version, hosting setup. You get a clear update path and a fixed-price range.
Composer migration
If your site still uses the old typo3conf setup, we migrate to Composer-based dependency management — required for v12+ and clean update handling.
Extension compatibility
Every extension is checked for v14 compatibility. Incompatible ones get an upgrade, a replacement or are subsumed by core features (e.g. powermail → cms-form).
Templates & Site Sets
Migration of TypoScript templates to Site Sets, Fluid migration from v3 to v4, deprecation fixes with Rector. Clean foundation for the next two major versions.
Schema and data migration
Database schema updates, cleanup of orphan records (e.g. from uninstalled extensions), data migrations where needed. Content is left untouched.
Editor training
The v14 backend looks different. We train your editors in two 90-minute sessions and provide a written quick reference.
What decision-makers ask about updates.
How long does a TYPO3 major upgrade take?
Typically 4–12 weeks, depending on site size, number of extensions and amount of custom code. Jumps across multiple major versions (e.g. v9 → v14) run in two stages with extra time for the Composer migration.
What happens to our extensions?
During the audit we check each extension. Three buckets: (1) v14-compatible — just update. (2) v14 update available — bring it along. (3) Incompatible — either code adjustment, replacement or functionality is now in core. You receive a recommendation per extension.
Will the site be offline during the update?
No. We work on a staging system. Only when all tests are green do we cut over — typically a 30–60-minute maintenance window, outside business hours.
What does an update cost?
Smaller sites (1–2 languages, few extensions): from about 4,000 euros. Typical institutional portals: 8,000–25,000 euros. Large multi-tenant setups: 30,000+ euros. After the audit we name a fixed price.
What if our previous agency is gone?
We regularly take over “orphaned” TYPO3 sites: code and infrastructure audit, documentation of the legacy site, update to current security level. TYPO3 is open source — any professional TYPO3 agency can take over at any time.
Tell us where you stand — and we’ll show you the path to v14.
30-minute call, an initial update audit, a realistic picture of effort and sequence.