Security vulnerabilities are repeatedly discovered in any major software and made public every few weeks. Once published, they can be found and exploited in a targeted manner or via automated, widespread scans.

Therefore, it is essential - especially since before GDPR - to always use a TYPO3 version that is still officially supported (“under support”): only then can newly discovered security vulnerabilities be closed, thereby preventing risks to your website and your users.

Beyond reducing security risks, upgrading to a more current version naturally offers many additional benefits, such as functional improvements, access to modern extension modules, and significantly enhanced usability.

What are the “lifetimes” of the various versions?

To avoid having to switch to a new version too frequently, TYPO3 should generally be used in a so-called “Long Term Support” (LTS) version, whose lifecycle spans several years.

In addition, the TYPO3 project offers a (paid) extended maintenance period, usually for up to three more years - more information on this below.

However, even these cycles eventually end, namely:

We are happy to offer you the “OwnSaaS” option: A monthly flat rate that covers not only operation, etc., but also all updates and version upgrades.

The full convenience of SaaS - yet first-party, with complete data sovereignty and freedom!

What does “Paid Extension of Software Maintenance” mean?

For users who did not manage to migrate to a current version in time, the TYPO3 project offers a paid Extended Software Maintenance (“Extended Long Term Support”, eLTS) that provides security updates. Details and pricing can be found here:
https://typo3.com/products/extended-support

If desired, we can handle the commissioning and administration for our customers. (In general, however, we recommend aiming for a timely upgrade, since migration challenges do not get smaller as versions age!)

Should I combine a version upgrade with a relaunch?

This is definitely worth considering: for many customers, combining the two has proven to be an effective and efficient strategy to minimize work, operational limitations, and costs.

Can I skip versions - for example, upgrade from v11 to v13?

Yes - however, in this scenario, you should either act very quickly or additionally use Extended Software Maintenance (eLTS) for TYPO3 so as not to go without security updates for many months.

Otherwise, this approach is indeed interesting for many users, as it extends the lifecycle and can save time and money.

Please keep in mind:

• You will go without the conveniences and functional improvements that each new LTS version brings for a long time.
• The technical effort to upgrade to the version after next is generally not significantly lower than migrating twice to the direct successor - the main savings are organizational.

What changes from version to version?

As you might guess: “It depends.”

TYPO3 version 9 introduced, among other things, new front-end editing, site management, URL and redirect handling, and much more.

With version 10, TYPO3 received an extensible dashboard as well as a new template handling system and a new email API for developers.

Version 11 focused particularly on usability and accessibility for editors, along with unified authentication and much more.

In version 12, TYPO3 became noticeably more efficient to use in many areas - focusing on productivity, but also on performance and seamless integration.

For TYPO3 version 13, the spotlight was on API accessibility, as well as further productivity gains, including in basic configuration and the introduction of new content types.

How does the upgrade work, and what does it cost?

This depends heavily on the specific situation - the versions involved, the technologies and extensions currently in use, the frequency of editorial changes, and more.

Typically, the upgrade is tested first on a copy of the system, and any necessary adjustments and transfer procedures are developed and validated. The exact process is always tailored to your specific requirements.

The effort usually amounts to a few days, although this may increase, for example, if many custom extensions need adaptation.

Should I upgrade sooner or later?

The most important advice: Don’t wait until the “last minute.”
Even if you intend to upgrade late, please begin planning (especially scheduling) early to avoid bottlenecks during implementation.

In general, it is advisable to upgrade to the targeted LTS version early (a few months after release). This gives you stable software, allows you to benefit from the latest improvements, and lets you make optimal use of the LTS lifecycle - saving money and effort.

One final note: When using an old TYPO3 version, the server platform can also become “outdated.” That means the operating system (e.g., Ubuntu) may incur additional costs for extended maintenance, or a platform change may be required - along with necessary TYPO3 adjustments (e.g., due to a new PHP version).