← InsightsMigration · 2026

SharePoint 2013 Workflow is gone. What now?

Migration is not a one-to-one conversion exercise. First decide which old processes should be kept, redesigned or retired.

01

1. Inventory the business processes first

Identify which workflows still run, who owns them, which lists and libraries they use and how critical they are.

  • process inventory
  • business owner
  • criticality
  • usage frequency
02

2. The target is not always a Power Automate copy

Simple approvals fit Power Automate well; complex stateful or high-volume processes may need Power Apps, Dataverse, Logic Apps or a custom backend.

  • Power Automate
  • Power Apps
  • Dataverse
  • Azure Logic Apps / Functions
03

3. Redesign permissions and error handling

Modernisation is a chance to fix connection ownership, service accounts, DLP, alerts, logging and environment lifecycle.

  • connection ownership
  • service account / service principal
  • monitoring
  • ALM
04

4. Do not leave another black box behind

The target should be documented, supportable and understandable to both business owners and IT.

  • documentation
  • operational ownership
  • alerts
  • maintainability
Related service

SharePoint

Document management, lists, permissions and workflows on a well-structured SharePoint Online foundation.

View the service →
First step

Show us the process you would like to make simpler.

In a 30-minute call we look at how it works today, what is worth automating, where AI can help, and what should stay simple.