Power Automate Rebuild After SharePoint 2013 Workflow Retirement — the 4-Phase Playbook
Microsoft retired the SharePoint 2013 workflow engine on April 2, 2026. Every workflow built with SharePoint Designer 2013 that ran on SharePoint Online stopped executing that day. If your organization still relied on any of them — approvals, list automations, document routing, or the Project Online workflow layer — this is EPC Group's discovery-to-cutover rebuild playbook.
Phase 1 — Discovery (Weeks 1-2)
PowerShell + the SharePoint REST API enumerating every workflow subscription in the tenant. EPC Group's discovery script iterates every site collection, every list, and every content type; enumerates every workflow subscription and workflow association; and outputs a CSV with (site URL, list, workflow title, workflow type, last run, current state, dependencies).
Enterprise tenants routinely surface 200 to 2,000 workflows in this inventory. Most of them are long-forgotten but load-bearing for a small user community.
Phase 2 — Triage & mapping (Weeks 3-4)
Every workflow gets one of three decisions:
- Archive — nobody has used it in 24+ months, or the business owner confirms it's no longer needed.
- Replace with a simpler pattern — SharePoint list rules, native SharePoint approval, Teams approvals, Microsoft Lists automation. Fastest path to shutdown.
- Rebuild in Power Automate — the business-critical, custom-logic, cross-system workflows.
For each rebuild-track workflow, EPC Group maps the SPD2013 pattern to a Power Automate pattern. Loops, state machines, and elevated-permission actions all need pattern translation, not literal port.
Phase 3 — Rebuild with ALM (Weeks 5-10)
Every flow built in a dedicated Dataverse environment with dev/test/prod promotion via Power Platform ALM. Solutions used for packaging. Unit tested. Load-tested with realistic data volumes. Peer-reviewed before promotion.
Phase 4 — Cutover (Weeks 11-12) + 90-day support
Waved cutover: migrate in-flight items, retrain users, decommission the SP2013 workflow subscription. Every engagement includes a 90-day post-cutover support window with named senior architects — because the flows that surface as broken only after users try to use them always surface in the first 30 days.
Frequently Asked Questions
What exactly happened on April 2, 2026?
Microsoft retired the SharePoint 2013 workflow engine across SharePoint Online, meaning every workflow built with SharePoint Designer 2013 (SPD2013) — the classic drag-and-drop workflow tool — stopped executing. Existing workflow instances that were "in progress" that day terminated. New instances stopped starting. This affected the SharePoint approval workflows, list-item automation workflows, custom document routing, and the entire Project Online workflow layer. If your organization built anything in SPD2013 that ran on SharePoint Online after April 2, 2026, it is dead.
How do we find every SP2013 workflow still in the tenant?
PowerShell + the SharePoint REST API. EPC Group's discovery script iterates every site collection, every list, and every content type; enumerates every workflow subscription and workflow association; and outputs a CSV with (site URL, list, workflow title, workflow type, last run, current state, dependencies). Typical enterprise tenants surface 200-2,000 workflows in this inventory — most of them long-forgotten but load-bearing for a small user community.
Do we rebuild every workflow in Power Automate?
No — that would be a bad decision. Roughly a third of any inventory is workflows nobody has used in 24+ months; those get archived. Another third can be replaced by simpler patterns (SharePoint list rules, native SharePoint approval, Teams approvals, Microsoft Lists automation). Only the final third — the business-critical, custom-logic, cross-system workflows — should be rebuilt as full Power Automate cloud flows. The discovery phase produces the triage decision for each one.
Are the Power Automate patterns 1:1 with SPD2013 patterns?
No, and this is where organizations that try to DIY the rebuild get stuck. SPD2013 conditional branching maps to Power Automate 'Condition' actions but the surrounding context is different. SPD2013 loops are trivially easy in SPD2013 and painful to replicate cleanly in Power Automate (loops in a cloud flow have per-loop concurrency limits and a 24-hour ceiling). SPD2013 state machines don't have a direct Power Automate equivalent — the pattern is Approval → Update State → Trigger next stage via child flow. Every SPD2013 pattern has an equivalent Power Automate pattern, but none are 1:1.
What does EPC Group deliver in a workflow-rebuild engagement?
A discovery report (every SP2013 workflow in the tenant, categorized archive/replace/rebuild); a rebuild backlog (every rebuild-track workflow with mapped Power Automate pattern, connectors required, security groups affected); the rebuilt flows themselves (built in a dedicated environment with dev/test/prod promotion via ALM); the cutover plan (data migration for in-flight items, user retraining, decommissioning of the SP2013 subscription); and a 90-day post-cutover support window with named senior architects.
Talk to a senior architect
If SPD2013 workflows are dead in your tenant and users are complaining, the fastest path is a senior architect with a discovery script and a Power Automate rebuild backlog process.
Email contact@epcgroup.net or call 888-381-9725.
North America's oldest continuous Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.