Get a Scope
Migration guide

How to migrate from Power Automate to n8n

The short answer

Moving from Power Automate to n8n means rebuilding each cloud flow as an n8n workflow; there is no importer for exported flow JSON. Conditions, Switch and Apply to each map cleanly to n8n nodes, but desktop flows, approvals and Dataverse dependencies need planning. Most teams move non-Microsoft and premium-connector flows first and keep simple Microsoft 365 flows where they are.

ConceptPower Automaten8n
Cloud flowAutomated, instant or scheduled cloud flowWorkflow with an app trigger node, Webhook node or Schedule Trigger node
Connector and actionStandard, premium or custom connector actionsApp nodes, or the HTTP Request node for any REST API
ConnectionsConnections, and connection references inside solutionsCredentials, shared within an n8n project
ConditionCondition action with yes and no branchesIf node
SwitchSwitch action on a single valueSwitch node with rules or expressions
LoopsApply to each and Do untilNodes process every item automatically; Loop Over Items for batching; an If node looping back for do-until logic
Variables and ComposeInitialize variable, Set variable and Compose actionsEdit Fields (Set) node and expressions
ExpressionsWorkflow Definition Language functions such as concat() and formatDateTime()JavaScript expressions inside double curly braces, plus the Code node
Child flowsRun a Child Flow action, for flows inside a solutionExecute Sub-workflow node and Execute Sub-workflow trigger
Error handlingConfigure run after, Try and Catch scopes, retry policy, Terminate actionPer-node On Error setting with an error output, Retry On Fail, Stop and Error node, error workflow
HTTP triggerWhen an HTTP request is received trigger, a premium featureWebhook node, included in every n8n edition
Desktop flowsDesktop flows for UI automation on WindowsNo direct equivalent; replace with an API call, or keep the desktop flow and call it
PackagingSolutions moved between environments as zip filesWorkflow JSON export, projects, and Git-based source control on paid plans

Stay on Power Automate if

  • Most of your flows connect Microsoft 365 apps using connectors your licenses already include
  • You rely on Dataverse, model-driven apps or Power Apps that call flows
  • IT governs automation through Power Platform environments and data loss prevention policies
  • You depend on desktop flows to automate Windows applications that have no API

Move to n8n if

  • Many flows need premium connectors or the HTTP trigger, so per-user licensing is growing
  • Your important systems are outside Microsoft, such as HubSpot, Stripe, Shopify or Postgres
  • Flows have grown into deep nests of scopes and conditions that are hard to debug
  • You are building AI agents and want to choose models, tools and memory yourself
  • You want automations self-hosted in your own cloud account

Why teams migrate

Power Automate is a strong choice inside Microsoft 365. Teams move away from it when their work stops being mostly Microsoft.

Licensing friction. Standard connectors come with many Microsoft 365 plans, but premium connectors, the HTTP request trigger and custom connectors require premium Power Automate licensing, typically per user or per flow. When a company’s core systems are Salesforce, HubSpot, Stripe or a Postgres database, more and more flows need premium features. Check Microsoft’s current licensing guide for your plan.

Maintainability. Large flows with nested scopes, run-after settings and long expressions are hard to read and test. n8n shows the input and output of every node for each execution, which makes debugging faster.

AI and openness. n8n lets you run AI agents with your choice of model, call any API with the HTTP Request node and self-host the whole platform. For a feature-level view, read n8n vs Power Automate.

The migration plan

  1. Inventory. List every cloud flow by environment, owner, trigger, connectors used (marking premium ones), run frequency and whether it sits in a solution. Export the solutions so you have each flow’s JSON definition.
  2. Prioritize. Move first the flows that use premium connectors, connect non-Microsoft systems or fail often. Leave simple Microsoft-only flows, such as saving Outlook attachments to OneDrive, unless you are retiring Power Automate entirely.
  3. Prepare n8n and Microsoft access. Stand up n8n, then register an app in Microsoft Entra ID with the narrowest permissions each workflow needs and get admin consent. Set up an error workflow and alerting.
  4. Rebuild. Use the mapping table. Rewrite Workflow Definition Language expressions as n8n expressions. Replace Try and Catch scopes with error outputs on the nodes that can fail and a shared error workflow.
  5. Run in parallel. Run the n8n workflow on the same inputs with final writes disabled or pointed at a test list, and compare with the flow’s run history for a full business cycle.
  6. Cut over. Repoint any system that calls an HTTP trigger URL to the n8n Webhook URL, enable the n8n trigger, and turn off the cloud flow in the same window.
  7. Decommission. Leave flows turned off for 30 days, then remove them from their solutions and release premium licenses you no longer need.

What to watch for

  • Webhook and trigger URLs change. HTTP trigger URLs in Power Automate are generated per flow. Every caller must be updated to the n8n production webhook URL.
  • Re-authorization and tenant consent. Microsoft connections cannot move to n8n. Plan for admin consent on a new app registration, and use application permissions only where the workflow genuinely needs tenant-wide access.
  • Approvals in flight. Approvals waiting on a person will still complete in Power Automate after you switch. Let them drain before turning the flow off.
  • Duplicates during overlap. Triggers such as When a new email arrives or When an item is created will fire in both systems if both are on. Use a unique key check before create or send steps, or run the n8n side read-only until cutover.
  • Throttling. Microsoft Graph and SharePoint apply request limits. Batch requests and use Retry On Fail with a wait between tries.
  • Hidden dependencies. Power Apps buttons, Copilot Studio agents and other flows may call the flow you are moving. Search solutions for references before turning anything off.

Timeline and cost

A single flow, rebuilt and run in parallel, fits our single workflow automation band of $2,500–$12,000 and typically takes 1–3 weeks. A program of 5–15 flows is typically $15,000–$50,000 over 4–10 weeks. Flows that drive desktop automation or approvals with compliance requirements sit toward the top of those ranges. Our n8n automations suite case study shows how we structure production n8n work, and the approval workflow guide covers one of the most common flows we rebuild.

What we recommend

Do not migrate for its own sake. If your flows are mostly Microsoft 365 and your licenses cover them, Power Automate is the sensible home. If premium licensing, non-Microsoft systems or AI agents are driving cost and complexity, move those flows to n8n first and keep the rest where they work.

Frequently asked questions

Can n8n import a Power Automate flow?

No. Power Automate exports flows as JSON inside a solution or package zip, and n8n cannot import that format. The exported definition is still useful during the rebuild because it lists every action, expression and run-after setting in the flow.

Does n8n work with Microsoft 365?

Yes. n8n has nodes for Outlook, Microsoft Teams, Excel, OneDrive, SharePoint and Entra ID, authenticated through an app registration in your Microsoft tenant. Your Microsoft 365 admin will need to approve the app and its permissions.

What replaces Power Automate approvals?

n8n can send a message in Slack, Microsoft Teams, Outlook or Gmail and pause the workflow until someone approves or replies, using the Send and Wait for Response operation. For audit trails, write each decision to a database or SharePoint list.

What should we do with desktop flows?

First check whether the application now has an API, since that is the more reliable path. If it does not, keep the desktop flow and let n8n trigger it, or plan a broader move as described in our RPA to AI agents migration guide.

How long does the migration take?

One flow typically takes 1–3 weeks with a parallel run. A program of 5–15 flows typically takes 4–10 weeks. Tenant approval for the Microsoft app registration is often the slowest single step, so start it in week one.

Next steps

01 Browse free n8n templates Fifty starter workflows you can import today. No email required. 02 Take the 5-minute AI readiness assessment Get a score and a recommended first project in your browser. 03 Get a written scope and estimate Tell us what you want to automate. We reply within two business days.

Keep reading

Last updated October 14, 2026. Product details change often; check each vendor's current documentation and pricing.