The Ultimate TYPO3 Update/Upgrade to Version 13
TYPO3 update/upgrade is one of the most crucial tasks for TYPO3 Agency and developers. In my long journey of TYPO3 (since 2011), I’ve developed numerous websites (Medium to Large-scale), TYPO3 upgrade from old-school version 4.x to modern agency 10.x, 11.x, 12.x, and 13.x.
Here, I would like to share my experience, which will help beginners to expert-level TYPO3 developers and TYPO3 Agencies, even with TYPO3 version 12 and TYPO3 version 13. After reading this blog, I’m sure you will have enough knowledge to perform the TYPO3 upgrade well, and your client will be more than happy.
What is TYPO3 Update/Upgrade?
As simple as it seems, a TYPO3 update, also known as an upgrade, is the process of renewing your current TYPO3 content management system (CMS) software to a higher version with improved features and functionalities, with or without the help of a TYPO3 WEB AGENCY.
The primary purpose of the TYPO3 update is to make life easier for TYPO3 users by adding new features and improving website security. In addition, a TYPO3 update is very important for your website’s cross-device performance. You will lose significant traffic if your website is not optimized for mobile devices. Updating your current TYPO3 version to a new one can increase your website's mobile suitability and performance, which also helps reduce loading time.
TYPO3 CMS Roadmap
TYPO3 is well-known for being pre-planned, creating a roadmap, and strictly following the deadline to continuously release the next TYPO3 versions.
You can find all the information related to new versions of TYPO3 CMS from the TYPO3 CMS roadmap below. Now that the TYPO3 version is approaching, let’s glimpse it.
TYPO3 version 14 Roadmap
| Version | Date | Milestone |
| 14.0 | 25 November 2025 | Breaking Changes |
| 14.1 | 20 January 2026 | Feature Integration |
| 14.2 | 31 March 2026 | Feature Freeze |
| 14.3 | 21 April 2026 | LTS Final Release |
What is the current TYPO3 version?
The current TYPO3 version is TYPO3 v13 LTS, released in October 2024. This version brings new improvements in security, usability, and customization options, including enhanced backend UX with features like a reactive page/file tree, streamlined bulk editing, and an upgraded Fluid template engine.
TYPO3 update version categorization
TYPO3 update can be categorized into two major categories as follows:
Option 1: Updates
This means you must plan to update TYPO3 from one LTS (Long Term Support) version to the next.
If you have a TYPO3 website with TYPO3 9.x LTS, consider updating to the latest TYPO3 13.x LTS. Updating TYPO3 can be challenging and complex, depending on the site's structure and the number of installed extensions.
Option 2: Website Relaunch
Sometimes, it's recommended that the website be relaunched instead of completely updating TYPO3. Relaunch means a brand-new website development.
Did you know?
“TYPO3 is the only open source content management system with a vendor-level warranty.”
TYPO3 Relaunch or TYPO3 Upgrade?
You might be confused when choosing between TYPO3 Relaunch and TYPO3 Upgrade. Many factors can lead to a relaunch or update as follows:
- TYPO3 update from 4.x to 13.x with very complex and old-school techniques?
- Is your TYPO3 website responsive?
- Does your website perform well? E.g., SEO, Industry standards, etc.
- Do you want a modern look for your new website?
- Are you facing a major issue with speed & performance?
- Does your existing site have outdated code & techniques?
- Are the estimation efforts of the Major update and Relaunch almost the same?
Check out the concluding factors to help you decide whether to relaunch or update your TYPO3 website. Study them and choose wisely :)
Website Security
If you need regular updates, it gives the best protection against bugs. For support dates, you can check the roadmap of TYPO3 CMS.
Website Appearance
If the website is incompatible with all devices and has an old-fashioned, primitive look, it might look good on some devices, but it will give your visitors an unpleasant experience. When this is the case, relaunching or switching to a responsive design is often the best idea.
Ease of Use
Every upgrade brings a better user experience and exciting new features. TYPO3 CMS sites are easy to control, manage, and create workflow and content, so upgrading makes complete sense.
Site Performance
Search engine rankings play a significant role in building visitors' trust. According to Google’s algorithm, these ranks depend upon the load time of the site pages, so improve performance and rankings by making the site responsive and fast.
Did you know?
TYPO3 is the only open source CMS that provides Vendor-based Support!
TYPO3 CMS has its own set of unique advantages and features, so making the switch is practical. This upgrade gives you extra Extended Long-Term Support at the end of the 3-year regular support cycle, resulting in longer validity and support.
Let’s understand it with an example: with the end of the TYPO3 support cycle and the launch of TYPO3 11, community support was discontinued for security fixes. The users had the option to,
- Upgrade
- Relaunch
- Purchase ELTS for the current version
ELTS offers compatibility fixes and security updates for 24 months. You can book this for 1-2 years with a total support of 5 years with TYPO3 version 10.4. However, migration to the next versions, such as 12.4 and 13.3, is a natural choice. ELTS keeps your site running securely for longer, but does not remove the need for upgrades.
How do you determine the currently used TYPO3 version on your site?
Currently, the most stable or preferred TYPO3 version for development is TYPO3 version 13. The latest version has long-term support (LTS). It will support maintenance bug fixes until April 2026 and security updates until October 2027.
Also, another piece of good news for TYPO3 lovers: TYPO3 version 14.0 will be released on November 25th, 2025. TYPO3 v13 LTS has introduced many new features and major enhancements to existing features.
Depending on the TYPO3 version, you can find your current version of TYPO3 as follows.
TYPO3 version 13.x
In the new TYPO3 version 13.x, the version number is in the header and main area of the TYPO3 backend once you log in.
Why update your TYPO3 site?
A TYPO3 upgrade is significant in ensuring the health and smoother performance of your TYPO3 website. And it relies on the major factors listed below,
Security
Protecting websites from cyber attacks requires continuous updating and resources. TYPO3 issues updates frequently and increases security standards, while older versions can make websites vulnerable.
Speed
Website loading speed correlates to rankings, conversions, and user experience. TYPO3 works well, and recent assessments have shown faster times for FCP delivery compared with other CMSs.
Features
The latest versions of TYPO3 deliver tools that reduce errors, reduce effort in the content creation process, and create consistency within editors' editing efforts while allowing greater flexibility and control.
Editors
Editors achieve benefits from innovations that save costs and reduce the weight of relative effort. Some of the key features in v11.5 include the following:
- Modern, user-friendly editing experience
- Image editing directly in the backend
- Rich support for social and SEO efforts
- New form building wizard
- Feedback for editors is more robust
- Files create media references and perform search capabilities
SEO
Many built-in SEO modules limit the need for third-party extensions specifying things like metadata storage. Generating images progressively delivers a fast page regarding user experience, TYPO3 SEO factors, search rankings, and reduced bounce rates. Editors can also handle metadata and social sharing links from within the CMS.
GDPR
New and enhanced features for GDPR compliance limit risk for data by providing options for IP anonymization, improved hashing algorithms for passwords, and management of users, cookies, clean-ups, and TLS/HTTPS connections.
How to analyze & estimate TYPO3 upgrade?
Because of many technical risks, you will usually underestimate the TYPO3 upgrade project. That’s why you should always analyze the existing site to make a proper estimation. This will please your sales team and maintain a healthy relationship with the client.
Fact for TYPO3 update
“The TYPO3 core update always rocks; only extensions’ compatibility causes problems."
Prepare TYPO3 Backend Report
Team NITSAN developed one of the great TYPO3 Extension called “ns_ext_compatibility”. You can download it from our TYPO3 Shop: TYPO3 Upgrade Extensions Compatibility
This extension will be very helpful to generate TYPO3 compatibility with features like:
- Extensions Compatibility Report
- Automatic email notification for new version update
- Compatible from TYPO3 4.x to 13.x
- Export Feature for Customer
- Extension Statistics Report
- Server Compatibility Report
- System Overview Report
Estimation & Proposal Process
From the above analysis, I’m sure you will be able to judge the proper estimation of TYPO3 update. Even if it’s a technical matter, you may send the detailed proposal to your client as follows:
- x Hours: TYPO3 Upgrade from 4.x to 6.x to 7.x to 8.x to 9.x to 10.x to 11.x to 12.x to 13.x
- x Hours: Template Engine/Method change from Automaketemplate to Extbase/Fluid
- x Hours: TYPO3 Extensions Upgrade (Number of non-compatible extensions * ~2 Hour)
- x Hours: QA Testing + Bug Fixing
- x Hours: Miscellaneous (design issues, feedback & support, deployment to DEV & LIVE etc., )
It’s always good practice to check the scope & complexity of the website. You may also write to the client about one of the most uncertain aspects of TYPO3 updates as follows:
Notes for Non-compatible Extension
If an extension is incompatible, we will do our best to make it compatible. If a particular extension does not work, we must find a new solution, which will require extra effort.
TYPO3 Update/Upgrade: A Step by Step Guide
Step 1: Set up a Local Server
Download & Setup everything from LIVE to your LOCAL server
Step 2: Perform TYPO3 Upgrade
At your LOCAL server, start to upgrade TYPO3 core, Upgrade extensions, QA Testing & Bug Fixing.
Step 3: Non-compatible Extensions
You will need to do your best to make compatibility for all the TYPO3 extensions with TYPO3 patches, hooks, new standards, etc. You must provide your customer with a list of "not-feasible" TYPO3 extensions and a possible “alternative solution.”
Step 4: Upload it to the DEV Server
Once complete, everything should be on the LOCAL server, and then uploaded to the DEV server, e.g., dev.youdomain.com.
Step 5: Customer’s Approval
Your customer will need to test drive the whole site & provide approval that everything is fine.
Step 6: Go-Live
Finally, you can upload everything from DEV to the LIVE server.
How to quickly upgrade minor/security updates?
TYPO3 provide the best feature is, we can check out minor/security updates directly from TYPO3 backend.
- The Install Tool in the "Important Actions" section provides a function to update the TYPO3 Core.
- This only works under Unix and macOS, and your TYPO3 project is working with the typo3_src symlink.
- The document root needs to be writable, and one path above it (../) needs to be writable (new directories need to be allowed to be created).
- One more important thing is that the 'tar' command must be available to extract the Source package.
Manually upgrade TYPO3
You can install the minor/security updates manually. Go to the TYPO3 official site, typo3.org/download/, download the Source package of the new TYPO3 version, extract the package on your web server, and adjust the typo3_src symlink.
TYPO3 Template Changes
We recommend making changes and/or upgrading following the TYPO3 templating method:
- css_styled_content to fluid_styled_content
- TemplaVoila to Fluid
- Any outdated third-party TYPO3 extension to Fluid
TYPO3 Extensions Upgrade
The extension has two types, so let's briefly check them.
TER Extension
There are two main ways to upgrade the TER Extension.
1. Upgrade from EM
Directly upgrade the extension using the Extension Manager. Firstly, we need the scheduler called “Update extension list (extension manager)”
This scheduler compares and give the list of upgrade extension when we switch on Manage Extensions.
After you will click on the upgrade icon you will see the popup the list of versions.
Then just check the version you want to upgrade and click on the Upgrade Extension button. Boom, your version has been upgraded.
2. Upgrade Manually
You must manually search for your extension on the TYPO3 official website, https://extensions.typo3.org/, and download it after checking the dependencies.
Custom Extension
The Custom extension is designed based on the functionality of the client's requirement, so there is no special way to upgrade your custom Extension. However, we will face the major issue with code deprecation in the custom extension, so you need to study the Changelog of the TYPO3 version.
You can study at TYPO3's official site:
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Index.html. There, you will get most of the solutions to errors and issues.
Important Code Deprecation and Changes
Here, we would like to write a few lines of code to help migrate (and make compatible) your particular TYPO3 extension, which contains old-school code.
| piBased Code | Extbase Code |
|---|---|
| $this->cObj->IMG($imageConf) | $myImage = $this->cObj->cObjGetSingle('IMAGE', $ImgConf); |
| \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule(...) | \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule(...) |
| t3lib_extMgm::addStaticFile(...) | \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile(...) |
| Tx_Extbase_Utility_Extension::registerModule(...) | \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule(...) |
| t3lib_div:: | \TYPO3\CMS\Core\Utility\GeneralUtility:: |
require_once
All lines beginning with "require_once" and including TYPO3 core files are to be removed.
t3lib_div::loadTCA('')
All occurrences of "t3lib_div::loadTCA('')" are to be removed.
t3lib_extMgm::
All occurrences of "t3lib_extMgm::" should be replaced by "\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::".
t3lib_div::
All occurrences of "t3lib_div::" by "\TYPO3\CMS\Core\Utility\GeneralUtility::" are to be replaced.
tslib_pibase
All occurrences of "tslib_pibase" with "\TYPO3\CMS\Frontend\Plugin\AbstractPlugin" are to be replaced.
tslib_cObj
All occurrences of "tslib_cObj" must be replaced by "\TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer ".
makeInstance()
All occurrences of "makeInstance()" with "\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance()"" are to be replaced.
$GLOBALS['TCA']['any_table']
TCA definitions must now be moved to "Configuration/TCA/<any_table.php>" . The section " dynamicConfigFile " within the ctrl-section is omitted.
ExtensionManagementUtility::addStaticFile()
TypoScript definitions must be moved to "Configuration/TCA/Overrides/sys_template.php".
ExtensionManagementUtility::addPageTSConfig()
Page TSConfig definitions must be moved to "Configuration/TCA/Overrides/pages.php".
ExtensionManagementUtility::addTCAcolumns()
Must now be done within "Configuration/TCA/Overrides/<any_table>.php".
ExtensionManagementUtility::addToAllTCAtypes()
Must now be done within "Configuration/TCA/Overrides/<any_table>.php".
ExtensionManagementUtility::addPiFlexFormValue()
Must now be done within "Configuration/TCA/Overrides/tt_content.php".
ExtensionUtility::registerPlugin()
Must now be done within "Configuration/TCA/Overrides/tt_content.php".
ExtensionManagementUtility::addPlugin()
Must now be done within "Configuration/TCA/Overrides/tt_content.php".
ExtensionManagementUtility::getFileFieldTCAConfig()
The parameters of this method must be adjusted if you want to enable backend image editor (Cropping) for FAL images.
$_EXTKEY
The variable is omitted and all occurrences are to bereplaced by the extension keywith the exception of "ext_emconf.php".
ext_localconf.php
To our knowledge, only "\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin" is left;)
ext_tables.php
Nothing should be written in $TCA or $GLOBALS['TCA'] and the file should be omitted in future TYPO3 versions. Also allowed are "\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOn StandardPages()"
Remove duplicate FAL records after TYPO3 6.2 upgrade
CREATE TABLE sys_file_new LIKE sys_file; INSERT sys_file_new SELECT tx_phpunit_is_dummy_record, MAX(uid) AS uid, pid, tstamp, last_indexed, missing, storage, type, metadata, identifier, identifier_hash, folder_hash, extension, mime_type, name, sha1, size, creation_date, modification_date FROM sys_file GROUP BY BINARY identifier; SELECT * FROM sys_file_new; RENAME TABLE sys_file TO sys_file_bak; RENAME TABLE sys_file_new TO sys_file;
CREATE TABLE sys_file_reference_new LIKE sys_file_reference; INSERT sys_file_reference_new SELECT tx_phpunit_is_dummy_record, MAX(uid) AS uid, pid, tstamp, crdate, cruser_id, sorting, deleted, hidden, t3ver_oid, t3ver_id, t3ver_wsid, t3ver_label, t3ver_state, t3ver_stage, t3ver_count, t3ver_tstamp, t3ver_move_id, t3_origuid, sys_language_uid, l10n_parent, l10n_diffsource, uid_local, uid_foreign, tablenames, fieldname, sorting_foreign, table_local, title, description, alternative, link, downloadname FROM sys_file_reference WHERE deleted=0 GROUP BY pid,uid_local,uid_foreign,tablenames,fieldname; SELECT * FROM sys_file_reference_new; RENAME TABLE sys_file_reference TO sys_file_reference_bak; RENAME TABLE sys_file_reference_new TO sys_file_reference;
UPDATE sys_file_reference LEFT OUTER JOIN sys_file ON (sys_file.uid = sys_file_reference.uid_local) SET sys_file_reference.uid_local = sys_file_reference.uid_local + 1 WHERE sys_file.uid IS NULL;
Checklist for QA Testing
Once the TYPO3 upgrade finish, Your QA team should test the backend and frontend of the website as follows:
| Testing Scenario | Priority |
|---|---|
| Check UI/UX Design | Medium |
| Check Functional Frontend Features (if any) | High |
| Check TYPO3 Backend | High |
| Check Cross-Browsers Compatibility | Medium |
| Check Cross-Devices Compatibility | Medium |
| Check Speed & Performance Testing (Google insight, Pingdom) | Low |
| Check TYPO3 Backend Report | High |
| Check TYPO3 Error Logs | Medium |
| Check Console Error | Low |
| Check Deprecation Logs | Medium |
| Check the page-to-page comparison of before & after the upgrade | High |
Go-Live: Deployment to Live server
Before deployment checklist
- Check server compatibility with TYPO3 version
- Check server access detail
After the deployment checklist
- Check Report/Install tool module and solve errors if any
- Testing of speed/performance (Google Page Speed, Pingdom)
- Check TYPO3 backend error log
- QA Testing whole Live website
Conclusion
Thanks for reading such a long article ;)
I would love to know your experience and tips/tricks for completing TYPO3 upgrade projects smoothly and successfully. Please write down any suggestions or queries using the comment box below. Thank you! Also, check out our TYPO3 Support and Maintenance service to keep your site current.
Have a happy & secure TYPO3 upgrade :)
TYPO3 Upgrade Kit
Well, we have an ultimate TYPO3 Upgrade guide that provides detailed instructions and processes to ensure a safe upgrade.
Contact for project management and team coordination
Mihaela Angelova
Project Manager - Germany
Mihaela Angelova
Project ManagerMihaela keeps technology projects on track and ensures to meet business goals. She specializes in coordinating teams, optimizing workflows, and delivering projects. At NITSAN, she works closely with clients to transform ideas into actionable solutions. Outside of work, she enjoys exploring new hiking trails.
Be the First to Comment