SharePoint On-Premises by Microsoft is a system outside Microsoft 365 that is operated and licensed in parallel. We show what standard Microsoft 365 already includes, what our web parts take over – and what you decide deliberately.
Profile
Initial assessment
Almost everything an on-premises farm does is included in SharePoint Online – usually better (search, mobile, Teams). Old farm solutions and workflows (InfoPath, Nintex, full-trust solutions) remain custom.
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
SharePoint On-Premises has the status “end of support for SharePoint 2016/2019: July 14, 2026”. Anyone staying will migrate to a new platform anyway – so better move straight to standard Microsoft 365, which you already pay for.
License model: Server/CAL licenses plus hardware, operations and maintenance – paid twice if you already hold an M365 license. On standard Microsoft 365 this recurring license disappears entirely – you pay once for setup and web parts.
End of support for 2016/2019 in July 2026, security updates are running out.
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 SharePoint On-Premises does well | How we do it in Microsoft 365 |
|---|---|
| Data in your own data center | Standard All content stays in your Microsoft 365 tenant – no second data store |
| Home-grown business solutions | Web parts We check this in the Replacement Check – usually feasible with standard web parts and configuration |
Feature comparison
Every feature with its counterpart in SharePoint, Teams, Viva or our web part catalog.
| Feature in SharePoint On-Premises | Solution in standard Microsoft 365 | Classification |
|---|---|---|
| Intranet pages (classic) | SharePoint pages and libraries with metadata, versioning and approval; FAQ/glossary web part | Standard Microsoft 365 |
| Document libraries | SharePoint pages and libraries with metadata, versioning and approval; FAQ/glossary web part | Standard Microsoft 365 |
| Lists & workflows (Nintex/InfoPath) | Planner, To Do and Power Automate | Standard Microsoft 365 |
| Search | Microsoft Search across SharePoint, Teams and OneDrive; search center web part with filters (Digital Touch) | Standard Microsoft 365 |
| Permissions & AD | Feasible with standard web parts and configuration | With our web parts |
| Custom web parts (farm solutions) | Web part package by Digital Touch with source code – no recurring license | With our web parts |
| Records management | Feasible with standard web parts and configuration | With our web parts |
| Mobile (limited) | Teams app and Viva Connections on the smartphone; a dedicated white-label app and login without M365 account are custom development | Custom / add-on module |
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 |
|---|---|
| InfoPath/Nintex workflows | Rebuild in Power Automate / Power Apps |
| Farm solutions (full trust) | SPFx web parts or standard |
Process
We go through SharePoint On-Premises 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 SharePoint On-Premises, clean it up and reorganize it for the target audiences; the editorial team and departments are enabled.
Pilot group, communication, go-live – then the SharePoint On-Premises 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. SharePoint On-Premises is a product of Microsoft; product and feature names are for orientation only. Digital Touch is not affiliated with the vendor.
In 60 minutes we go through your SharePoint On-Premises intranet and show what standard Microsoft 365 already includes, what our web parts take over and what the replacement costs.