Migrating your existing site to TYPO3 v13.4 LTS — with a new template, clean content, and documented paths for every extension.
Is your TYPO3 running on v10, v11, or v12, has the template become bloated, and is the editorial team struggling with Mask fields that no one understands anymore? We’ll handle a relaunch without a big bang: the core, PHP, content system, and template are migrated in parallel, with every step verifiable. Rector automatically handles 80 percent of the code adjustments. We review the rest manually. Dennis Hüttner personally oversees every project. The team handles the implementation.
Migration Tools
A TYPO3 relaunch isn’t a clean slate—it’s a controlled migration with four parallel tracks: Core, PHP, Content System, and Templates. Rector handles most code adjustments automatically. PHPStan ensures type safety as a baseline. No cutover without staging approval.
On the content side: Masks to ContentBlocks, Gridelements to b13 containers, INCLUDE_TYPOSCRIPT to Site Sets. Editors do not lose any content and can continue working during the migration.
# Typo3 core migration: v10/v11/v12 → v13.4 LTS (LTS to LTS) PHP: 7.4/8.1/8.2 → 8.3 or 8.4 # Automation rector: 80% code adjustments automatic phpstan: Baseline · incremental type safety# Content system migration mask: → ContentBlocks (friendsoftypo3/content-blocks) gridelements: → b13/container typoscript: INCLUDE_TYPOSCRIPT → Site Sets (v13) # DevOps local: DDEV (parallel staging environment) deploy: Deployer · Git-based · reproducible ci: GitLab CI · Pre-live checks
Four parallel paths
Four paths, all managed simultaneously — no cutover without a safety net in place for all four.
LTS-to-LTS upgrade: v10 → v12 → v13 or directly v12 → v13. PHP major version: Rector automatically handles 80 percent of the code changes. PHPStan baseline serves as a safety net for the rest.
Mask → ContentBlocks, Gridelements → b13-Container, INCLUDE_TYPOSCRIPT → Site-Sets. Editors won't lose any content and can continue working—we're migrating on the staging environment, not on the live system.
Site Package, forked third-party extensions, and in-house plugins. Each extension has been updated to the v13 API, tested, and documented. If an extension is no longer maintained, we take over the fork.
New Fluid template built with Tailwind CSS, based on your design or a new concept. SEO redirect mapping for all existing URLs, Core Web Vitals baseline, and submission of the sitemap to GSC.
Process
Every TYPO3 relaunch follows the same process. The staging environment runs in parallel—the live system remains untouched until acceptance.
// Step 01 / 4 · Dauer ~ 3–5 days
Extension audit, compatibility check, Composer lock analysis, PHP version check, content management system assessment. Result: realistic time estimates, clear migration path — before committing.
Deliverable · Diagnostic Report with Cost Estimate
Maschinenbau · 615 Inserate
4,5 Tage · Namentlich dokumentiert
Fliegl Fahrzeugbau
Prices
Before we give you a quote: a free migration assessment. We’ll review Composer lock, the extension list, and the site package—and you’ll get an honest assessment of which package best fits your project.
Up to 50 pages, up to 5 custom extensions, v12 → v13, new template, SEO redirect mapping.
Up to 200 pages, up to 20 custom extensions, v11/v10 → v13, content system migration (Mask → ContentBlocks), new template.
Over 200 pages, multilingual, multi-site, unlimited custom extensions, API integrations. Includes 12 months of maintenance.
For individual migration components, extension repairs, and special cases not covered by the packages.
About Dennis
Dennis Hüttner is the CEO of Waterproof Web Wizard GmbH. Since 2007, he has been involved with every major TYPO3 release—from v4 to v13.4 LTS. He understands the architectural decisions behind each version and knows which migration paths work and which don’t. He personally reviews the diagnostics and oversees every go-live. No account manager.
FAQ
Seven direct answers regarding migration paths, costs, risks, and timelines.
Package A (v12 → v13, up to 50 pages): starting at €19,999. Package B (v11/v10 → v13, up to 200 pages): starting at €34,999. Package C (Enterprise, Multi-Site): starting at €59,999 — net prices, fixed price following migration assessment.
A 30-minute consultation + analysis of Composer lock, extension list, and site package. You’ll receive an honest assessment: Package A, B, C, or a special case. Free of charge, with no obligation.
Yes, but not in a single step. v9 → v10 → v12 or v9 → v10 → v13 is possible. The diagnosis will show whether package B or C is a good fit, or whether a custom path makes more sense.
No. We’re migrating in a staging environment. Editors will continue to work in the live system. We’ll synchronize the content before the cutover—the cutover itself takes minutes, not hours.
We review each one individually during the diagnostic phase. We migrate 70–80 percent of them semi-automatically using Rector. The rest are either migrated manually, rewritten, or replaced with a standard extension—depending on the cost-benefit ratio. If an extension is no longer maintained, we take over the fork.
Package A: 4–6 weeks. Package B: 8–12 weeks. Package C: 12–20 weeks. The actual duration depends on the speed of feedback, the complexity of the extension, and the volume of content. We plan realistically—we don’t make promises we can’t keep.
After the 30-day Hypercare period, you can switch to a TYPO3 maintenance retainer (starting at €432/month). Package C includes 12 months of maintenance right out of the box. No pressure—we deliver a clean solution; you decide. Details: TYPO3 Maintenance.
You give us 30 minutes and read-only access to Composer-Lock plus the extension list. We’ll give you an honest assessment: Package A, B, C, or a special case. No obligation.