Workflow Migration: SharePoint 2013 to Power Automate

How to Migrate Legacy SharePoint Workflows to Power Automate

Migrating legacy SharePoint 2010 and 2013 workflows to Power Automate is a critical modernization task because Microsoft has retired the legacy workflow engines in SharePoint Online, meaning organizations still running these workflows face broken business processes and compliance gaps. Power Automate provides a modern, cloud-native replacement with greater flexibility, reliability, and integration capabilities.

In our 25+ years of SharePoint consulting, we have migrated hundreds of legacy workflows for enterprise clients, from simple approval chains to complex multi-stage business processes spanning multiple systems. This guide covers the migration planning process, architectural decisions, common patterns, and execution strategies for a successful workflow modernization.

Understanding the Urgency

Microsoft deprecated SharePoint 2010 workflows in November 2020 and stopped supporting SharePoint 2013 workflows for new tenants. Existing 2013 workflows continue to run but receive no updates or bug fixes. Organizations should treat legacy workflow migration as urgent because workflows may stop functioning without warning, security vulnerabilities will not be patched, new features and integrations are only available in Power Automate, and technical debt increases with every month of delay.

Inventory and Assessment

Cataloging Existing Workflows

Before migrating, create a comprehensive inventory of all legacy workflows. Document the workflow name, the site and list or library where it runs, the trigger event, the workflow type (2010 or 2013), the business process it supports, the owner or business stakeholder, and the frequency of execution.

```powershell

# Inventory legacy workflows across the tenant

Connect-PnPOnline -Url "https://tenant.sharepoint.com/sites/team" -Interactive

$webs = Get-PnPSubWeb -Recurse -IncludeRootWeb

foreach ($web in $webs) {

$lists = Get-PnPList -Web $web

foreach ($list in $lists) {

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

foreach ($wf in $workflows) {

Write-Output "$($web.Url) | $($list.Title) | $($wf.DisplayName)"

}

}

}

```

Complexity Classification

Classify each workflow by migration complexity. Simple workflows include single-stage approvals, basic notifications, and status updates. These translate directly to Power Automate templates. Medium complexity workflows include multi-stage approvals, conditional routing, and calculated fields. These require custom Power Automate flows with branching logic. Complex workflows include multi-system integrations, custom code actions, impersonation steps, and looping constructs. These may require architectural redesign rather than direct translation.

Architectural Decisions

Power Automate Flow Types

Choose the appropriate flow type for each migrated workflow. Automated flows trigger on SharePoint events like item creation or modification. Instant flows are manually triggered by users. Scheduled flows run on a time-based schedule. Business process flows guide users through multi-step processes with a visual stage indicator.

Solution Architecture

Package related flows into Power Platform solutions for lifecycle management. Solutions support version control, environment promotion (dev to test to production), and dependency tracking. This is essential for enterprise deployments where workflows must go through change management processes.

Common Migration Patterns

Approval Workflow Migration

Legacy approval workflows typically set a status column, send an email to an approver, wait for a response, and update the item based on the decision. In Power Automate, use the Start and wait for an approval action which provides a richer experience with approval history, mobile push notifications, delegation, and Teams integration.

Notification Workflow Migration

Legacy email notification workflows translate to Power Automate's Send an email action with enhanced capabilities including adaptive card notifications in Teams, dynamic content with rich formatting, conditional recipient lists, and scheduled digest notifications.

Task Assignment Migration

Legacy task creation workflows translate to Power Automate's Planner integration or SharePoint task list creation. Consider migrating to Planner for better visibility and management, or use the SharePoint Create Item action to maintain task lists within SharePoint.

Execution Strategy

Phased Migration Approach

Migrate workflows in phases rather than all at once. Phase one migrates simple, high-impact workflows to demonstrate value and build team capability. Phase two handles medium complexity workflows with the lessons learned from phase one. Phase three tackles complex workflows that may require redesign or external expertise.

Parallel Running

Run legacy and new workflows in parallel during a transition period. Configure the Power Automate flow to run alongside the legacy workflow for two to four weeks. Compare outputs to verify the new flow produces identical results. Disable the legacy workflow only after confirming the new flow handles all edge cases correctly.

Testing Strategy

Test migrated workflows thoroughly. Create test cases that cover the normal approval path, rejection and revision scenarios, timeout and escalation conditions, error handling and retry logic, edge cases like empty fields or unexpected values, and high-volume scenarios to verify throttling behavior.

Handling Complex Scenarios

Impersonation Steps

Legacy workflows could impersonate the workflow initiator or specific users. Power Automate flows run under the connection owner's identity by default. For scenarios requiring different identities, use service accounts with appropriate permissions, the Send an HTTP Request to SharePoint action with app-only authentication, or custom connectors with certificate-based authentication.

Loops and Collections

Legacy workflows with loop actions translate to Power Automate's Apply to each action. Be aware of Power Automate's concurrency limits and consider pagination for large collections. Use the Filter array action to reduce the number of items processed in loops.

Post-Migration Governance

Establish governance for the new Power Automate environment. Define naming conventions for flows, document flow ownership and business purpose, set up monitoring for flow failures through the Power Platform admin center, configure DLP policies that control which connectors flows can use, and implement regular review cycles to identify orphaned or broken flows.

When to Engage Expert Support

Power Automate Governance for Migrated Workflows

After migration, establish governance practices that keep your Power Automate environment healthy. Create a flow registry in a SharePoint list tracking every production flow with its name, purpose, trigger type, owner, and last review date. Require quarterly reviews. Implement naming conventions that identify flows by department and purpose. Configure DLP policies controlling which connectors can be used together to prevent unauthorized data routing. Set up environment management separating development, testing, and production flows.

Monitor flow run success rates through the Power Platform Admin Center and establish alerting thresholds that notify administrators when flows fail repeatedly. Document every flow with its business logic, error handling approach, and escalation contacts so that maintenance does not depend solely on the original creator.

Organizations with more than 50 legacy workflows or workflows that integrate with external systems should consider professional migration assistance. Our SharePoint migration services include comprehensive workflow inventory, migration planning, execution, testing, and post-migration support. Contact us to discuss your workflow migration requirements.

Detailed Migration Patterns by Workflow Type

Document Approval Migration Pattern

Legacy SharePoint Designer approval workflows typically follow a pattern of setting a status column, sending an email to the approver with a link to the document, waiting for a task completion event, and updating the item status based on the approver's decision. In Power Automate, this translates to a trigger on item creation or modification, a condition checking the status value, the Start and Wait for an Approval action that provides rich mobile and Teams notifications, and conditional branches that update the item and send result notifications.

The Power Automate version is superior because it provides native mobile push notifications, approval history visible in the Power Automate portal, delegation capabilities when approvers are out of office, and integration with Microsoft Teams for approval actions directly in the Teams activity feed.

Status Change Notification Migration Pattern

Legacy notification workflows that send emails when list items change status translate directly to Power Automate. The key improvement is replacing static email templates with dynamic content that pulls current item values, includes formatted tables of changed fields, and can optionally send adaptive card notifications in Teams instead of or in addition to email.

Calculated Field and Data Update Migration Pattern

Legacy workflows that perform calculations or update fields across multiple lists translate to Power Automate flows using the Update Item action for SharePoint list modifications and expressions for calculations. Power Automate expressions support mathematical operations, date calculations, string manipulation, and conditional logic that replaces the equivalent SharePoint Designer actions.

Managing the Transition Period

Communication Plan

Notify all workflow stakeholders about the migration timeline, what will change in their experience, and what they need to do during the transition. Create a FAQ document addressing common concerns such as whether historical workflow data will be preserved, whether the new workflows will behave identically, and how to report issues during the transition.

Rollback Planning

Maintain the ability to revert to legacy workflows if critical issues are discovered during the transition. Do not delete legacy workflow definitions until the Power Automate replacements have been validated in production for at least four weeks. Keep the legacy workflow in a paused or disabled state rather than deleting it, so it can be re-enabled quickly if needed.

Knowledge Transfer

Train the team responsible for maintaining workflows in Power Automate. The skills required are different from SharePoint Designer: Power Automate uses a visual flow designer, supports connectors to hundreds of services, and follows different error handling patterns. Invest in Power Automate training for your SharePoint administrators and designated workflow builders.

Post-Migration Monitoring and Optimization

Flow Analytics

Monitor migrated flows using the Power Automate analytics dashboard. Track flow run success rates, average execution time, most common failure reasons, and flow run volume. Identify flows with high failure rates and investigate root causes. Common post-migration issues include throttling from high-volume flows, permission mismatches, and connector authentication expiration.

Continuous Improvement

After migration, look for opportunities to improve workflows beyond simple one-to-one migration. Power Automate capabilities that were not available in SharePoint Designer include parallel approval branches, adaptive card notifications with inline actions, AI Builder integration for document processing, and HTTP connectors for integration with external APIs. Enhance migrated workflows to take advantage of these capabilities based on user feedback and business process improvement goals.

Documentation Standards

Maintain documentation for every production Power Automate flow including the business process it supports, trigger conditions and expected behavior, error handling logic, owner and escalation contacts, and dependencies on other flows or systems. Store this documentation in a SharePoint site dedicated to workflow governance.

Enterprise Implementation Best Practices

In our 25+ years of enterprise SharePoint consulting, we have managed hundreds of large-scale migrations for organizations ranging from mid-market firms to Fortune 500 enterprises, and the patterns of success and failure are remarkably consistent. Migration projects that skip proper planning inevitably encounter data loss, broken permissions, and extended downtime that erodes user trust.

• Conduct a Comprehensive Pre-Migration Assessment: Before moving a single document, inventory your entire source environment including site structures, custom solutions, workflows, permissions, and integrations. Map every content type, metadata schema, and business process that depends on the current environment. This assessment typically reveals 20 to 30 percent more complexity than stakeholders initially estimate, and discovering these issues before migration prevents costly mid-project scope changes.

• Establish a Pilot Migration Program: Select two to three representative sites that cover your most common scenarios including document libraries with complex metadata, sites with custom permissions, and libraries with active workflows. Migrate these pilot sites first, validate every aspect of the migration output, and document lessons learned. Pilot migrations consistently reduce overall project timelines by 25 to 40 percent because they expose environment-specific issues early.

• Implement a Parallel Run Period: Maintain both source and target environments for 30 to 60 days after migration. This parallel period allows users to verify their content, report discrepancies, and build confidence in the new environment. Configure the source environment as read-only during this period to prevent data divergence while preserving rollback capability.

• Plan for Identity and Permission Mapping: Permission migration is the most error-prone aspect of any SharePoint migration. Build comprehensive identity mapping tables that account for renamed accounts, merged departments, and external users. Validate permission inheritance chains and explicit permission assignments on a representative sample before executing the full migration.

• Automate Pre and Post Migration Validation: Build automated validation scripts that compare source and target environments across document counts, metadata values, version histories, and permission assignments. Manual validation is impractical at enterprise scale and inevitably misses discrepancies that automated checks catch consistently.

Governance and Compliance Considerations

Migration projects create unique compliance challenges because they involve moving data across environments where governance controls, retention policies, and access permissions may differ significantly. Organizations subject to regulatory requirements must maintain chain of custody documentation throughout the migration process.

For HIPAA-regulated healthcare organizations, every document containing protected health information must maintain its access controls, audit trail, and encryption status throughout the migration. Document the permission mapping for PHI-containing libraries, verify that sensitivity labels transfer correctly, and confirm that retention policies remain enforced in the target environment without gaps during the transition period.

Financial services organizations must ensure that migration does not disrupt SEC and FINRA recordkeeping compliance. Verify that version histories transfer completely, that immutable records maintain their declaration status, and that litigation hold content remains preserved throughout the migration. Document the migration process as part of your records management audit trail.

Government organizations subject to FedRAMP or CMMC must confirm that migration activities comply with authorized boundary requirements and that content classifications transfer accurately. Maintain migration logs that satisfy NIST 800-53 audit requirements and verify that access controls align with security clearance levels in the target environment.

Regardless of your regulatory framework, implement a post-migration compliance validation process that verifies retention policy application, permission accuracy, sensitivity label assignment, and audit logging activation across all migrated content. Working with experienced SharePoint consultants who understand your regulatory landscape ensures compliance continuity throughout the migration lifecycle.

Ready to execute a migration that preserves every document, permission, and compliance control? Our migration specialists have completed hundreds of enterprise SharePoint migrations with zero data loss across healthcare, financial services, and government sectors. Contact our team for a comprehensive migration assessment, and explore how our SharePoint consulting services can deliver a seamless transition that meets your timeline, budget, and compliance requirements.

Common Challenges and Solutions

Organizations implementing Workflow Migration consistently encounter obstacles that, if left unaddressed, undermine adoption and erode stakeholder confidence. Drawing on two decades of enterprise SharePoint consulting, these are the challenges we see most frequently and the proven approaches for overcoming them.

Challenge 1: Content Sprawl and Information Architecture Degradation

Over time, Workflow Migration environments accumulate redundant, outdated, and trivial content that degrades search relevance and confuses users. Without proactive content lifecycle management, the signal-to-noise ratio deteriorates and user trust in the platform erodes. The resolution requires a structured approach: establishing automated retention policies that flag content for review after defined periods of inactivity, combined with content owner accountability structures that assign clear responsibility for each site collection and library. Organizations that address this proactively report 40 to 60 percent fewer support tickets within the first 90 days of deployment. Establishing a dedicated governance committee with representatives from IT, compliance, and business stakeholders ensures ongoing alignment between technical configuration and organizational objectives.

Challenge 2: Compliance and Audit Readiness Gaps

Workflow Migration implementations in regulated industries often lack the audit trail depth and policy enforcement rigor required by frameworks such as HIPAA, SOC 2, and GDPR. Retroactive compliance remediation is significantly more expensive and disruptive than building compliance into the initial design. We recommend embedding compliance requirements into the information architecture from day one. Configure Microsoft Purview retention labels, DLP policies, and audit logging before deploying content, and validate compliance posture through regular internal audits. Tracking these metrics through SharePoint health dashboards provides early warning indicators that allow administrators to intervene before minor issues become systemic problems affecting enterprise-wide productivity.

Challenge 3: Inconsistent Governance Across Business Units

When different departments implement Workflow Migration independently, inconsistent naming conventions, metadata schemas, and security configurations create silos that undermine cross-functional collaboration and complicate compliance reporting. The most effective mitigation strategy involves centralizing governance policy definition while allowing controlled flexibility at the departmental level. A hub-and-spoke governance model balances enterprise consistency with departmental autonomy. Enterprises operating in regulated industries such as healthcare and financial services must pay particular attention to this challenge because compliance violations carry significant financial and reputational consequences. Regular audits conducted quarterly at minimum help organizations maintain alignment with evolving regulatory requirements and internal policy updates.

Challenge 4: Migration and Legacy Content Complexity

Organizations transitioning legacy content into Workflow Migration often underestimate the complexity of mapping old structures, metadata, and permissions to modern architectures. Failed migrations erode user confidence and create parallel systems that duplicate effort. Addressing this requires conducting thorough pre-migration content audits that classify and prioritize content based on business value. Invest in automated migration tools that preserve metadata fidelity and permission integrity while providing detailed validation reports. Organizations that invest in structured change management programs achieve adoption rates 35 percent higher than those relying on organic discovery alone. Executive sponsorship combined with department-level champions creates the organizational momentum necessary for sustained success.

Integration with Microsoft 365 Ecosystem

Workflow Migration does not operate in isolation. Its value multiplies when connected to the broader Microsoft 365 ecosystem, creating unified workflows that eliminate context switching and reduce manual data transfer between applications.

Microsoft Teams Integration: Embed Workflow Migration dashboards and document libraries as Teams tabs to create unified workspaces where conversations and structured content management coexist within a single interface. Teams channels automatically provision SharePoint document libraries, which means workflow migration configurations and content flow seamlessly between collaborative conversations and structured document management. Users can surface SharePoint content directly within Teams tabs, reducing the friction that typically causes adoption to stall.

Power Automate Workflows: Implement scheduled flows that perform routine Workflow Migration maintenance tasks including permission reports, content audits, and usage analytics without requiring manual intervention. Automated workflows triggered by SharePoint events such as document uploads, metadata changes, or approval completions eliminate repetitive manual tasks. Organizations typically automate 15 to 25 processes within the first quarter, saving an average of 8 hours per week per department. These automations also create audit trails that satisfy compliance requirements for regulated industries.

Power BI Analytics: Build executive dashboards that aggregate Workflow Migration metrics alongside other business KPIs, providing a holistic view of digital workplace effectiveness and investment returns. Connecting SharePoint data to Power BI dashboards provides real-time visibility into content usage patterns, adoption metrics, and operational KPIs. Decision makers gain actionable intelligence without requiring manual report generation, enabling faster response to emerging trends and potential issues.

Microsoft Purview and Compliance: Implement retention policies that automatically manage Workflow Migration content lifecycle, preserving business-critical records for required periods while disposing of transient content to reduce storage costs and compliance exposure. Sensitivity labels, data loss prevention policies, and retention schedules configured in Microsoft Purview extend automatically to workflow migration content. This unified compliance framework ensures that governance policies apply consistently across the entire Microsoft 365 environment rather than requiring separate configuration for each workload. For organizations subject to HIPAA, SOC 2, or FedRAMP requirements, this integrated approach significantly reduces compliance management overhead.

Getting Started: Next Steps

Implementing Workflow Migration effectively requires more than technical configuration. It demands a strategic approach grounded in your organization's specific business requirements, compliance obligations, and growth trajectory. The difference between a deployment that delivers measurable ROI and one that becomes shelfware often comes down to the quality of upfront planning and expert guidance.

Begin with a focused assessment of your current SharePoint environment. Evaluate your existing information architecture, permission structures, content lifecycle policies, and user adoption patterns. Identify gaps between your current state and the target state required for successful workflow migration implementation. This assessment typically takes 2 to 4 weeks and produces a prioritized roadmap that aligns technical work with business outcomes.

Our SharePoint specialists have guided organizations across healthcare, financial services, government, and education through hundreds of successful implementations. We bring deep expertise in SharePoint architecture, governance frameworks, and compliance alignment that accelerates time to value while minimizing risk.

Ready to move forward? Contact our team for a complimentary consultation. We will assess your environment, identify quick wins, and develop a phased implementation plan tailored to your organization's needs and timeline. Whether you are starting from scratch or optimizing an existing deployment, our enterprise SharePoint consultants deliver the expertise and accountability that Fortune 500 organizations demand.