TYPO3

Complex TYPO3 upgrades for your client projects

We move your clients' TYPO3 installations to a current LTS release, even when a site is several major versions behind or carries a lot of custom code. As your white-label partner we work in the background, and your agency remains the client's point of contact.

Discuss your upgrade

Why upgrades get complicated

Moving to the next LTS release is usually easy to plan. It gets harder when a site has fallen several major versions behind. The core changes add up, and any one of them can affect code, configuration or templates. The usual problem areas:

  • Extensions that are no longer maintained for newer TYPO3 versions
  • Custom extensions built on core APIs that have since changed or been removed
  • TypoScript, Fluid templates and backend configuration that need rework
  • New requirements for the PHP version and Composer dependencies

The tools we use

The TYPO3 Extension Scanner shows which parts of the code are affected by breaking changes and deprecations. Rector migrates PHP code automatically, and Fractor does the same for TypoScript, FlexForms and Fluid. Anything the tools can't handle, we fix by hand and test.

White-label for your agency

We stay out of sight. Your agency owns the client relationship and we do the technical work, following your repository, your deployment setup and your coding standards.

How an upgrade works

  1. Analysis

    We review the TYPO3 version, extensions, custom code and server environment, and show you where the effort lies.

  2. Plan

    Together we agree on the target version and decide what happens to extensions that have no successor.

  3. Migration

    We update the core, extensions and custom code, run the upgrade wizards and update the database schema.

  4. Testing

    We check frontend, backend and forms on a staging environment. Then your team signs it off.

  5. Go-live

    We support the launch and stay available for fixes afterwards.