TYPO3 to Astro migration

Move from TYPO3 to Astro and own your code in every language

No more LTS upgrades stuck on one extension. We rebuild your site in Astro, move the content into Sanity and carry over your page tree, language versions and every URL that ranks today.

  • 50+ B2B SaaS teams trust us
  • 5.0 out of 5 stars
  • 5.0 out of 5 stars
  • 5.0 out of 5 stars
Timeline
8–14 weeksDepending on languages and page tree size.
SEO risk
MediumLanguage paths, slugs and old page IDs get their own redirect rules.
Content
Carried overPage copy, news records, translations, metadata, files
Design and features
RebuiltFluid templates, TypoScript logic, extensions, forms
Price
Fixed priceSet once we have checked every URL.

Why teams switch

Common reasons to leave TYPO3

01

Every LTS upgrade turns into a project

The TYPO3 community maintains each LTS version for three years. After that you upgrade or pay for Extended Long Term Support. If one extension isn't ready, the upgrade waits.

02

Only one person understands the setup

TypoScript, Fluid and custom extensions often live in one agency's or one developer's head. In Astro the site is plain TypeScript that AI agents like Claude or Codex can read and change.

03

Marketing needs to ship faster

A new use-case page or a reworked section sits in the ticket queue. With our AI workflow, your team describes the change, checks the preview and approves it.

04

Data protection needs to stay auditable

Astro ships pages as prebuilt HTML, with no PHP backend exposed to the web. You decide where the site runs, including an EU-based host.

TYPO3 vs. Astro

What changes for your team

CriterionTYPO3Astro
MaintenanceLTS upgrades for core and extensions, plus PHP and server updates at your host.Dependency updates in the repository, with static HTML as the output.
EditingBackend with page tree and content elements, layout changes through templates.Content in Sanity Studio, larger changes through the AI workflow with a preview.
LanguagesLanguages in the site configuration, translations per page and element.Astro i18n routing plus one linked Sanity document per language.
Roles and approvalsBackend user groups with fine-grained rights on pages and fields.Sanity roles, such as Contributor for drafts without publishing rights.
RedirectsRedirects module in the backend, including automatic redirects when a slug changes.Defined in the Astro project and written to the hosting configuration.

TYPO3

  • LTS upgrades for core and extensions, plus PHP and server updates at your host.
  • Backend with page tree and content elements, layout changes through templates.
  • Languages in the site configuration, translations per page and element.
  • Backend user groups with fine-grained rights on pages and fields.
  • Redirects module in the backend, including automatic redirects when a slug changes.

Astro

  • Dependency updates in the repository, with static HTML as the output.
  • Content in Sanity Studio, larger changes through the AI workflow with a preview.
  • Astro i18n routing plus one linked Sanity document per language.
  • Sanity roles, such as Contributor for drafts without publishing rights.
  • Defined in the Astro project and written to the hosting configuration.

What moves

What comes over from TYPO3

We transfer the content. Templates and extensions are rebuilt in the Astro project or replaced by a service.

  • Migrated
  • Partly
  • Rebuilt
  • Replaced
  • Pages and content elements

    Partly

    We carry over the copy stored in tt_content. Text, image and accordion elements become typed blocks in Sanity.

  • News and records

    Migrated

    News items, categories and custom records become their own document types in Sanity, with author and date.

  • Translations

    Migrated

    Each language version becomes its own Sanity document linked to the original, so every language can publish on its own schedule.

  • Files and images

    Partly

    From fileadmin we take only what is in use. We optimize images and keep alt text from the file metadata.

  • Templates and TypoScript

    Rebuilt

    Fluid templates and TypoScript logic become Astro components. Anything computed out of sight gets documented first.

  • Extensions

    Replaced

    Every extension gets an answer: Astro code, an external service, or drop it. Anything without a replacement shows up in the inventory.

  • Forms

    Rebuilt

    Forms from the Form Framework or Powermail are rebuilt and connected to HubSpot or your CRM. We test every submission.

  • User groups

    Replaced

    TYPO3 groups become Sanity roles. We check which roles your Sanity plan includes before we design the content model.

For your marketing

What keeps running for your marketing

Rankings are only one part. We also protect everything your team uses to measure leads and pipeline.

Tracking and attribution

GA4, the tag manager, UTM parameters and conversion events keep running from day one. In Astro tracking scripts load only after consent and do not slow the page. Before launch we compare every event on staging with the old site.

Forms and CRM

We replace Powermail and TYPO3 Form Framework forms with custom forms connected straight to your CRM. Fields, hidden fields for the lead source and the handover to HubSpot, Salesforce or Pipedrive stay the same. We check test leads right in the CRM.

Demo booking

Demo and contact pages, calendars like HubSpot Meetings, Calendly or Chili Piper and your chat stay in place. Old demo URLs from ads, emails and sales decks redirect straight to the new page.

Visibility in AI search

Structured data, clear headings and an up-to-date sitemap are in place from launch. That helps Google and AI search like ChatGPT or Perplexity find your pages again quickly.

Content mapping

How TYPO3 content becomes Sanity documents

In TYPO3In Astro
Page treePage documents with slug and parentyour team manages navigation in Sanity
Content elements (tt_content)Reusable blockseach block has a matching Astro component
News and categoriesDocument types with referencescategory and author as linked documents
Language versionsOne document per languagelinked through Document Internationalization
Page propertiesSEO fields per documenttitle, description, canonical, noindex

Process

How we migrate
your TYPO3 site

An example project: 12 weeks to launch. Afterwards we monitor rankings and redirects for four more weeks.

Migration from TYPO3, example project

path digitalYour team

Your team

Access, sign-offs

SEO

URLs, redirects, tests

Build

Pages, content in Astro

Point at a step to see what happens there.

  1. Week 1 · Your team

    Kickoff

  2. Weeks 1–2 · SEO

    Audit and URL inventory

  3. Weeks 2–3 · SEO

    Redirect plan and content model

  4. Weeks 3–8 · Build

    Components and build

  5. Week 3 · Your team

    Redirect plan sign-off

  6. Weeks 7–10 · Build

    Content migration

  7. Weeks 10–12 · SEO

    SEO parity and QA

  8. Week 12 · Your team

    Launch

  9. After launch · SEO

    Launch and monitoring

Pre-launch checklist

What we check before launch

Stage 1 of 4

Before the build

Stage 2 of 4

During the build

Stage 3 of 4

Before launch

Stage 4 of 4

After launch

To be honest

When you should stay on TYPO3

  • Your team runs TYPO3 well

    If in-house developers handle upgrades as routine and your editors are productive, switching platforms solves no real problem.

  • An intranet, portal or login area depends on it

    If the same installation also runs a customer portal or member area, moving only the marketing site is rarely clean.

  • You want to keep TYPO3 as a headless backend

    The headless extension lets TYPO3 deliver content as JSON to a separate frontend. That can be enough if your editors rely on the backend.

  • Nobody should own code

    Astro needs a development partner for new features. If your team wants to build everything visually on its own, Webflow is the better fit.

Frequently asked questions about migrating from TYPO3 to Astro

What B2B SaaS teams want to know before moving from TYPO3 to Astro.

Is Astro with Sanity a good headless alternative to TYPO3?

For B2B SaaS marketing sites, often yes. Sanity holds the content and Astro turns it into fast pages. If you want to keep TYPO3 as the backend, the headless extension can run TYPO3 headless instead.

How do you handle multiple languages?

Astro's i18n routing defines the languages and URL prefixes. In Sanity, each language version is its own document, linked to the others and published on its own.

Will our editors still have roles and approvals?

Yes. Sanity has roles like Editor, or Contributor, who can write drafts but not publish. Which roles you get depends on your Sanity plan and we check that during the inventory.

What happens to our extensions?

Every extension gets a solution: Astro code, an external service, or drop it. You see the list and the reasoning before the project starts.

Do we still need a developer afterwards?

Not for content, your team manages that in Sanity. Larger changes go through the AI workflow with a preview to approve. New features need a development partner, which can be us or your own team.

Does TYPO3 stay live until launch?

Yes. Your site stays online unchanged until the domain switches. Anything published in the meantime gets transferred before launch.

Plan your migration
from TYPO3 to Astro

Show us your TYPO3 installation. We tell you which content and languages move, which extensions get replaced and how your team works afterwards.