SharePoint Workflows with Power Automate: Migration and Implementation

SharePoint Workflows: From Legacy to Power Automate

SharePoint workflow technology has undergone a complete transformation. SharePoint 2010 and 2013 workflows built in SharePoint Designer are deprecated with announced end-of-support dates. Power Automate is the only supported workflow engine for SharePoint Online going forward. Organizations that have not migrated their legacy workflows face both functionality loss and security risk.

This guide covers the migration path from legacy workflows to Power Automate and provides implementation patterns for common SharePoint automation scenarios.

---

Legacy Workflow Landscape

SharePoint 2010 Workflows

Built in SharePoint Designer, running on the SharePoint workflow engine. These workflows execute directly on the SharePoint server and support basic conditions, actions, and loops. They are limited to single-site scope and cannot call external services.

SharePoint 2013 Workflows

Also built in SharePoint Designer but running on Azure Workflow Manager. These workflows support HTTP calls, dictionary operations, and more complex logic than 2010 workflows. However, they are still limited compared to Power Automate.

End of Support Timeline

Microsoft has announced deprecation for both workflow types in SharePoint Online. Organizations should treat migration as urgent. After end-of-support, existing workflows may continue to run but will receive no bug fixes, security patches, or feature updates. New creation of legacy workflows is already blocked.

---

Migration Planning

Workflow Inventory

Document every active workflow in your SharePoint environment. For each workflow, record the site and list it is associated with, the trigger conditions, the complete logic flow including all conditions and actions, all participants (initiators, approvers, notification recipients), integration points with other systems, and run frequency and business criticality.

```powershell

# Find all workflows in a site collection

Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/HR" -Interactive

$lists = Get-PnPList

foreach ($list in $lists) {

$workflows = Get-PnPWorkflowDefinition -List $list.Title -ErrorAction SilentlyContinue

if ($workflows) {

foreach ($wf in $workflows) {

Write-Host "$($list.Title): $($wf.DisplayName) - $($wf.Published)"

}

}

}

```

Complexity Assessment

Categorize workflows by migration complexity. Simple workflows have linear logic with 5 or fewer actions, basic approval or notification, and no external integrations. Budget 1 to 2 hours for migration. Medium workflows have conditional branching, multiple approval stages, email formatting, and basic error handling. Budget 3 to 5 hours. Complex workflows have parallel branches, loops, external HTTP calls, custom logic, and complex error handling. Budget 8 to 16 hours.

Migration Priority

Migrate workflows in priority order. Critical business workflows first (approvals that block operations). High-frequency workflows second (daily or weekly runs). Low-criticality workflows last (annual or rarely used).

---

Building Workflows in Power Automate

Core SharePoint Triggers

When an item is created fires for new list items or file uploads. Use for new document processing, welcome notifications, and initial routing.

When an item is created or modified fires on any change. The most commonly used trigger. Add trigger conditions to filter and avoid unnecessary flow runs.

For a selected item creates a manual trigger in the list command bar. Users click the flow name to initiate it for a specific item. Use for on-demand actions like submit for approval or generate document.

When a file is created in a folder fires for files created in a specific folder path. Use for processing uploaded files in a designated intake folder.

Approval Patterns

Simple approval: Route to a single approver. The approver receives an email and Teams notification with Approve and Reject buttons.

Sequential approval: Route through multiple approvers in order. Each must approve before the next receives the request. Use for multi-level authorization (manager then director then VP).

Parallel approval: Send to multiple approvers simultaneously. All must approve (Everyone must approve) or any one can approve (First to respond). Use for committee decisions or peer reviews.

Custom approval with conditions: Route to different approvers based on item properties. A purchase request under 5,000 dollars goes to the department manager. Over 5,000 dollars goes to the VP. Over 50,000 dollars goes to the CFO.

Document Processing

Document routing: When a document is uploaded to an intake library, read its metadata, determine the correct destination library based on document type, copy the file to the destination, update metadata, delete the original from intake, and notify the document owner.

Document generation: When a list item reaches a certain status, generate a document from a Word template using the Populate a Word template action, save the generated document to a library, and notify stakeholders with a link to the document.

Notification Patterns

Targeted notifications: Send different notifications to different people based on their role or the item's properties. Use Switch actions for routing logic and parallel branches for simultaneous notifications.

Digest notifications: Scheduled flows that aggregate activity over a period and send a single summary email. More effective than individual notifications for high-volume lists.

---

Error Handling and Reliability

Configure Run After

Every action in a flow has a Configure run after setting that determines when it executes. By default, actions run after the previous action succeeds. Configure alternative paths that run after failure, timeout, or skip to handle errors gracefully.

Scope Actions for Try-Catch

Wrap related actions in a Scope action. Add a parallel Scope that runs after the first scope fails. This creates a try-catch pattern where errors are caught and handled.

Error handling template:

• Scope: Try (contains the main workflow actions)
• Scope: Catch (runs after Try fails)
• Get the error details from the failed actions
• Log the error to a SharePoint error log list
• Send a notification to administrators
• Update the item status to Error

Retry Policies

Configure retry policies on actions that may fail transiently (HTTP requests, SharePoint API calls during throttling). Set retry count to 3 or 4 with exponential backoff intervals.

---

Governance

Naming Standards

Adopt a consistent naming convention for flows. Include the scope, action, and trigger type. Examples: HR Benefits - Document Approval - On Status Change, Finance - Invoice Processing - Daily Scheduled, IT - Access Request - Manual Trigger.

Environment Strategy

Use Power Platform environments to separate development, testing, and production. Build and test flows in a development environment. Promote to production using solutions. This prevents untested automations from affecting production data.

Monitoring

Monitor flow runs through the Power Automate portal. Create a monitoring dashboard that shows daily flow run counts, failure rates by flow, average run duration, and flows approaching throttling limits.

---

Frequently Asked Questions

Is there an automated migration tool?

No. There is no automated tool to convert SharePoint Designer workflows to Power Automate. Each workflow must be manually rebuilt. This is because Power Automate's architecture and action model differ fundamentally from legacy workflows.

Can Power Automate run on SharePoint on-premises?

Yes, using the on-premises data gateway. Install the gateway on a server with access to your SharePoint farm and configure the SharePoint connector to use the gateway. Performance is slower than SharePoint Online connections.

What is the difference between Power Automate and Logic Apps?

Both are built on the same platform. Power Automate is designed for business users and IT professionals with a visual designer and SharePoint integration. Logic Apps are designed for developers with Azure portal integration, more connectors, and enterprise integration patterns. For SharePoint workflows, Power Automate is the recommended choice.

---

For help migrating legacy workflows to Power Automate, [contact our automation team](/contact) for a workflow assessment. We have migrated hundreds of SharePoint workflows for organizations where [business process continuity](/services) is critical.

Advanced Automation Patterns

Parallel Processing Workflows

For scenarios requiring multiple independent tasks to complete before proceeding, use parallel branches. When a new employee is onboarded, simultaneously provision their SharePoint access, create their OneDrive, add them to relevant Teams groups, and send welcome emails. Use a parallel branch for each task and add a synchronization point where all branches must complete before the workflow continues to the next stage.

Scheduled Maintenance Workflows

Create scheduled flows for recurring SharePoint maintenance tasks. Weekly flows can audit external sharing links and remove expired ones, check for orphaned sites where the owner has left the organization, generate storage consumption reports, and identify stale content for review. Monthly flows can perform comprehensive permission audits, generate compliance reports, clean up unused term store terms, and review and refresh site collection administrator assignments.

Integration with Azure Services

Extend Power Automate capabilities by integrating with Azure services. Use Azure Functions for complex processing logic that exceeds Power Automate expression capabilities. Use Azure Cognitive Services for document analysis and classification. Use Azure Logic Apps for enterprise integration patterns. Use Azure Key Vault for secure credential storage used in flow connections.

Workflow Documentation and Knowledge Transfer

Document every production workflow with its purpose, trigger conditions, complete logic flow, error handling approach, expected run frequency, responsible owner, and escalation contacts. Store this documentation in a SharePoint list that serves as a workflow registry. Include links to the flow in Power Automate and the associated SharePoint lists or libraries.