We assess your instance, plan the upgrade path, and ship with clear milestones â including staging, extension compatibility checks, and a rollback plan.
Timeline
v12 LTS: regular support until 30.04.2026, ELTS until 30.04.2029
v13 LTS: regular support until 31.12.2027, ELTS until 31.12.2030
v14 LTS: Release schedule: 14.0 (25.11.2025) â 14.1 (20.01.2026) â 14.2 FeatureâFreeze (31.03.2026) â 14.3 LTS (21.04.2026)
PHP Compatibility Chart
| PHP versions | TYPO3 v14 2024 - 2029 | TYPO3 v13 2023 - 2027 | TYPO3 v12 2021 - 2026 | TYPO3 v11 2020 - 2024 | TYPO3 v10 2019 - 2023 |
|---|---|---|---|---|---|
| PHP 8.5 | Yes | Yes | no | no | no |
| PHP 8.4 | Yes | Yes | Yes | no | no |
| PHP 8.3 | Yes | Yes | Yes | Yes | no |
| PHP 8.2 | Yes | Yes | Yes | Yes | no |
| PHP 8.1 | no | no | Yes | Yes | no |
| PHP 8.0 | no | no | no | Yes | no |
| PHP 7.4 | no | no | no | Yes | Yes |
| PHP 7.3 | no | no | no | no | Yes |
| PHP 7.2 | no | no | no | no | Yes |
| PHP 7.1 | no | no | no | no | no |
| PHP 7.0 | no | no | no | no | no |
Why upgrading now is a smart move
TYPO3 follows a LongâTerm Support cycle: three years of free security/bugfix updates, then optional ELTS for up to three more years. Staying on an unsupported major version increases risk and compliance burden. Upgrading keeps your platform secure, fast, and futureâproof.
What we deliver
(scope)
- Readiness & inventory: Current state, hosting/PHP/DB, Composer/classic, extension inventory, deprecations log/scanner.
- Staging copy & backups: a safe test bed â no live impact.
- Core & extensions: compatibility review, alternatives, Upgrade Wizard & DB Analyzer, reference index.
- Quality assurance: Frontend/Backend tests, editorial workflows, imaging/WebP, caching/perf.
- GoâLive window: content freeze, deploy, rollback plan.
- Aftercare: language packs, caches, monitoring, quick editor briefing.
Transparent effort
A careful upgrade is not a button click â itâs a small project with defined phases.
Typical ranges for a small/medium corporate site (1â3 languages, ~10â25 extensions, standard hosting):
- Readiness & staging (2â4h): copy, configure, deprecations/scan, extension inventory.
- Core + extensions (4â6h): compatibility/alternatives, Upgrade Wizard, DB Analyzer.
- Testing & fixes (3â4h): FE/BE checks, editorial flows, imaging/cache.
- Goâlive & afterwork (2â3h): content freeze, deploy, checks, language packs/caches.
12 months of service included
To lower your operational risk postâupgrade, you get one full year of service:
- Security & patch headsâup aligned with your LTS (incl. ELTS advisories if relevant).
- Monthly âhealth checkâ (short): error logs, caches, status (remote/backend).
- Small tasks allowance: e.g., 1 hour/month for minor fixes (editor Q&A, tiny CSS/text changes, nav items, redirects).
- Bestâeffort incident response for urgent issues.
- Quarterly microâreport (optional): recommended updates & next steps.
Not included (but available on request): larger features, redesigns, deep extension refactoring, thirdâparty integrations.
What influences effort & price?
- Extensions: count, maintenance status, compatibility (replacements/refactoring where needed).
- Templates/Fluid: custom overlays, legacy patterns.
- Integrations: CRM/ERP/shop, auth flows, caching/proxy layers.
- Infrastructure: PHP/database versions, server settings.
- Languages & workflows: multilingual, translation processes.
TYPO3 Upgrade Process
đ 1. Readiness Check & Inventory
- Analysis of the current instance
- Review of extensions, sites, and multidomain setup
- Determining the upgrade strategy (subdomain deployment or local migration)
đ 2. Staging & Backup Setup
- Prepare subdomain or create a local copy
- Full backup of database and files
- Ensure all rollback options are available
đ 3. Core Upgrade & Extension Review
- Update the TYPO3 Core
- Check and adjust extensions as needed
- Prepare SitePackages for the new version
đ 4. Testing & GoâLive Planning
- Functional testing of all pages and extensions
- QA in the staging/local environment
- Create an approval and goâlive release plan
đ 5. Security & PostâLaunch Support
- Review all security updates
- Monitoring and ongoing support
- Client receives clear documentation
Update vs. upgrade â whatâs the difference?
Best time to upgrade?
Weâre on v11/v10 â is that critical?
Weâre on v11/v10 â is that critical?
Those branches are in ELTS: you still get paid security fixes, but no ongoing development. For compliance & futureâreadiness, plan the move to v13/v14. [my.typo3.org]