Data MigrationMigrating SharePoint 2010/2013 workflows and InfoPath forms to Power Automate and Power Apps

SharePoint 2010 and 2013 workflows have been retired in SharePoint Online, and InfoPath has reached the end of its life, so any process that still depends on them needs rebuilding in Power Automate and Power Apps. There is no automatic converter that produces a good result: the reliable approach is to inventory what you have, decide what is still needed, then rebuild each process properly. Most organisations find that a sizeable share of old workflows can simply be switched off.

At the time of writing (October 2026). Microsoft's published timeline retired SharePoint 2010 workflows in SharePoint Online in 2020 and announced April 2026 as the retirement date for SharePoint 2013 workflows in existing SharePoint Online tenants. The InfoPath 2013 client and SharePoint Designer 2013 reached end of support in July 2026, alongside Microsoft's plans to remove InfoPath Forms Services from SharePoint Online. Check the Microsoft 365 Message Center for the exact position in your tenant, and note that on-premises SharePoint Server follows a different lifecycle.

What has changed and why it matters

Classic SharePoint workflows were built in SharePoint Designer or with out-of-the-box templates such as approval and three-state workflows. InfoPath forms gave SharePoint lists and libraries custom data-entry screens. Both technologies are now end of life in Microsoft 365.

In practice this means:

• Workflows on the retired platforms stop starting, and in-flight instances may stop.
• InfoPath forms can stop opening in the browser, and the desktop client no longer receives security updates.
• Nobody on your team may remember what the old workflow did, because it was built years ago by someone who has left.

If processes have already stopped, the priority is triage. If they are still limping along on SharePoint Server, you have time to plan, but not indefinitely.

Step 1: Find everything

You cannot migrate what you have not found. Microsoft provides the SharePoint Modernization Scanner, which reports classic workflows and InfoPath forms across a tenant. At the time of writing it can also give an initial view of how each workflow's actions map to Power Automate.

For each item, record:

Step 2: Decide what to keep

Hold a short review with each business owner. For every workflow and form, choose one of four outcomes.

• Retire: not used, or replaced by something else. Switch it off and document the decision.
• Replace with out-of-the-box features: list approvals, content approval, alerts or Microsoft Forms may do the job with no build at all.
• Rebuild as-is: the process is sound; recreate it in Power Automate and, for forms, Power Apps.
• Redesign: the old process was a workaround. Use the migration to fix it.

In our experience, the redesign conversations are where most of the value sits. Old workflows often encode email chains and manual checks that a modern flow or app can remove. Our approvals without email and paper forms to app use cases describe typical replacements.

Step 3: Map old concepts to new ones

Some patterns need more thought. Long-running state machine workflows can exceed flow run duration limits, so they are usually rebuilt as several smaller flows triggered by status changes. Repeating sections in InfoPath usually become child records in a separate list or table.

Step 4: Rebuild properly

A migration is a chance to fix the reasons old workflows were fragile.

• Use solutions. Build flows and apps inside solutions so they can be moved between development, test and production environments.
• Use connection references and a service account, so flows do not depend on one person's login. Our article on ownerless flows explains why.
• Check connectors early. Most SharePoint, Outlook and Teams actions are standard, so many replacements need no extra licences. Calling external web services usually means premium connectors and premium licences. See how much Power Platform costs.
• Keep data where it is where that makes sense. SharePoint lists remain a good data source for many processes. Move to Dataverse if you need relational data or stronger security.
• Add error handling, with notifications to a shared mailbox or Teams channel when a flow fails.
• Document each process in plain English for the business owner.

Step 5: Test, switch over and switch off

• Test with real users and real data in a test environment.
• Decide what happens to in-flight items under the old workflow: finish them manually, or migrate their status.
• Run the new process in production and confirm the first few cycles with the owner.
• Disable the old workflow or form and record the date.
• Keep an export of old workflow history if you need it for audit or retention reasons.

Typical effort and cost

Effort depends on the number of processes and how much redesign is involved. A simple approval workflow can often be rebuilt in a day or two including testing. A complex InfoPath form with repeating sections, rules and printing requirements can take considerably longer.

The most cost-effective approach is to batch similar processes. Our fixed-price Automation Sprint (from £1,750) is designed for rebuilding a defined set of approvals and notifications, and the Spreadsheet to App package suits larger form replacements. Every engagement gets a written fixed price before work starts. For broader moves, see our data migration and SharePoint services.

Migration checklist

• Run the SharePoint Modernization Scanner and export the results.
• Assign a business owner to every workflow and form.
• Classify each item: retire, out-of-the-box, rebuild or redesign.
• Agree a priority order based on business impact.
• Set up environments and a service account before building.
• Rebuild in solutions with connection references.
• Confirm licensing for any premium connectors.
• Test with real users, then plan the switchover of in-flight items.
• Disable old workflows and forms and record the decision.
• Hand over documentation to each owner.

Frequently asked questions

Can SharePoint workflows be converted to Power Automate automatically?

Not in a way we would rely on. Tools can map actions and give a useful starting point, but the old logic usually needs reviewing and rebuilding to work well in Power Automate.

What replaces InfoPath?

For most list forms, a Power Apps customised form. For more complex forms, a canvas app writing to SharePoint or Dataverse. Simple surveys may only need Microsoft Forms.

Do we need extra licences for the replacements?

Often not. Flows and apps using SharePoint, Outlook and Teams are covered by Microsoft 365. Premium connectors or Dataverse would need premium licences for users.

What about SharePoint Server on-premises?

On-premises SharePoint Server has its own support lifecycle and workflow engine. Check your version's support dates; many organisations use the migration to SharePoint Online as the moment to rebuild.

Our workflow has stopped. What should we do first?

Find out who depends on it, set up a temporary manual process, then prioritise a rebuild. Our support service handles urgent rescue work.

Key takeaways

• SharePoint 2010 and 2013 workflows and InfoPath are end of life in Microsoft 365.
• Inventory first, then decide what to retire, replace, rebuild or redesign.
• Rebuild in solutions with service account connections so the new processes outlast their builders.
• Many replacements need no extra licences, but check premium connectors early.
• Batch similar processes for a fixed price. If you want help planning the move, see our Power Automate service or book a call below.