Home›Replace your intranet›
SharePoint On-Premises
Replacement ·
Other system

Replace SharePoint Server (on-premises) – with standard SharePoint and our web parts

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

Other system
Hersteller
Microsoft
Sitz
USA (Redmond)
Lizenzmodell
Server/CAL licenses plus hardware, operations and maintenance – paid twice if you already hold an M365 license
Typische Kunden
Companies with their own SharePoint farm (2013, 2016, 2019, Subscription Edition)
Betrieb
Own data center, farm operation
Status
end of support SharePoint 2016/2019: July 14, 2026
Covered by standard Microsoft 365
95
 %
70
 % standard
25
 % web parts
5
 % custom

Initial assessment

What standard Microsoft 365 already covers – and what it doesn't

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.

70
%
Standard Microsoft 365
25
%
with our web parts
5
%
custom / add-on module

Already in the standard

  • Pages & documents
  • Tasks & workflows
  • Search
  • News
  • Communities & social
  • Chat & meetings

With our web parts

  • Further features
  • Web part catalog

Custom or add-on module

  • Employee app

Digital Touch estimate based on publicly documented features – not a vendor comparison, no guarantee. The free Replacement Check delivers the reliable assessment.

Reasons

Why companies replace SharePoint On-Premises

1

Product discontinued or acquired

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.

2

License per user, every year

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.

3

Limits in everyday use

End of support for 2016/2019 in July 2026, security updates are running out.

A fair look

What SharePoint On-Premises does well – and how we deliver it on standard Microsoft 365

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 wellHow we do it in Microsoft 365
Data in your own data centerStandard All content stays in your Microsoft 365 tenant – no second data store
Home-grown business solutionsWeb parts We check this in the Replacement Check – usually feasible with standard web parts and configuration

Feature comparison

Feature comparison: SharePoint On-Premises and standard Microsoft 365

Every feature with its counterpart in SharePoint, Teams, Viva or our web part catalog.

Feature in SharePoint On-PremisesSolution in standard Microsoft 365Classification
Intranet pages (classic)SharePoint pages and libraries with metadata, versioning and approval; FAQ/glossary web partStandard Microsoft 365
Document librariesSharePoint pages and libraries with metadata, versioning and approval; FAQ/glossary web partStandard Microsoft 365
Lists & workflows (Nintex/InfoPath)Planner, To Do and Power AutomateStandard Microsoft 365
SearchMicrosoft Search across SharePoint, Teams and OneDrive; search center web part with filters (Digital Touch)Standard Microsoft 365
Permissions & ADFeasible with standard web parts and configurationWith our web parts
Custom web parts (farm solutions)Web part package by Digital Touch with source code – no recurring licenseWith our web parts
Records managementFeasible with standard web parts and configurationWith 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 developmentCustom / add-on module
Standard = included in your Microsoft 365 planWeb parts = solution from our catalog, one-time, with source codeCustom = Power Platform, add-on module or dropped

An honest calculation

What stays custom – and how we handle it

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 customOur approach
InfoPath/Nintex workflowsRebuild in Power Automate / Power Apps
Farm solutions (full trust)SPFx web parts or standard

Process

From SharePoint On-Premises to standard Microsoft 365 in five steps

Replacement Check

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.

Target picture & prototype

Information architecture, permissions and design in SharePoint – as a clickable prototype in your tenant, before the migration starts.

Build & web parts

Pages, navigation and the right web parts from the catalog; custom building blocks are created with Power Platform or SPFx.

Content & migration

Take over content from SharePoint On-Premises, clean it up and reorganize it for the target audiences; the editorial team and departments are enabled.

Go-live & switch off SharePoint On-Premises

Pilot group, communication, go-live – then the SharePoint On-Premises license expires and the intranet lives on in Teams and SharePoint.

References

How we did it for others

All references →

License calculator

What will your legacy system cost over five years?

Enter your user count and price – the calculator shows your savings over 1, 3 and 5 years compared to a one-time replacement project.

Calculate your savings

FAQ

Frequently asked questions about replacing SharePoint On-Premises

What happens to our content from SharePoint On-Premises?

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.

Do we have to run SharePoint On-Premises and the new intranet in parallel?

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.

How long does the replacement take?

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.

What about features the standard doesn't have?

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.

Free Replacement Check for SharePoint On-Premises

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.