Move your TYPO3 site
to a headless stack.

We migrate TYPO3 sites to a modern headless setup. Your URLs and translations carry over, your editors get out from under the backend, and your developers stop writing TypoScript. No more six-figure LTS upgrades, no more extensions that break on every major version, no more Fluid templates nobody else can read.

Let's talk See if we're a fit

Trusted by

TYPO3 was the safe choice. It is not anymore.

TYPO3 ran the DACH corporate web for a long time. Structured, multilingual, enterprise-ready. It still does most of that. But the cost of staying on it has crept up to the point where the next LTS upgrade looks a lot like a rebuild, and the rebuild looks a lot like the right time to leave the platform behind.

Every layout change starts with a TypoScript ticket and ends a week later.

Each LTS upgrade is a separate project with its own budget conversation.

Half your extensions break on the next major version and nobody owns them anymore.

The backend still scares editors who have used it for years.

Frontend rendering is slow and the cache configuration has become its own subsystem.

The agency that built it uses TYPO3 because they always have, not because it still fits.

The Reality

The platform is not the problem. The accumulated cost of staying on it is. Replatforming separates the content from the platform.

What Survives the Move

Your content and translations come along.

TYPO3's strength is structured multilingual content, and that is the part worth preserving. Page tree, language records, content elements, URL slugs all carry over. The migration is in the platform underneath, not in the editorial structure your team already knows.

  • Your content

    every page, every content element, every news record. Exported through the database or the TYPO3 export format and re-imported into a structured content model.

  • Your URLs

    RealURL, CoolURI, and the modern slug-based routing all get mapped. Localized URL segments are preserved per language.

  • Your multilingual structure

    sys_language records and translated content move into native multi-locale fields with proper hreflang in place.

  • Your page tree

    the hierarchy your editors know becomes a structured content tree in the new CMS. Categories and tags carry across.

  • Your media library

    fileadmin contents, FAL records, and image references move to a CDN with responsive derivatives generated automatically.

What Changes

The TYPO3 layer goes away.

Most of what makes a TYPO3 site hard to maintain is platform plumbing. TypoScript, Fluid, the extension graph, the backend. They go away. What replaces them is built around how editors and developers actually want to work, not around how TYPO3 happens to organize the world.

  • TypoScript

    is gone. Configuration that lived in nested object syntax becomes either CMS settings editors can change or code in version control developers can review.

  • Fluid templates

    become frontend components in Astro. The same content elements render, but the templates live next to the rest of the codebase, not in a separate templating engine.

  • Extensions

    either get replaced by features built into the new CMS, rebuilt as small services, or dropped if nobody uses them anymore. The extension dependency graph stops being a maintenance problem.

  • The backend

    is gone. No more module navigation, no more Page TS Config, no more Form Framework. Editors get a CMS designed for editors, not a system administrator's tool.

  • PHP and MySQL

    go away. The new site is static or server-rendered, served from a CDN. No more LAMP stack, no more cache rebuilds, no more scheduler tasks.

How It Works

The migration process

1

Audit and content model

We export the database, walk through the page tree, every content element type, every TypoScript constant set, and every active extension. Then we design the content model around how your editors actually publish, not around how the install grew over the years. You approve the model before development starts.

2

Migrate, translate, rebuild

We export content through the database or the TYPO3 export format and import it into Storyblok or DatoCMS. The frontend is rebuilt in Astro, with components replacing Fluid templates. Multilingual content is mapped to native multi-locale fields with hreflang configured from the first deploy. URL slug logic is reproduced per language so old links still resolve.

3

Cutover and 30 days of watching

We launch on a low-traffic window, swap DNS, and monitor Search Console, Analytics, and Core Web Vitals for 30 days. TYPO3 stays running as a fallback during the watch window. After 30 days you decide whether to keep us on with a subscription or take it from here.

A note on extensions

Most TYPO3 extensions are platform-shaped solutions to platform-shaped problems.

The news system, the powermail forms, the various SEO extensions, half of them have built-in equivalents in a modern stack. The other half were workarounds for backend limitations. We list every active extension at the audit stage and decide which ones translate, which ones get dropped, and which ones need a small custom service.

Start with an audit

Pricing

Fixed price, no scope creep

TYPO3 migrations vary in scope more than most. A 100-page corporate site with three languages and a clean install is one thing. A large-scale corporate site with deep TypoScript, dozens of extensions, and a decade of accumulated content elements is another. The ranges below are where typical projects land. Once we scope yours, you get a fixed quote.

Migration project
€ 30.000 — € 75.000 fixed price

  • Full audit of your TYPO3 install, extensions, and content

  • Content model rebuilt around your editorial workflow

  • URL map covering RealURL, CoolURI, and slug-based routing

  • Content migration from database export or TYPO3 export format

  • Frontend in Astro, CMS in Storyblok or DatoCMS

  • Multilingual with hreflang from day one

  • 30 days of post-launch monitoring

Ongoing subscription
€ 1.500 — € 3.500 per month (optional)

  • Same team stays accountable for the system

  • Performance and uptime monitored continuously

  • Content and component changes handled monthly

All prices are net, excluding applicable VAT.

Who This Is For

Who this is for

This works well if you

  • Run a corporate or institutional TYPO3 site built somewhere between TYPO3 8 and 12

  • Are looking at the next LTS upgrade and the quote came back close to a rebuild anyway

  • Manage multilingual content across DACH or EU markets and want this stable, not patched together

  • Want editors to stop fearing the backend without retraining them on something just as dense

  • Need a fixed-price migration with a clear scope, not a multi-year time-and-materials engagement

  • Have a team comfortable with code-first frontends rather than Fluid templates

This is not a fit if you

  • Run a government or regulated site with hard requirements that depend on TYPO3-specific extensions or accessibility certifications. Talk to us first

  • Use TYPO3 as a central data hub with custom backend logic that needs to stay in TYPO3. The frontend can still go headless, scope is different

  • Have a small TYPO3 install where the cost of migration outweighs the gain

  • Are not sure yet what the right move is. Start with a Headless Audit

  • Need a new build from scratch with no legacy content. See Headless Website

If your website has become a bottleneck, let’s talk!

Let's talk Or email me directly