SharePoint applications after end of support

The dates have arrived. SharePoint Server 2013 went out of support in April 2023; 2016 and 2019 followed on 14 July 2026. A farm on any of them gets no security fixes.

The applications inside it are on their own timetable. In Microsoft 365, SharePoint 2013 workflows stopped on 2 April 2026, and InfoPath Forms Services was retired on 14 July 2026, with new or changed forms blocked from May. On an on-premises farm those forms and workflows keep running, unsupported, for as long as the farm does. So the choice isn't whether to move them. It's whether they become Power Apps and Power Automate flows in Microsoft 365, or an application of their own.

SharePoint Server Subscription Edition is Microsoft's on-premises successor, with no fixed end date but the same legacy features being retired over time. It's a home for the documents, not for the applications.

A document store, which it's good at, and then a place to build things because it was there. The pattern is the same everywhere:

• Lists as databases. Customers, jobs, assets, in lists with lookups between them, past the point where a list copes.
• InfoPath forms for data entry, with rules in the form.
• SharePoint Designer or 2013 workflows for approvals and notifications, built by someone who's left.
• Custom code. Web parts, event receivers, timer jobs, farm solutions, written against a SharePoint version that's gone.
• Integrations with the line-of-business systems, often through the same custom code.

The document store moves to Microsoft 365 with tooling. The applications don't, and they're where the business runs.

Microsoft 365, with Power Apps and Power Automate. Microsoft's route for forms and approvals. Right for small, document-centred processes that stay close to SharePoint. The Power Apps page covers what happens when that route is pushed past its limits.

An application you own. For the lists that became databases and the workflows that became the business process. A database, screens and rules in one place, with documents still in SharePoint or Microsoft 365 and linked. No delegation limits, no per-user premium licence, and customers or suppliers can be given access.

Subscription Edition on-premises. Where the data has to stay on-site, for the documents and for the applications that haven't moved yet. It buys time, and the retirements follow it.

The assessment sorts every application into one of the three from evidence, and the plan does the document migration once and the applications one at a time.

1. Inventory. Every site, list, form, workflow and piece of custom code, with its owner, its last use and what depends on it. The assessment produces this from the farm, not from memory.
2. Classify. Documents, small processes, applications. Three destinations.
3. Move the documents to Microsoft 365 or Subscription Edition, with the migration tooling, once.
4. Rebuild the applications, one at a time, in order of risk: the list nearest its limits or the workflow nobody can change first. Each runs in staging on migrated data, reconciled, then switches, with the SharePoint version read-only behind it.
5. Rebuild the small processes in Power Apps and Power Automate where that's the fit, or fold them into the application.
6. Decommission the farm when the last application has moved.

Each stage has its own fixed price, and each ends with something working and off the old farm.

Lists export cleanly, with their lookups mapped to relationships. Documents move with their metadata and versions. Neither meets a change until the change has proven itself somewhere else: a migration tested against a copy in a test environment, then run in staging with counts and a sample reconciled, before anything switches. The SharePoint site stays read-only alongside until you're confident.

Yes, and for a farm with several applications it's the only safe way. Documents once, then one application at a time, with the rest of SharePoint untouched until their turn. Stop after any stage and keep everything.

The assessment is from £395 + VAT, sized on a free one-hour consultation, with an exact price before you commit. For a SharePoint farm it produces the inventory, sorts every application into its destination, and prices the document move and each application as fixed numbers. What drives the price and the payment terms each have a page.

The farm is unpatched now, and it's usually the one internet-facing thing in the estate that the IT team can't upgrade. The workflows and forms have no supported replacement path on the farm, so each change to a process is done by hand or not at all. And the person who built the workflows left with the only description of how the business approves things.

Inventory, classify, documents once, applications one at a time. Marc Allington has built on SharePoint on-premises and builds on the .NET and web stacks that SharePoint applications move to. Everything we build runs on open, widely used technology, in your own accounts, with full source code and ownership transferring to you on final payment.