n8n vs. Power Automate vs. Zapier: Which one fits your company?
n8n vs. Power Automate vs. Zapier: Which one fits your company?
Three tools, three philosophies. An honest comparison of cost, data ownership and effort — without vendor bias.
SharePoint Workflow Engine is being shut down — what to do before April 2026
Microsoft is pulling the plug: on 2 April 2026 the classic SharePoint Workflow Engine ends. Anyone who does not act now risks established processes stopping overnight. The switch is manageable — if you plan it in time.
Many mid-sized companies have built small, useful workflows in SharePoint over the years: leave requests, approvals, notifications. They run quietly in the background and no one thinks about them anymore. That is exactly what is now becoming a problem.
What is being shut down?
Microsoft is permanently ending the classic SharePoint Workflow Engine (based on the 2013 Workflow Platform) on 2 April 2026. Workflows running on this engine will no longer execute after that date. This affects both SharePoint Online and older, connected automations.
In short
From 2 April 2026, all processes still based on the old SharePoint Workflow Engine will stop. There is no automatic migration — the switch must be actively planned.
Who is affected?
Practically every company that has been actively using SharePoint for several years and has mapped its own processes there is affected. Typical candidates:
- Approval and sign-off workflows for documents
- Automatic notifications on status changes
- Leave and absence requests via SharePoint lists
- Escalation and reminder logic in project libraries
The concrete risk
The insidious part: these workflows do not fail loudly — they simply stop working. Approvals pile up, notifications stop arriving, and it often takes days before someone realises the cause is a shut-down engine.
The most expensive downtime is the kind nobody notices right away.
Diagram: old engine → Power Automate
The clean migration path
The good news:
1. Inventory
First, we take stock of all active SharePoint workflows: what is running, how critical is it, and what can be dropped while we are at it?
2. Rebuild in Power Automate
The relevant workflows are rebuilt in Power Automate with clear approvals and traceable steps. Existing Microsoft 365 licences are usually sufficient.
3. Parallel operation and cutover
Before the deadline, both run in parallel so nothing is lost. Only once the new workflow demonstrably works cleanly is the old one switched off.
What you should do now
The deadline seems distant, but inventory, rebuild and parallel operation all need lead time. Anyone who only starts in March 2026 will be under pressure. It makes sense to take stock now, even if the actual migration happens later.
Our offer
In the free initial analysis, we review your SharePoint workflows and tell you concretely what needs to be migrated and at what effort. No strings attached.
About NordFlux
More about us NordFlux UG (haftungsbeschränkt)
NordFlux builds digital employees for organisations: automations and AI agents that take over repetitive work. You stay in control.
Read more
→
Related posts
Process automation in Wismar: Where mid-sized companies start first
Process automation in Wismar: Where mid-sized companies start first
From invoice processing to onboarding: the five processes with the greatest leverage in day-to-day operations.
Internal knowledge assistant: AI on your own documents
Internal knowledge assistant: AI on your own documents
How an assistant on your own data answers routine questions in seconds — with source references and clear boundaries.
Free initial analysis
Still running SharePoint workflows?
We review your inventory and tell you concretely what needs to be migrated before April 2026. No strings attached.
- One dedicated contact, no call centre
- First results in around 30 days
- German data sovereignty, DPA in place