Many intranets have historically grown on TYPO3 – maintained by the website agency, with their own login and their own search. On standard SharePoint you get the same pages, connected to Microsoft login, Teams and documents.
Profile
Initial assessment
A CMS intranet consists of pages, news and documents – all standard SharePoint. The added value comes from Teams integration, personalization and search, which TYPO3 does not offer internally.
Already in the standard
With our web parts
Custom or add-on module
Digital Touch estimate based on publicly documented features – not a vendor comparison, no guarantee. The free Replacement Check delivers the reliable assessment.
Reasons
Employees sign in separately. Permissions are maintained twice – in TYPO3 and in Microsoft 365.
TYPO3 versions, extensions and hosting need an agency or IT. SharePoint is operated and updated by Microsoft.
The CMS knows neither Teams nor SharePoint libraries. Content is maintained twice.
A fair look
Nobody replaces a system that can't do anything. That's why we take its strengths seriously – and show how we answer them with standard Microsoft 365.
| What TYPO3 does well | How we do it in Microsoft 365 |
|---|---|
| No license price | Standard Not applicable: Microsoft 365 is already licensed – only one-off project costs apply |
| Flexible templating | Standard Standard Microsoft 365 (Office integration is built in) |
Feature comparison
Every feature with its counterpart in SharePoint, Teams, Viva or our web part catalog.
| Feature in TYPO3 | Solution in standard Microsoft 365 | Classification |
|---|---|---|
| Pages & navigation | SharePoint pages and libraries with metadata, versioning and approval; FAQ/glossary web part | Standard Microsoft 365 |
| News | SharePoint news with templates and audiences; news web part (Digital Touch) for layout | Standard Microsoft 365 |
| Documents | SharePoint pages and libraries with metadata, versioning and approval; FAQ/glossary web part | Standard Microsoft 365 |
| Forms | Microsoft Forms and Viva Pulse; survey web part (Digital Touch) | Standard Microsoft 365 |
| Multilingual support | Multilingual web part with automatic translation (Digital Touch) | With our web parts |
| Roles & permissions | Feasible with standard web parts and configuration | With our web parts |
| Search | Microsoft Search across SharePoint, Teams and OneDrive; search center web part with filters (Digital Touch) | Standard Microsoft 365 |
| Extensions | Feasible with standard web parts and configuration | With our web parts |
An honest calculation
Not every feature needs to be rebuilt. In the end, many features are used by only a fraction of the workforce – we check that before any effort is spent.
Assess in the Replacement Check| Stays custom | Our approach |
|---|---|
| Special TYPO3 extensions | Case-by-case assessment |
Process
We go through TYPO3 feature by feature: what is standard, what web parts take over, what stays custom. Result: mapping, effort and license savings.
Information architecture, permissions and design in SharePoint – as a clickable prototype in your tenant, before the migration starts.
Pages, navigation and the right web parts from the catalog; custom building blocks are created with Power Platform or SPFx.
Take over content from TYPO3, clean it up and reorganize it for the target audiences; the editorial team and departments are enabled.
Pilot group, communication, go-live – then the TYPO3 license expires and the intranet lives on in Teams and SharePoint.
References
License calculator
Enter your user count and price – the calculator shows your savings over 1, 3 and 5 years compared to a one-time replacement project.
FAQ
Pages, news and documents are exported, cleaned up and restructured in SharePoint. Not everything has to come along – the Replacement Check shows what users really need. We map permissions via Entra ID groups.
Only briefly: we plan the go-live so that your license's notice period is met. A parallel run of a few weeks for the pilot group is usually enough.
Typically three to six months from workshop to go-live, depending on content volume and custom building blocks. The first usable version is usually ready after a few weeks.
That is what our web parts with source code are for – no recurring license. Anything beyond that we build with Power Platform or deliberately leave out after consulting with you.
Digital Touch estimate based on publicly available product information (as of October 2026), not a third-party assessment. TYPO3 is a product of TYPO3 (open source) / agencies; product and feature names are for orientation only. Digital Touch is not affiliated with the vendor.
In 60 minutes we go through your TYPO3 intranet and show what standard Microsoft 365 already includes, what our web parts take over and what the replacement costs.