“Migration of workflows failed” – Migration of workflows from older versions of SharePoint failed.

Migration of Workflows Failed – Troubleshooting Guide for SharePoint Workflow Migration

Migrating workflows from older versions of SharePoint (2010/2013) to newer versions (2016, 2019, or SharePoint Online) can be challenging, especially when dealing with deprecated features, compatibility issues, and unsupported workflow actions. If your SharePoint workflow migration fails, follow this step-by-step troubleshooting guide to identify and resolve issues.

---

Step 1: Identify the Type of Workflow

Before troubleshooting, determine what type of workflow is failing:

1. SharePoint 2010 Workflows (Retired in SharePoint Online – August 2020)
2. SharePoint 2013 Workflows (Still supported, but may require updates)
3. SharePoint Designer Workflows (Custom-built, may require modifications)
4. Power Automate Workflows (New alternative for SharePoint Online)

🔍 Solution: If migrating from SharePoint 2010, consider rebuilding the workflow in Power Automate, as 2010 workflows are no longer supported in SharePoint Online.

---

Step 2: Verify SharePoint Workflow Services

1. Check if the Workflow Service is Running (for SharePoint On-Premises): Get-SPServiceInstance | Where-Object {$_.TypeName -like "*Workflow*"}
   • If it’s not running, restart it: Restart-Service -Name SPWorkflowService
2. For SharePoint 2013 Workflows:
   • Ensure the Workflow Manager 1.0 is installed and connected to SharePoint.
   • Run the following to check the connection: Get-WFFarm
   • If disconnected, reconnect Workflow Manager: Register-SPWorkflowService -SPSite "https://yoursharepointsite" -WorkflowHostUri "http://workflowserver:12291"

---

Step 3: Check Migration Logs for Errors

• If you used a third-party migration tool, check its logs for errors.
• If migrating manually, enable verbose logging in ULS logs:
  • ULS log location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\
  • Look for errors related to workflow migration.

---

Step 4: Test Workflows in the Source Environment

Before migrating, confirm that workflows run successfully in the old SharePoint version:

• Go to SharePoint Designer → Open the workflow → Check for Errors.
• If the workflow fails, fix errors before migrating.

---

Step 5: Migrate Workflows Separately

Instead of migrating workflows along with sites/libraries, export and import them separately:

1. Export Workflows from SharePoint Designer:
   • Open SharePoint Designer → Click Workflows.
   • Select a workflow → Click Export to Visio (.vwi file).
2. Import into the New Environment:
   • Open SharePoint Designer in the target site.
   • Click Workflows → Import from Visio.
   • Reconfigure any missing actions or connections.

---

Step 6: Check for Deprecated Workflow Actions

Some workflow actions are deprecated or changed in newer SharePoint versions.

1. Common Deprecated Actions in SharePoint 2013+:
   • “Start Approval Process” → Use Power Automate Approvals instead.
   • “Collect Data from User” → Use custom forms or Microsoft Forms.
   • “Pause Until Date” → Use Delay Until action in Power Automate.
2. Check for Custom Workflow Activities:
   • If the workflow contains custom workflow actions, they may not migrate correctly.
   • Recreate these actions using Power Automate or SharePoint Designer 2013.

---

Step 7: Update Workflow Permissions

If workflows fail after migration, check permissions:

1. Ensure the workflow runs as an authorized user (not an expired account).
2. Verify that the Workflow App Permissions are granted in SharePoint Online:
   • Open Site Settings → Site App Permissions.
   • Ensure the workflow app has Full Control permissions.

---

Step 8: Test and Re-Publish Workflows

After migration, test the workflows:

1. Open SharePoint Designer → Select the migrated workflow.
2. Click Edit Workflow → Save and Publish.
3. Run a test to ensure it executes as expected.

---

Step 9: Consider Power Automate as an Alternative

If migrating to SharePoint Online, it is recommended to rebuild workflows in Power Automate instead of fixing old SharePoint Designer workflows.

• Advantages of Power Automate:
  ✅ Modern, cloud-based automation.
  ✅ Supports Microsoft 365 integrations.
  ✅ Easier to manage and update.

---

Step 10: Contact Microsoft Support or Use Third-Party Migration Tools

If workflows still fail to migrate, consider:

1. Using Microsoft’s SharePoint Migration Tool (SPMT) for better workflow compatibility.
2. Using a third-party migration tool like ShareGate or Metalogix.
3. Contacting Microsoft Support for advanced troubleshooting.

---

Final Recommendations

✅ Test workflows in the source environment before migrating.
✅ Migrate workflows separately from site content.
✅ Recreate deprecated workflow actions in Power Automate.
✅ Ensure Workflow Manager is properly configured (for On-Premises migrations).
✅ Check and update permissions after migration.

By following these steps, you can effectively troubleshoot and resolve workflow migration failures in SharePoint.