TYPO 3 - the Upgrade!?!

We assess your instance, plan the upgrade path, and ship with clear milestones — including staging, extension compatibility checks, and a rollback plan.

Request a free upgrade assessment

Timeline

(overview):

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)

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.

What you gain (for editors & IT)

  • More productive backend UX: modernized UI, dark mode, reactive page tree (v13/v14) — quicker daily work. 
  • Future‑proof stack: modern PHP, cleaned‑up core, transparent roadmap. 
  • Lower complexity: fewer legacy knobs in core; better stability in deployments.

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):

  1. Readiness & staging (2–4h): copy, configure, deprecations/scan, extension inventory.
  2. Core + extensions (4–6h): compatibility/alternatives, Upgrade Wizard, DB Analyzer. 
  3. Testing & fixes (3–4h): FE/BE checks, editorial flows, imaging/cache.
  4. 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

Upgrade Process

FAQ

Update vs. upgrade — what’s the difference?
Update vs. upgrade — what’s the difference?
  • An update moves between minor versions in the same major (e.g., 13.4.23 → 13.4.26). 
  • An upgrade moves between major versions (e.g., v12 → v13/v14) 
  • and may include breaking changes — hence staging & tests.
Best time to upgrade?
Best time to upgrade?

At Feature Freeze or LTS release for the new major — functionality is stable, most extensions are aligned.

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]

How long does it take?
How long does it take?

For small/medium sites: a few workdays end‑to‑end including test cycles. 

We provide a firm plan after the free assessment.

Fields: Name, Email, Current TYPO3 Version (or “not sure”), Notes (extensions/languages/integrations).

You’ll receive a work estimate, risk flags, and a milestone plan — no obligation.

Request your free upgrade assessment