Since 2007 · v4 through v13.4 LTS · Fixed price following analysis · Limited liability · v12 EOL April 2026 · Secure slot capacity

TYPO3 v13 Upgrade — Migrated Smoothly, Tested in Production

TYPO3 v13.4 LTS upgrade from v10, v11, or v12. Three fixed-price packages: €4,999 / €11,999 / €24,999 (excl. tax). 4-phase process with staging acceptance. v12 EOL April 2026 — Secure your slot capacity.

Is your TYPO3 installation still running on v10, v11, or v12? Then it’s time: TYPO3 v13.4 LTS has been available since October 15, 2024, and will receive security updates through October 2027. Older versions are gradually losing official support—and with it, security patches. Anyone still running TYPO3 v10 in production has been operating without official TYPO3 updates since April 2023.

We’ll handle your TYPO3 upgrade: analysis, migration, testing, go-live. Dennis Hüttner personally leads the project. The team handles the implementation. We’ve worked with every TYPO3 version since v4—no surprises, no flying blind.

Since 2007 · Every version from v4 to v13.4 LTS 32 long-term customer partnerships Fixed price after analysis · guaranteed v12 EOL April 2026 — book now LLC · NDA-compliant · Code Rescue in case of emergency
TYPO3 v13 Upgrade — Fixed price: €4,999 / €11,999 / €24,999; v12 EOL: April 2026
TYPO3 v13.4 LTS Upgrade · Fixed Price · Staging Tests

Upgrade Pre-Check

Was wir vor dem Upgrade prüfen

No upgrade is undertaken blindly. Before migrating a single line of code, we analyze the source version, PHP environment, extension compatibility, and custom code. The result: a documented migration plan that outlines the specific effort required and potential risks.

// upgrade-check.yaml
# Pre-check
extensions:
Check compatibility of all installed extensions
php:
        PHP 8.2+ required starting with v13
typoScript:
Check for deprecated conditions and syntax

# Backup before starting
backup:
     DB + fileadmin + composer.lock
staging:
    Set up an isolated upgrade environment
Repository · private STATUS · PRE-CHECK

What's new in TYPO3 v13.4 LTS?

The current TYPO3 LTS version is not just a cosmetic update. v13.4 introduces changes that will affect both the architecture and day-to-day operations:

  • PHP 8.2+ is required. No more PHP 7.4, no PHP 8.0. Hosting must be set up correctly before the upgrade begins
  • PSR-14 events replace old hooks. Anyone still using $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS'] must make adjustments
  • Middleware-based request handling. Fully PSR-15 compliant. Custom request manipulations must be migrated
  • Content Blocks as a core feature. Stable as a core component since v13.2 — content elements without a custom extension
  • Improved backend UX. Streamlined navigation, faster backend load times, better accessibility
  • File Abstraction Layer improvements. Better performance with large file collections
  • Expanded CLI tools. More operations via the command line — relevant for deployment pipelines and CI/CD
  • Drag-and-drop in the Page module for faster editorial workflows

Upgrade paths

Four routes to V13

The migration effort depends on the source version and the extension landscape.

01

v12 → v13 (most direct path)

Deprecations have been removed from v12 — if you’ve followed best practices in v12, you’ll have very little to adjust. Check extension compatibility, address deprecation warnings, and update the PHP version. 1–3 weeks.

02

v11 → v13 (two LTS jumps)

Architectural changes in v12 (Fluid Standalone, TCA migration) and v13 combined. Custom extensions: Adaptations to TCA, TypoScript syntax, and event handling. For complex extension bases, an intermediate step via v12 is recommended. 3–6 weeks.

03

v10 → v13 (three major versions)

v10 EOL April 2023 — no security updates. Three-version jump: Doctrine DBAL, Fluid Templates, TypoScript conditions, extension APIs. Thorough analysis required. 4–8 weeks.

Upgrade process

Four phases until go-live

No upgrade without an analysis, no go-live without staging acceptance.

// Step 01 / 4 · Dauer ~ 1–2 weeks

Analysis

Assessment: TYPO3 version, PHP version, list of extensions, custom code, TypoScript setup, hosting environment. Each extension was checked for v13 compatibility—even those that “probably still work.” Result: a documented migration plan with specific costs and risks.

  • Extension Compatibility List
  • PHP Version Check
  • Risk Assessment of Custom Code

Deliverable · Migration Plan Document

Stumbling blocks

Three common obstacles

What causes work in almost every upgrade—and what we systematically check during the analysis phase.

01

Extension compatibility

Most common roadblock. Third-party extensions that do not support v13 must be replaced, forked, or superseded by custom solutions. Custom extensions require updates to comply with PSR-14 and updated TCA.

02

Deprecations + Breaking Changes

What appeared as a deprecation warning in the log in v12 has been removed in v13. TypoScript conditions, TCA configurations, backend modules, signal/slot registrations—all are affected.

03

PHP Version + Hosting

v13 requires PHP 8.2 or later. Some hosting environments are still running PHP 8.0 or older. Composer dependencies break during PHP upgrades. Let’s address this in Phase 1 before migrating the first line of code.

Project example: v11 → v13 standard upgrade

B2B service provider · 14 extensions
· 4 weeks · Fixed price: €6,800 ·
Anonymized

Background

  • TYPO3 v11.5 LTS has been in production since 2022
  • 85 pages, 8 custom + 6 third-party extensions
  • Hosting PHP 8.1
  • In-house dev team with limited v13 experience
  • Goal: Upgrade before v11 LTS expiration (Oct. 2026)

What we did (4 weeks)

  • Phase 1 Analysis (8 hours): 14 extensions checked for v13 compatibility; 3 lacked v13 support (2 replaced, 1 forked in-house)
  • Phase 2 Migration (25 hours): Staging setup, PHP upgraded to 8.2, core upgrade, custom extensions updated to PSR-14, TCA migrations, 4 TypoScript condition rewrites
  • Phase 3 Testing (10 hours): Internal QA + customer team testing over 5 business days, 3 fixes
  • Phase 4 Go-Live (6 hours): Saturday night deployment, DB migration, cache warm-up, 48-hour monitoring

Result

2 ×
Backend performance feels faster
15% off
Front-end load time (PHP 8.2 + cache)
0%
Plummet in the rankings after 4 weeks
Even
Internal Dev Team Now v13-Ready

We do not disclose full names or company names (confidentiality agreement).

Fixed-price packages

Ranked by complexity

No hidden time charges. Before any fixed-price quote: a free 30-minute migration assessment with a cost estimate. Goldrausch Note: v12 EOL April 2026 — Slot capacity in the DACH market will become scarce starting in Q3 2026.

Package 01
Package A (v12 → v13)
Shortest path

Up to 50 pages, up to 5 custom extensions. The most direct approach with minimal customization.

4.999 €einmalig
NET · 2 WEEKS
  • TYPO3 Core Migration: LTS to LTS
  • Major PHP version jump to 8.3 or 8.4
  • Rector migration for custom code
  • PHPStan Baseline with Coverage Report
  • 30-Day Hypercare After Go-Live
Up to 50 pages · up to 5 custom extensions
Request Package A →
Package 02
Package B (v11 → v13)
Most Popular

50–200 pages, up to 20 custom extensions. Plus Mask→Content Blocks and Gridelements→b13/container.

11.999 €einmalig
NET · 4 WEEKS
  • Everything from Package A
  • Mask → Content Blocks Migration
  • Grid elements → b13/container
  • Up to 20 custom extensions migrated
  • Multilingual Migration (Basic)
  • GitLab CI Setup with Pre-Release Checks
  • Editor Training (online, 2 hours)
50–200 pages · up to 20 custom extensions
Request Package B →
Package 03
Package C (v10 → v13)
Enterprise

Over 200 pages, multilingual, multiple brands. Includes multi-site setup and migration, plus 12 months of maintenance.

24.999 €einmalig
NET · 8 WEEKS
  • Everything from Package B
  • Unlimited custom extension migration
  • Multilingual Migration (full)
  • Multi-site setup migration
  • Editor Training (online, 4 hours)
  • 12-month maintenance contract included
  • 30-Day Hypercare After Go-Live
200+ pages · Multi-site · International
Discuss Package C →
Package 04
Special Cases: Hourly Basis
Custom

v8/v9 migrations with checkpoints, highly complex multi-site setups, emergency forks. Priced on a case-by-case basis.

108 €/Stunde
NET · 15-MINUTE BLOCKS
  • 15-minute billing intervals
  • Checkpoint Migration v8/v9 → v10/v11 → v13
  • Emergency forks for missing extensions
  • Personal Migration Plan
v8/v9 · Emergency forks · Special cases
Request a diagnosis →
Special Cases: Hourly Basis Highly complex multi-site setups, emergency forks, v8/v9 migrations with checkpoints — custom pricing based on the diagnosis. €108/hour (net) in 15-minute increments.

Upgrade Commitment

Fixed price guaranteed after analysis

After the analysis phase, we guarantee the quoted fixed price: We—not you—will cover any additional costs resulting from issues not identified during the analysis (such as third-party extensions that fail during staging migration). This is specified in the contract.

No guarantees regarding rankings, performance, or traffic after the upgrade—that would be unprofessional. We guarantee clean code, staging before go-live, and a fixed price following an analysis.

// FIXED-PRICE GUARANTEE
Zusatz
for any issues not detected during analysis
In writing · set forth in a contract
Dennis Hüttner — TYPO3 v13 Upgrade Specialist, Founder of Waterproof Web Wizard GmbH
Dennis Hüttner · TYPO3 v13 Upgrade

About Dennis

Dennis Hüttner personally oversees every upgrade

Dennis Hüttner is the CEO of Waterproof Web Wizard GmbH. He has been working with TYPO3 since 2007—from version 4.x to the current version 13.4 LTS. He personally reviews every extension analysis, determines the migration path, and oversees every go-live personally (together with the team).

FAQ

Frequently Asked Questions About the TYPO3 v13 Upgrade

Four direct answers regarding effort, downtime, costs, and EOL.

How long does a TYPO3 v13 upgrade take?

v12 → v13: 1–3 weeks. v11 → v13: 3–6 weeks. v10 → v13: 4–8 weeks. v9 or older: 6–12 weeks with Checkpoint migration. Exact time required will be determined after the analysis phase.

Will there be any downtime during the go-live?

With proper preparation, the DNS switch window is typically less than 30 minutes. We deploy on Saturday night or during an agreed-upon maintenance window. Staging tests ensure that the live deployment goes smoothly.

What if my extensions aren't compatible with v13?

Identified during the analysis phase. Three options: 1) Replace the extension with a v13-compatible alternative, 2) Fork the extension and maintain it ourselves, 3) Develop our own custom solution. We recommend the best option based on the effort required for the extension.

When will v12 actually expire?

v12 will lose free community support in April 2026. ELTS (Extended LTS) will be available until 2027—but at an additional cost (typically €4,000–8,000 per year, depending on the provider). Slot capacity for v13 upgrades starting in Q3 2026 will be limited in the DACH market.

Migration Assessment

Free 30-minute diagnosis

Before any quote: a free 30-minute assessment with a cost estimate. You’ll know in advance which package and the approximate cost.

Fixed price starting at €4,999 Gold Rush Q2–Q4 2026 30-Day Hypercare