Upgrade calculator BETA

TYPO3 Upgrade Analyser and Cost Calculator

Check the complexity, expected effort and estimated cost of your TYPO3 upgrade. Enter your TYPO3 versions and extensions to receive an initial project assessment based on our experience with more than 70 upgrades per year.

Your TYPO3 upgrade
Contact (optional)
TYPO3 upgrade guide

What does a TYPO3 upgrade cost?

The cost of a TYPO3 upgrade depends on how far you jump between versions, how many extensions you run and how much custom code needs porting. A small, well-maintained site can be upgraded in a few days, while a large multisite installation with custom extensions can take several weeks. This TYPO3 upgrade calculator turns those factors into a transparent effort and cost range, so you can budget the TYPO3 upgrade cost before committing to a full project.

TYPO3 upgrade serviceFixed-price TYPO3 upgrades

What does the TYPO3 Upgrade Analyser check?

The analyser reviews the inputs that most influence a TYPO3 upgrade estimate:

  • Current and target TYPO3 versions
  • Number of major-version steps
  • TER and Packagist extension compatibility
  • Unsupported and custom extensions
  • Installation size
  • Number of sites and domains
  • Custom backend modules
  • Additional testing effort

How is the TYPO3 upgrade effort estimated?

Every extension you enter is checked against the TER and Packagist to see whether a release already supports your target version. Compatible extensions add little effort; unsupported or custom extensions are estimated at a fixed porting effort each. On top of the extensions, the estimate adds effort per major-version step, a testing budget scaled to your installation size, and extra time for additional sites or custom backend modules. The result is an effort range and a TYPO3 upgrade estimate at our standard rate.

How we automate TYPO3 upgradesSeparating code and database migration

Which factors increase upgrade complexity?

Complexity rises with the version distance (for example TYPO3 8.7 to v14 crosses many breaking changes), the number of custom or unmaintained extensions, heavy TypoScript and Fluid customisation, integrations with third-party systems, and large editorial installations with many sites and languages. Extensions that have been replaced in newer versions — such as gridelements by EXT:container or mask by Content Blocks — add migration effort even when a direct successor exists.

TYPO3 extension compatibility

Extension compatibility is usually the biggest variable in a TYPO3 upgrade. The analyser looks up each extension key and Composer package to determine whether a version compatible with your target TYPO3 release exists. Extensions with no compatible release are treated as custom work that must be ported or replaced. Some vendors — for example the in2code extensions powermail and femanager — ship early TYPO3 support through an Early Access Program, which the analyser flags where relevant.

Planning a TYPO3 v14 upgrade

TYPO3 v14 LTS is the current long-term-support target for most upgrades. If you are still on TYPO3 11, 12 or 13, planning a v14 upgrade now keeps you on a supported version and lets you budget the work in one step. Enter your current version and TYPO3 v14 as the target above to see the expected effort and cost for your installation.

Case study: DRK Kliniken TYPO3 upgrades

Calculator versus complete source-code analysis

This is a fast preliminary estimate. It does not inspect your source code, TypoScript, Fluid templates, deprecations or the database, so treat the result as a planning figure rather than a fixed quote. A complete TYPO3 upgrade audit is a separate service that may additionally use Rector, Fractor, the TYPO3 Extension Scanner and manual code review to find deprecations and breaking changes. This calculator is an independent Digital Zombies tool, not a source-code analyzer.

Frequently asked questions

How much does a TYPO3 upgrade cost?
A TYPO3 upgrade typically costs from a few days of work for a small, well-maintained site to several weeks for a large multisite installation with custom extensions. The exact cost depends on the version distance, extension compatibility and installation size. Use the calculator above for an initial cost range.
How long does a TYPO3 upgrade take?
Most upgrades take between a few days and several weeks. A single-step upgrade of a small site is quick; jumping several major versions, porting custom extensions and testing a large installation takes longer. The calculator shows an effort range in hours.
How accurate is the estimate?
The estimate is a fast preliminary figure based on your inputs and public extension data. It is accurate enough for budgeting and comparison, but it is not a fixed quote — a binding offer follows a short review of your actual code and configuration.
Which factors affect TYPO3 upgrade costs?
The main cost factors are the number of major-version steps, the number and compatibility of your extensions, unsupported or custom extensions, installation size, the number of sites and domains, custom backend modules and the required testing effort.
Can I calculate the cost of an upgrade to TYPO3 v14?
Yes. Select your current version and TYPO3 v14 as the target, add your extensions, and the calculator returns the expected effort and estimated cost for a TYPO3 v14 upgrade.
How are TYPO3 extensions checked?
Each extension key is checked against the TYPO3 Extension Repository (TER) and each Composer package against Packagist to see whether a release supports your target version. Extensions without a compatible release are treated as porting work.
Can the analyser check custom extensions?
Custom and private extensions are not published in the TER or on Packagist, so they cannot be verified automatically. The calculator estimates them conservatively as porting work; a full audit reviews their code individually.
Does the analyser inspect source code?
No. This calculator does not read your source code, TypoScript, Fluid templates or database. It estimates effort from your version, extension list and installation details. A complete source-code audit is a separate service.
Is uploading composer.json safe?
Yes. If you upload a composer.json, we only read the list of required extensions to check their compatibility. We do not store the file itself, and development dependencies, core packages and libraries are ignored.