Nintex alternatives: where to go and how to move your workflows
Seven destinations ranked by how well they replace Nintex, one per reason for leaving, plus an eight-step migration plan.
The short answer: Power Automate if your company runs on Microsoft 365 (your license already includes it with standard connectors), FlowForma if you want no-code forms and approval flows inside SharePoint, Kissflow if business teams should build their own processes, Appian for heavy enterprise processes, and n8n, Make or Zapier if your workflows mostly move data between cloud apps. If you'd rather stay, Nintex has its own exits: Nintex Automation K2 on your servers, or the cloud edition. One thing to know before you choose: no tool on the market turns a Nintex workflow into a Power Automate flow. You rebuild. We compared these seven destinations and their migration paths in 2026.
The ranking is editorial: a sponsored spot is always labeled on its card, and no affiliate link changes a score.
Why teams are leaving Nintex, and what still runs
For years, Nintex was the easiest way to bolt workflows (automated routes: a request, an approval, a notification) onto SharePoint. Most of the 2026 exits are driven by Microsoft, which retired the pieces Nintex was built on. The rest comes down to price and weight. Six reasons, each checked, with the nuance that matters: not everything is shutting down.
Nintex Workflow for Office 365 is done
Microsoft retired the SharePoint Add-In model from Microsoft 365 in 2026. As a result, the Nintex Workflow and Nintex Forms for Office 365 add-ins are no longer available. Workflows built with the add-in no longer run, and its forms no longer open. The only survivors are workflows upgraded to Nintex Workflow before the retirement, and forms moved to the New Responsive format on SPFx. If nothing was migrated in time, Nintex says it plainly: rebuild or replace.
Microsoft retired the old workflow stack
Nintex itself relays Microsoft's timeline: the SharePoint 2013 workflow engine left Microsoft 365 in 2026, and SharePoint Server 2016 and 2019 fell out of Microsoft support the same year. If your Nintex runs on one of those servers, the foundation no longer gets security patches, not just the add-in.
No new code for Nintex for SharePoint
The nuance first: Nintex for SharePoint 2016, 2019 and Subscription Edition is still supported, with no end-of-life date announced, and Nintex has said any future announcement would come with a support period after it. But Nintex has also said it will no longer push code updates for the product. It runs, it doesn't move forward. The SharePoint 2013 version is no longer supported at all.
A price nobody can read
Nintex publishes no pricing: its pricing URL sends you to a contact form. Even your cloud license details live in the console, or you ask your account manager. Users keep raising the same points: a license seen as expensive next to competitors, two tiers (standard and enterprise) that are hard to compare, and costly annual support.
Heavy on servers, dated on screen
User feedback lands on two things. On-premises Nintex is server-intensive. And the interface isn't seen as intuitive: you need to know the tool to find your way, which makes every admin departure a risk.
No automatic conversion on the way out
Microsoft's migration tool (SPMT) converts native SharePoint 2010 and SharePoint Designer workflows to Power Automate, not Nintex ones. ShareGate doesn't convert Nintex workflows into Power Automate flows. Leaving Nintex means rebuilding. Even staying takes a project: moving to K2, the import is partial and forms have to be redone.
You're leaving because… go to…
The right Nintex alternative depends on where your data lives and who will build the new workflows. Usually one card fits better than the rest. Each one jumps to the full card below.
Included in your Microsoft 365 license for standard connectors, Premium at $15 if needed.
You want no-code forms and approvals in SharePointFlowFormaBuilt for Microsoft 365, with credits to fund the move off Nintex.
Business teams should build their own processesKissflowLow-code platform, quote-based, fixed annual agreements.
Your processes are heavy, with bots and AIAppianPriced per user, per month, per app; RPA bots from the first plan.
Your workflows mostly connect cloud appsn8n or MakeBilled per execution or credit, not per user. n8n can be self-hosted.
You want to stay with NintexNintex Automation K2 or CEK2 on your servers, CE in the cloud: a partial import, and forms to rebuild.
Nintex alternatives, tool by tool
The cards are ranked by how relevant each tool is for leaving Nintex: first the ones that take over SharePoint workflows best, then the ones that replace part of what Nintex did. Appian ranks above n8n because it takes over full approval routes, while n8n mostly takes over data exchanges. Pega and ProcessMaker, often listed in roundups, aren't ranked here: they're platforms for large process management programs, oversized for replacing SharePoint approvals, and the ProcessMaker site now redirects to Decisions. NITRO Studio (from Crow Canyon) and skybow, often cited for on-premises SharePoint, aren't ranked either: they're forms and workflow tools built inside SharePoint and Microsoft 365 that also run on SharePoint Server, but we couldn't read any prices on their sites. If you're staying on your own servers, ask them for a quote. For each tool: why move to it, who it's for, its limit, how to migrate from Nintex, and what it costs. Prices are the ones shown in 2026, before tax, in the currency the vendor displays. Scores come from our full reviews when we've published one.
Power Automate: the natural exit for Microsoft 365
Most relevantWhy move to Power Automate. If your Nintex workflows live in SharePoint Online, Power Automate is already in the building. It's Microsoft's automation tool, and the first destination integrators point to. That also means the pitfalls of this move are the best known.
Who it's for. Companies whose data and users sit in Microsoft 365, with an IT team able to take over the workflows.
Who it's not for. A team that wants business users to build everything with no training. Power Automate is approachable, but a clean approval workflow takes discipline. Same for Nintex on SharePoint Server 2016, 2019 or SE: Power Automate is a cloud service, so you first move to SharePoint Online or install an on-premises data gateway (the SharePoint connector supports it for SharePoint 2016 and 2019).
Its limit. According to integrators, a flow can't wait for weeks or months, and standard approvals expire. A long sign-off has to be built differently (see step 6 of the plan). Forms move to Power Apps, a second tool to learn.
How to migrate from Nintex. No conversion: SPMT ignores Nintex workflows, and ShareGate won't turn them into flows. The path is inventory, an action mapping table, a flow-by-flow rebuild, and list content migrated separately. For a Nintex state machine, store the state in a list column and make each transition its own flow.
Price. Included in Microsoft 365 licenses with standard connectors (SharePoint, Approvals, Outlook). Premium is $15 per user per month, paid yearly, for premium connectors, Dataverse and one attended bot. Process is $150 per bot per month for desktop automation, Hosted Process $215 per bot on a Microsoft-hosted machine. There's a 30-day free trial. To see what people dislike about it, read our page on leaving Power Automate.
- Price
- included in Microsoft 365 (standard connectors), Premium from $15
- Trial
- 30 days
- Best for
- companies on Microsoft 365
- Limit
- long approvals need a redesign
FlowForma: no-code forms and approvals inside SharePoint
Migration creditsWhy move to FlowForma. FlowForma picks up the idea that made Nintex popular: a form plus an approval route, all inside SharePoint and Microsoft 365, built without a developer. It openly targets Nintex customers and offers migration credits to help fund a move from Nintex or Power Automate. Eligibility is decided on a call with the vendor.
Who it's for. Microsoft 365 organizations whose processes are mostly form-driven (purchase requests, leave, expenses, quality checks) and who want business teams to build them.
Who it's not for. Anyone outside Microsoft 365. The vendor says so itself: the tool isn't meant for them.
Its limit. The entry price. It's billed by number of processes and starts high: a department with two or three small workflows will pay more than with Power Automate.
How to migrate from Nintex. You rebuild your forms and routes in FlowForma. Before signing, ask whether your project qualifies for migration credits, and get a quote for rebuilding your longest workflows.
Price. Published and billed yearly: Essentials from $2,347 per month for 3 processes, Professional from $3,293 per month for 30 processes, Enterprise on quote.
- Paid
- from $2,347 / month (3 processes)
- Billing
- annual
- Best for
- form-driven processes in Microsoft 365
- Limit
- pricey for a handful of processes
Kissflow: when business teams build their own processes
Quote-basedWhy move to Kissflow. Kissflow is a low-code platform (you build apps by assembling blocks, with little code) for processes and approval flows. The vendor pitches itself as a Nintex alternative. Forms, workflows, apps and portals run on a single model. And it promises no shortcut: your Nintex workflows on SharePoint and Office 365 have to be rebuilt. The upside: your processes leave SharePoint, so they stop depending on Microsoft's retirement calendar.
Who it's for. Companies that want business teams to create and change their own processes without filing an IT ticket every time.
Who it's not for. A team that wants its forms to stay at the heart of SharePoint. Power Automate or FlowForma are closer to what you have.
Its limit. No published price. You'll only know what you pay after a sales conversation, just like with Nintex.
How to migrate from Nintex. There's no Nintex import: you rebuild each flow. Use your inventory to start with the simple processes that have the most users, and leave the tricky ones for last.
Price. On quote. The vendor advertises fixed annual agreements, with no surcharges for AI or API usage (the API is how two pieces of software exchange data).
- Price
- on quote, fixed annual agreement
- Best for
- processes built by business teams
- Limit
- no public price
Appian: for heavy enterprise processes
EnterpriseWhy move to Appian. Appian is a process automation platform for large organizations. It combines workflows, RPA bots (software that clicks through screens that have no connector) and AI actions. If your Nintex workflows ran regulated case files or cross-department routes, it's a step up.
Who it's for. Enterprises with a team to build and maintain process applications.
Who it's not for. A mid-size company replacing ten approval workflows. The platform is far bigger than the need.
Its limit. No price on the page, and billing is per user, per month, per app. The more apps you build, the more the bill follows.
How to migrate from Nintex. Appian doesn't plug into SharePoint out of the box: you take your processes out of SharePoint and rebuild them. Start in the free Community Edition, which gives you a dedicated Appian instance: rebuild one representative Nintex workflow there before you sign.
Price. On quote. Three plans: Standard with 5 RPA bots and 200K AI actions a month, Advanced with 25 bots and 500K, Premium with unlimited bots and 1M.
- Price
- on quote, per user and per app
- Free
- Community Edition
- Best for
- enterprises, regulated processes
- Limit
- bill grows with each app
n8n: workflows on your own servers, billed per execution
Labs score 4.2Why move to n8n. Plenty of Nintex workflows aren't approvals at all: they copy data from one system to another, send an alert, fill a table. For that, n8n is often a better fit. It bills per execution, not per user, and it can run on your own servers, which matters if you're leaving on-premises Nintex.
Who it's for. Technical teams that want control over hosting and like wiring APIs.
Who it's not for. Business users who want to fill a request form and get it approved. n8n has basic forms (the n8n Form node) and wait-for-approval steps, but no business form designer like Nintex Forms.
Its limit. Getting started takes real technical skills, and multi-level approval routes are yours to build.
How to migrate from Nintex. In your inventory, flag the workflows that move data with no human approval. Those go to n8n; approval routes go elsewhere. More in our full n8n review.
Price. n8n bills in euros. Starter at €20 a month billed yearly (about €24 monthly) for 2,500 executions, Pro at €50 a month billed yearly (about €60) for 10,000 executions, Business at €667 a month self-hosted.
- Labs score
- 4.2 / 5
- Paid
- Starter €20, Pro €50 / month
- Best for
- technical teams, self-hosting
- Limit
- basic forms, no business form designer
Make: visual scenarios on a small budget
Labs score 4.1Why move to Make. Make builds workflows (it calls them scenarios) by linking blocks on a canvas, no code needed. For Nintex workflows that sync cloud apps or send notifications, it's an approachable, low-cost replacement.
Who it's for. Small and mid-size teams that want to automate work between cloud apps without a dedicated IT team.
Who it's not for. An organization that must keep its data on its own servers: Make is a hosted service.
Its limit. Make is built to connect apps: for business forms and approval routes, look at Power Automate or FlowForma instead. And the bill follows the credits you burn, so count your runs before picking a plan.
How to migrate from Nintex. Rebuild one data-moving workflow at a time, working from your mapping table. More in our full Make review.
Price. Core at $9 a month billed yearly, for 10,000 credits.
- Labs score
- 4.1 / 5
- Paid
- Core $9 / month billed yearly
- Best for
- SMBs, app-to-app flows
- Limit
- billed on credits used
Zapier: small flows, set up in an hour
Labs score 3.8Why move to Zapier. Zapier connects two apps very simply: one trigger, one or more actions, and it's live. For the small Nintex workflows that sent an email or created a row somewhere else, it's often an hour's work.
Who it's for. Non-technical business teams that want to take back their simple automations themselves. Zapier also includes forms, even on the free plan, for a simple request that kicks off a flow.
Who it's not for. High volumes and multi-step approval routes: the bill climbs fast and the logic gets hard to read.
Its limit. Volume pricing. Zapier bills each task: 750 tasks on the first paid plan, and $129 a month billed yearly for 10,000 tasks. Past a few thousand tasks a month, compare with Make or n8n.
How to migrate from Nintex. Keep Zapier for short workflows. Count each Nintex workflow's monthly runs before choosing a plan, or the first invoice will surprise you. More in our full Zapier review.
Price. Professional at $19.99 a month billed yearly ($29.99 monthly) for 750 tasks.
- Labs score
- 3.8 / 5
- Paid
- $19.99 / month billed yearly
- Best for
- small flows built by business teams
- Limit
- expensive at volume
The 7 Nintex alternatives side by side
Our default picks: Power Automate if you're on Microsoft 365, FlowForma if you want SharePoint-style forms without a developer. Prices don't line up row by row, because each vendor bills a different unit: the user at Power Automate, the number of processes at FlowForma, the user and the app at Appian, the execution at n8n, the credit at Make, the task at Zapier. To put numbers on it: for SharePoint approvals on standard connectors, 20 people pay nothing beyond their Microsoft 365 licenses. If they need premium connectors, Dataverse or an attended bot, it becomes 20 × $15 = $300 a month in Premium licenses, while FlowForma starts at $2,347 a month for 3 processes, whatever the headcount. Kissflow and Appian are quote-based.
| Published entry price | Migration from Nintex | |
|---|---|---|
| NintexWhere you start | Quote-based: the pricing page redirects to a contact form | Office 365: add-ins retired, only workflows upgraded before the retirement still run; to K2: partial import, forms rebuilt |
| Power AutomateMicrosoft 365 | Included in Microsoft 365 (standard connectors); Premium $15 per user per month; 30-day trial | Rebuild: neither SPMT nor ShareGate converts Nintex |
| FlowFormaNo-code SharePoint | Essentials from $2,347 per month (3 processes), annual | Migration credits if eligible; rebuild in the tool |
| KissflowBusiness teams | Quote-based, fixed annual agreement | Rebuild your approval flows in Kissflow |
| AppianEnterprise | Quote-based, per user, per month, per app; free Community Edition | Rebuild; RPA bots for screens with no connector |
| n8nSelf-hostable | Starter €20 per month billed yearly, 2,500 executions | Rebuild your app-to-app flows |
| MakeVisual, low budget | Core $9 per month billed yearly, 10,000 credits | Rebuild your app-to-app flows |
| ZapierSmall flows | Professional $19.99 per month billed yearly, 750 tasks | Rebuild your simple flows |
Prices taken in 2026 from each vendor's official pricing page, before tax. Quote-based: the vendor publishes no amount.
Migrating off Nintex in eight steps
Order matters. The first steps tell you how much time you have left; the next ones protect your data, your in-flight approvals and your forms.
Inventory your Nintex workflows and forms
Step 1List every workflow and form with three facts: the Nintex product (Office 365, SharePoint 2016, 2019 or Subscription Edition, cloud), the site it runs on, and when it last ran. Note the Nintex actions it uses too.
With more than a hundred workflows, this sort changes everything: a good share hasn't run in ages, and nothing forces you to rebuild what nobody uses.
- Deliverable
- a sheet, one row per workflow
- Risk if rushed
- a forgotten workflow
Place each workflow on the timeline
Step 2Not everything is equally urgent. Nintex for Office 365 workflows come first: unless they were upgraded before Microsoft retired SharePoint add-ins in 2026, they no longer run. Check which ones still run in your Microsoft 365 environment, then rebuild the rest from your inventory and exports. Workflows on SharePoint Server 2016 or 2019 depend on a server that left Microsoft support in 2026. Nintex for SharePoint Subscription Edition is still supported with no end date announced.
Sort your inventory in that order. That's your schedule.
- Most urgent
- Nintex for Office 365
- Least urgent
- SharePoint Subscription Edition
Decide: stay with Nintex or leave
Step 3Staying is a real option. Nintex offers Nintex Automation K2 to keep workflows on your servers, Nintex Automation CE in the cloud, or a hybrid. For Nintex Workflow for Office 365, the Workflow Upgrade Tool worked before the add-in retirement: workflows upgraded in time run in Nintex Workflow, the others get rebuilt. Ask Nintex, or a Nintex Modernization Program partner, what can still be carried over.
But staying is a project too. For K2, the K2 Workflow Importer (built into K2 Five 5.9) is an accelerator, not a one-click migration: unsupported actions show up as placeholders carrying the original Nintex action name. And Nintex Forms don't import; they're rebuilt in SmartForms. If you're rebuilding anyway, compare with the cards above before you renew.
- On-premises
- Nintex Automation K2
- Cloud
- Nintex Automation CE
- Forms
- rebuilt in SmartForms
Write the action mapping table
Step 4For each Nintex action in your inventory, write its equivalent in the target tool: an approval request, an item update, an email, a loop. Actions with no direct match are your hard spots; isolate them early.
The table does double duty: it sizes the project, and it makes everyone who rebuilds a workflow do it the same way.
- Deliverable
- a Nintex action to target action table
Move lists and libraries separately
Step 5Content (lists, libraries, content types) and logic (workflows) travel on two different paths. Move the content first, then hook the new workflows onto it.
Watch the history: even for native SharePoint workflows, Microsoft's migration tool moves definitions and associations, not run history. If you have to prove who approved what, export that history before switching off.
- What doesn't come along
- workflow run history
Rebuild state machines and long approvals
Step 6A Nintex state machine (a workflow that moves between statuses: submitted, in review, approved, rejected) doesn't copy over as-is. According to integrators, Power Automate doesn't support indefinite waits, and its standard approvals expire.
The approach they recommend: store the state in the data (a SharePoint list column or a Dataverse table) and build one flow per transition. Each flow stays short, and a sign-off can take a month without breaking anything.
- Method
- status in a list, one flow per transition
- Avoid
- one flow waiting for weeks
Rebuild the forms
Step 7No path imports a Nintex form automatically, whether you go to Power Apps, K2 or somewhere else. Use the moment to simplify.
A trap integrators know well: repeating sections in Nintex forms (rows you add on the fly, like expense lines). For Power Apps, that data has to be pulled out into a separate list.
If your Nintex forms sit next to InfoPath forms, handle them in the same project: Microsoft ended InfoPath support in 2026.
- Hard spot
- repeating sections
Run in parallel, then cut over
Step 8Run the old and new workflow side by side for one full cycle (a month of requests, say), with a few pilot users. Finish in-flight approvals in Nintex before switching each workflow off.
Then cut over workflow by workflow, and keep the inventory current down to the last row.
- Suggested length
- one full request cycle
Is your tool missing from this page? Email us: hello@hackceleration.com
What makes a Nintex migration fail
The same mistakes show up again and again on the Nintex and Microsoft forums. Almost none of them are technical: they're wrong assumptions about what migration tools can do.
Betting on a converter
SPMT converts native SharePoint workflows, not Nintex ones. ShareGate doesn't convert Nintex workflows into Power Automate flows. A plan built on automatic conversion slips in week one. Budget for rebuilding.
Copying action for action
A 2016 Nintex workflow copied as-is into Power Automate makes a brittle flow. Use the rebuild to cut steps nobody uses and merge workflows that do the same job.
Forgetting approvals in flight
The day you switch off the old workflow, some requests are halfway through. If you don't finish them in Nintex or pick them up by hand, they vanish and nobody notices.
Parking a long approval in a waiting flow
According to integrators, Power Automate can't wait for weeks and its approvals expire. A month-long sign-off is built with a status stored in a list and one flow per state change.
Assuming history comes along
Even for native workflows, Microsoft's tool moves definitions and associations, not run history. If auditors need to know who approved what, export that history before you switch off.
Letting SharePoint Server 2016 or 2019 age
Microsoft support for SharePoint Server 2016 and 2019 ended in 2026: no more security patches. Your workflows still run, but on a foundation that turns into a security and compliance risk. Waiting for an outage to move means migrating under pressure, with business teams stuck. It already happened on Office 365, where workflows that weren't upgraded stopped with the add-in retirement.
- A list of every Nintex workflow and form, with its product and server
- Dead workflows deleted before anything gets rebuilt
- A mapping table from Nintex actions to the target tool
- Long approvals designed around a status in a list
- Run history exported if you need it for audits
- Old and new workflow running side by side for one full cycle before cutover
Nintex alternatives: frequently asked questions
What is the best Nintex alternative?
For a company on Microsoft 365, Power Automate: it works on your SharePoint lists with the Microsoft 365 license you already have, through standard connectors; Premium is $15 per user per month if you need premium connectors. If you want no-code forms inside SharePoint, look at FlowForma, which offers credits to fund the move off Nintex.
Do my Nintex for Office 365 workflows still work?
No, unless they were upgraded to Nintex Workflow before the retirement. Microsoft retired the SharePoint Add-In model in 2026: the Nintex Workflow and Nintex Forms for Office 365 add-ins are no longer available, and users who open them see an unavailable message. On the forms side, only forms moved to the New Responsive format on SPFx still work. Check what still runs in your Microsoft 365 environment, and ask Nintex what can still be carried over: everything else gets rebuilt.
Can I convert Nintex workflows to Power Automate automatically?
No. Microsoft's SharePoint Migration Tool converts native SharePoint 2010 and SharePoint Designer workflows, not Nintex ones. ShareGate doesn't convert them either. You rebuild, starting from an action mapping table.
What replaces Nintex on SharePoint Server Subscription Edition?
Nothing has to yet: Nintex for SharePoint Subscription Edition is still supported, with no end date announced, though Nintex no longer pushes code updates. If you want to stay on-premises long term, Nintex points to Nintex Automation K2; for app-to-app flows, n8n can be self-hosted.
How much does Nintex cost?
Nintex doesn't publish prices: its pricing page redirects to a contact form. Figures floating around review or procurement sites aren't vendor prices. To compare, ask Nintex for a quote on the same scope as your other quotes.
Should I stay with Nintex on K2 or Automation CE?
It makes sense if you're committed to Nintex or must stay on your own servers with K2. But the K2 import is partial and forms are rebuilt in SmartForms. Since you're rebuilding part of it anyway, compare with Power Automate before renewing.
Is there a free Nintex alternative?
If you already have Microsoft 365, yes: your license includes Power Automate with standard connectors (SharePoint, Approvals, Outlook), enough for most SharePoint approval flows. Premium at $15 is only needed for premium connectors, Dataverse or bots. Outside Microsoft 365, Appian has a free Community Edition to try things out. For small app-to-app flows, Make starts at $9 a month billed yearly. Our ranking of approval workflow software goes further.
Nintex or Power Automate: which one?
Power Automate if you're on Microsoft 365 and accept rebuilding your workflows: it's included in your Microsoft 365 license for standard connectors, and its Premium price is public ($15 per user per month), while Nintex's isn't. Nintex if you want to stay on your servers with K2. If you also need bots that click through software with no connector, Power Automate Process costs $150 per bot per month; our RPA software ranking compares the other options.
Get the next migration guide in your inbox
One tool to leave, one destination, one migration plan. Nothing else.
