TYPO3 Release Upgrades

Questions & Answers for Your Update Strategy

Why Upgrade?

Security holes can be found again and again in every major software and they are made public every few weeks. Once published, they can be targeted or exploited by automatic, nationwide scans. Using a TYPO3 version at any time - which is still supported by the official software maintenance ("in support") - is therefore essential: Only then well-known security holes can be removed, thus avoiding threats to your website and also to your users. In addition to avoiding security risks, switching to a more recent version naturally offers many more benefits, such as: functional adjustments, access to state-of-the-art expansion modules, and significantly improved ease of use.

What are the "Lifetimes" of the various Versions?

In order not to have to switch to a new version all too often, you should generally use TYPO3 as a so-called "Long Term Support" (LTS) version whose lifecycle is several years.
But these too have a lifespan, namely:

requires PHP 5.5 or higher
End of public software maintenance: Dec 1st, 2018
(Paid extension available through Dec 1st, 2021)

requires PHP 7.0 or higher
End of public software maintenance: Mar 31st, 2020
(Paid extension available through Mar 31st, 2023)

requires PHP 7.2 or higher 
End of public software maintenance: Oct 31st, 2021

(Paid extension available through Oct 31st, 2024)

requires PHP 7.2 or higher 
End of public software maintenance: Apr 30th, 2023
(Paid extension available through Apr 30th, 2026)

Release scheduled for 5.10.2021
requires PHP 7.4
End of public software maintenance: Oct 31st, 2024
(Paid extension available through Oct 31st, 2027)


Please find the official information at https://typo3.org/typo3-cms/roadmap/

What is "Paid Extension of TYPO3 Software Maintenance"?

For users who have not made the transition to an up-to-date version in a timely manner, the TYPO3 project offers a chargeable extended term support (eLTS), which guarantees security updates. Details and costs for the version 4.5 LTS and higher can be found here:


On request, we can take on the commissioning and processing for our customers. (In general, we recommend, however, to strive for the timely transition, because the switching problems are not going to get smaller with increasingly outdated versions!)

Should I combine Release Change and Relaunch?

This is well worth considering: for many customers, the merger has proven to be a successful and efficient strategy to minimize work, operational limitations, and costs.

Can I skip versions, e.g. upgrade from v7 to v9?

Yes - however, in this scenario, you should use the Extended Term Software Maintenance (eLTS) to avoid being without security for many months.

Otherwise, this mindset is quite interesting for many users, because it extends the life cycle and thus can save money and time.

Please keep in mind: 

  • You will not receive the amenities and functional enhancements that every new LTS version brings for a while.
  • The technical effort for the change to the version after the next version is usually not much lower than the two-time change to the direct successor - so a savings effect arises especially in the organizational area.

What changes between versions?

You guessed it: "That depends."

For example, the change to 6.2 LTS was marked by significant internal modernizations (such as the "FAL" introduction), which were only slightly visible to editors.

The change to TYPO3 7 LTS, however, brings a completely redesigned user interface for example, but again massive internal development.

The latter is driven by version 8 consistently, making TYPO3 more than ever before not only extremely powerful, but also up-to-date and well positioned for the future.

TYPO3 Version 9 stands out due to great front-end editing, site management, URL and redirect handling, and more.

How does the Upgrade Work, and What does it Cost?

It depends very much on the individual case, i.e. on the actual versions, on the techniques and expansion modules used so far, on the frequency of editorial changes and so on.

Usually, the release change is first tested on a copy and any adjustments and transmission methods are developed and tested. In detail, we always adapt the process to your specific requirements.

This can take a few days, however by adjusting many custom extensions this can increase.

Should I Upgrade rather Sooner or rather Later?

Most important advice: Do not wait until "shortly before the end". And even if you want to change later, please get into the (schedule) planning early to avoid bottlenecks during the implementation!

Otherwise, it is always advisable to switch to the intended LTS version at an early stage (a few months after its publication). This gives you stable software, the latest improvements, and the best use of LTS life, saving you both money and work.

Your browser is outdated!

Please update your browser to see this website correct. Update your browser now