TYPO3 Update
secure and plannable

A TYPO3 update affects much more than the version number in the backend. Core, Composer dependencies, PHP, database, extensions, site package, TypoScript, templates, permissions, forms, and external integrations are interconnected. Waldbyte therefore plans TYPO3 updates as a controlled technical change with a clear assessment, test environment, and approval process.

Technical inventory before the TYPO3 update

We start by recording the TYPO3 and PHP versions, hosting, deployment process, database, installed extensions, custom development, scheduler tasks, integrations, and known issues. We also identify business-critical functions and content or URLs that must remain available. This produces a realistic upgrade path rather than a generic version promise.

Upgrade path and dependencies

Older installations may require several technical intermediate steps. The core is only part of the picture: unmaintained extensions, deprecated APIs, custom TypoScript, and previous integration decisions determine effort and risk. We prioritize blockers and clarify which components should be upgraded, replaced, or redeveloped cleanly.

Review extensions and the custom site package

Before the upgrade, we assess public and custom extensions, templates, content elements, and backend configuration. Abandoned extensions are not carried forward without review. Where appropriate, we use current core functionality or maintained alternatives. Custom code is adapted so maintenance and later upgrades remain transparent.

Staging, testing, and approval

The update is prepared outside the live system. In staging, we test the frontend, backend, forms, search, protected areas, languages, redirects, integrations, caching, and editorial workflows. Agreed acceptance points make it clear which functions must be approved before go-live.

Protect SEO and existing URLs

A technical update must not unintentionally change important landing pages. We therefore review routing, canonicals, metadata, hreflang, XML sitemap, structured data, redirects, and indexability. If an update includes a relaunch, old and new URLs are mapped systematically. See also our guide to planning a TYPO3 update.

Controlled go-live and rollback plan

Before launch, backups, recovery, the maintenance window, and responsibilities are defined. After deployment, we recheck key page types, forms, logs, redirects, and caches. This keeps the response clear if a step must be reverted or corrected.

Update, migration, or relaunch?

Not every older TYPO3 system should be upgraded unchanged. If the template, content model, or extensions are fundamentally outdated, a TYPO3 migration or planned relaunch may be more economical. We separate required modernization from optional design and feature requests and provide a grounded recommendation.

What we need for an initial assessment

Useful inputs include the current TYPO3 and PHP versions, extension list, hosting information, details of custom development, known issues, and the desired timeframe. Access is only needed once a technical assessment has been agreed.

Frequently asked questions about TYPO3 updates

Can you take over a TYPO3 system developed by another agency? Yes. Before the update, we assess its architecture, dependencies, and available documentation.

Does the website stay online during preparation? Technical work is prepared in a separate environment. The live system is changed only during the agreed maintenance window.

Can custom extensions be retained? Often yes. Their code, APIs, and data model must be reviewed and adapted where necessary.

Related TYPO3 services

See also our TYPO3 agency, TYPO3 support and maintenance, and TYPO3 extension development.