TYPO3 update or upgrade? Change version, keep what works.
Your TYPO3 website should stay technically up to date while content and design continue to fit? We check the existing state and clarify which update makes sense.
When changing the major version, we take extensions, custom developments and the server environment into account. We prepare the implementation in a separate test environment and agree the publication with you.
The website fits. The technology needs an update.
An update updates TYPO3 within the same major version. Such maintenance and security updates fix bugs or close security vulnerabilities. We take care of them as part of the agreed support or after a separate order.
An upgrade leads to a new major version. We check which adjustments to extensions, custom developments and the technical environment are required. This page focuses on this version change.
There are limited support periods for every TYPO3 version. When regular support expires, the further procedure should be planned in good time. Depending on the version, paid extended support can be an interim solution. We also look at the maintenance status of the extensions and the server environment.
Together we clarify whether the existing system can be continued or whether a technical rebuild makes more sense.
Renew the technology, keep what works.
A version change does not automatically require a new design. If content, page structure and design continue to suit your requirements, we include them in the modernisation.
The assessment shows how much of the existing technical implementation can be retained. Sometimes adjustments are enough, sometimes individual functions or larger parts have to be redeveloped. We distinguish necessary work and additional wishes from each other in the quote.
What we take into account in an upgrade.
How we prepare the version change.
The technical implementation initially takes place separately from your live website. We agree a separate procedure for publication with you.
Assessment
We record the technical state and the important functions of your website. We also clarify which documents and access are needed for implementation.
Planning
We agree target version, scope of services and version steps. Preparation also includes data backup, dealing with interim changes and a plan for the switchover.
Implementation and testing
We carry out the necessary adjustments in the test environment. We test the agreed functions and provide you with the updated website for your own review.
Approval and publication
After your approval, we switch the website over at the agreed time and check the central functions in live operation. If operation in the backend changes, we prepare your editorial team for it.
An up-to-date basis for further support.
After the upgrade, your website works with the agreed, supported TYPO3 version. Extensions and server environment are aligned with it. Proven content and structures are retained as far as agreed.
We document the changes made and the notes for further maintenance. On request, we then also take over ongoing support.
Modernise grown TYPO3 websites.
Whether step-by-step upgrade or technical rebuild: these projects show different ways of developing existing websites further and retaining proven content.
Frequently asked questions
Questions about the TYPO3 upgrade.
An update updates TYPO3 within the same major version and fixes bugs or security vulnerabilities. An upgrade leads to a new major version and may require adjustments to extensions and custom developments. Regular updates are part of maintenance, but do not replace a later major version change.
As a rule, no. Content, files and page structures can often be carried over. We check in advance which technical components can be reused or adapted.
With heavily outdated installations, a technical rebuild can make more sense. This does not automatically mean that design and content also have to be created anew.
We check every custom development for its task and compatibility with the target version. We then propose which adjustments are necessary or whether a different solution would make more sense. We agree procedure and effort with you.
That depends above all on the source and target version, the extensions and the custom developments. The scope of testing and coordination with those involved also influence the schedule. After the assessment, we can estimate the effort and procedure more reliably.
During preparation, the existing website remains in operation, as we work in a separate test environment. We define in advance how content changed in the meantime and newly received data are transferred.
A short interruption or a pause in editorial work may be necessary for the switchover. We agree the time window with you.
Yes. An upgrade can be combined with a design revision. In the quote, we separate the technically necessary work from the desired design changes and plan a suitable order. A new design is not a prerequisite for the version change.
We choose a supported version with a suitable remaining support period. We take into account the compatibility of your extensions and the requirements of your website. Whether and which intermediate steps are necessary depends on the source version and the chosen procedure.
The decisive factors are the technical starting state, the target version, the extensions and the share of custom developments. Added to this are the transfer of data and the necessary tests. After the assessment, we distinguish the required effort and possible additional services from each other.
Report anomalies to us after the conversion. We check the cause and fix errors that arose from our implementation.
Before publication, we already plan the data backup and the procedure in case the conversion does not work as planned. We also take into account data that has been added since the switchover.
Is a TYPO3 upgrade coming up for you?
Tell us your website and, if known, the TYPO3 version used. We discuss the starting point with you and clarify which check makes sense for an estimate of effort and procedure.