Why Nintex Cloud Isn’t the Default Migration Path for On-Premise Companies

Most organizations running Nintex on-premise workflows assume the next stop is Nintex Automation Cloud. The migration tooling points there. The vendor messaging points there.

Here’s the part that gets missed: Nintex itself doesn’t actually recommend that path for everyone. On its own end-of-support page, Nintex routes a specific class of on-premise customers toward its self-hosted product, not its cloud. If your organization fits that description, the migration deadline isn’t a forcing function to move to the cloud. It’s a forcing function to actually evaluate where you should land.

This piece is for organizations weighing that decision honestly.

Key Points:

• Nintex’s own end-of-support page recommends Nintex Automation K2 (self-hosted) over Nintex Automation CE (cloud) for organizations with strict data residency, air-gapped or high-security environments, complex non-linear workflows, regulated industries requiring full data control, or large-scale automation with predictable costs.
• Nintex Cloud uses two licensing models, both with overage charges. The cost is a different shape, not just a different number.
• Nintex Cloud needs a Nintex Gateway server installed inside your network to reach on-premise systems, so the on-prem footprint doesn’t actually go away.
• There’s no lift-and-shift to Nintex Cloud. Workflows have to be rebuilt regardless of where you land.
• Since you’re rebuilding either way, this is the moment to compare every viable option, including modern Nintex Cloud on-premises alternatives that cover SharePoint Online, SharePoint on-prem (2016/2019/SE), GCC, GCC High, and air-gapped environments under one platform and one flat-rate license.

Here’s what’s retiring, and when

Per Nintex’s Microsoft End of Support page and Nintex’s community announcements, the timeline is:

Nintex extends limited support past Microsoft’s end dates, but per its subscription support policy, that support is restricted to troubleshooting, identifying workarounds, and resolving critical security issues. Not new functionality, not feature parity.

Nintex doesn’t actually push every on-prem customer to the cloud

This is the most useful thing on Nintex’s own website, and it’s hiding in plain sight.

On the Microsoft End of Support page, Nintex presents two destination platforms.

Nintex Automation K2 (self-hosted) is recommended for:

• Organizations with strict data residency requirements
• Air-gapped or high-security environments
• Complex, non-linear workflow requirements
• Regulated industries requiring full data control
• Large-scale process automation with predictable costs

Nintex Automation CE (cloud) is recommended for:

• Cloud-forward organizational strategies
• Rapid scalability and growth requirements
• Reduced IT overhead
• Access to the latest features and capabilities
• Global collaboration and remote workforces

Read those lists carefully. Most Nintex on-premise customers ended up on-premise because of the criteria in the first list. Nintex’s own page is telling you the cloud isn’t designed for your scenario.

That’s the moment to widen the evaluation, not narrow it. Nintex Automation K2 is one option. Modern third-party Nintex Cloud on-premises alternatives are another. The cloud is also still on the table for parts of your environment. But none of these answers should be assumed by default.

The pricing model isn’t just more expensive. It’s a different shape.

Nintex on-premise was typically licensed per server with predictable annual maintenance. Nintex Automation Cloud uses a different commercial structure than on-prem buyers should map carefully before signing.

Per FlowForma’s published breakdown of Nintex pricing, Nintex Automation Cloud is sold under two licensing models:

• Workflow consumption. Unlimited users, billed per workflow execution.
• User-based with capped workflow capacity. Fixed user fee, hard limit on executions before overage charges apply.

Both models charge for overages. Vendr’s marketplace data places small to mid-sized cloud deployments (10 to 50 users, standard workflow automation) in the $15,000 to $40,000 annual range, mid-market multi-module deployments at $50,000 to $200,000, and enterprise deployments at $200,000 to $500,000 or more, with implementation packages billed separately.

User reviews on Capterra, Software Advice, and TrustRadius repeatedly flag licensing complexity, overage charges, and renewal cost growth as the biggest pain points with Nintex.

For an on-premise migrator, the question isn’t the year-one quote. It’s the year-two and year-three quote at your real workflow execution volume, which is hard to predict before the platform is live.

Going hybrid means you still own on-premise infrastructure

If your environment still has on-premise data sources, Nintex Automation Cloud reaches them through Nintex Gateway, an on-premise Windows service installed inside your network.

Per Nintex’s official Gateway documentation, Gateway is required to connect Nintex Workflow to:

• SharePoint on-premises
• Microsoft SQL Server on-premises
• Nintex RPA and Nintex RPA Central
• Local web services and custom on-premise APIs

Most connector types require Gateway to be installed on a server joined to your Active Directory domain. And per the Nintex Gateway release notes, the upgrade from version 2.1.x to 2.2.2 required uninstalling and reinstalling Gateway, recreating the connection to Nintex Workflow Cloud, and updating every dependent connector reference.

Translation: moving from Nintex on-premise to Nintex Cloud doesn’t actually eliminate your on-premise responsibilities if you still run on-premise systems. It splits them across two control planes. The cloud platform is now vendor-controlled and vendor-updated. The Gateway servers are still yours to install, patch, upgrade, and monitor. You take on a SaaS dependency without shedding the on-prem footprint.

For some organizations, the trade-off is worth it. For others, it’s the worst of both architectures.

You’re rebuilding everything anyway, so this is the moment to look around

This is the structural fact that should change your conversation with the vendor.

Per FlowForma’s analysis of the Nintex end of life and Skybow’s published migration guidance, there is no lift-and-shift path from Nintex Workflow for Office 365 or Nintex on-premise to Nintex Automation Cloud. The Nintex Modernization Program offers the Workflow Upgrade Tool and partner services, but workflows still have to be rebuilt on the destination platform.

That single fact reframes everything.

You’re not choosing the easiest path. You’re choosing which platform to invest the next 6 to 18 months of rebuild work into, then commit to for the next 5 to 10 years. The cost of rebuilding on Platform A is roughly equal to the cost of rebuilding on Platform B. So the deciding factors stop being “what does the migration tool support” and start being:

• Where can my data legally live?
• What’s my real total cost of ownership over five years?
• What deployment options does this platform support today, and tomorrow?
• How predictable is the budget at scale?

These are the right questions. But they only get asked if you accept that you have a real choice in front of you.

How to actually evaluate your options

Before signing any quote, run these four steps.

Step 1: Inventory your workflows

Document every active workflow:

• Source SharePoint version and workflow engine
• Trigger type (manual, list event, schedule, external)
• Connected systems (SharePoint on-prem, SharePoint Online, SQL Server, REST APIs, third-party SaaS)
• Approval chain depth and parallelism
• Form complexity (conditional logic, repeating sections, attachments)
• Compliance sensitivity (PII, PHI, financial controls, regulated content)

This tells you which workflows are simple ports versus which need to be re-architected. The simple ones are cheap to move anywhere. The complex ones are where platform fit really matters.

Step 2: Get data residency and compliance sign-off in writing

Answer these with security and compliance approval:

• Where can this process data legally reside? (Customer tenant, GCC, GCC High, on-premises, air-gapped)
• Which audit frameworks apply? (FedRAMP level, HIPAA, PCI scope, sector-specific rules)
• What data flow path is acceptable? (Direct cloud, hybrid via gateway, on-prem only)

Platforms that fail these requirements drop out before any feature comparison. This step alone often eliminates Nintex Automation Cloud for regulated workloads, which is exactly why Nintex itself recommends K2 for those scenarios.

Step 3: Size your real workload, not your demo workload

For consumption-based platforms, project a 24-month workflow execution volume. Include:

• Recurring scheduled workflows
• Event-triggered workflows (the high-volume sources like inbox monitors and list events compound fast)
• Form submissions
• Document generation runs

Then compare projected 24-month consumption pricing against flat-rate alternatives. Build a TCO model that includes server lifecycle costs for hybrid or on-prem options, and be honest about the staff time required to manage Nintex Gateway in a hybrid setup.

Step 4: Estimate rebuild effort and platform fit

Estimate rebuild hours per workflow category. Multiply by your loaded rate. Add migration partner costs, training, parallel-run windows, testing, and change management.

Then ask the harder question: Does the destination platform actually solve the problems your Nintex on-premise environment had, or does it just relocate them to different infrastructure?

If the destination is a cloud platform but your most painful workflows touch on-premise systems, you’ve moved the problem. If the destination is K2 but you don’t need the K2 complexity, you’ve overshot. If the destination is a flat-rate platform that supports all five deployment models you might need, you’ve actually solved something.

What a real on-premise alternative looks like

For organizations whose evaluation lands on “we need on-premise or hybrid flexibility, predictable cost, and a SharePoint-native build experience,” NITRO Studio by Crow Canyon Software is one platform that fits that profile.

• Five deployment options. Microsoft 365 / SharePoint Online, SharePoint On-Premises (2016, 2019, Subscription Edition), GCC, GCC High, and Air-Gapped (NITRO Secure). 
• On-prem data control. “All data kept safely within your SharePoint farm” for the on-premises version.
• Licensing model. Flat-rate annual subscription. NITRO Studio is sold per user for the tenant. NITRO applications are sold at a flat rate per site. No overage fees, no usage-based costs.
• Reference price. $5,988 per 100 users per year for NITRO Studio.
• Security posture. CMMC Level 1, ISO, HIPAA, GDPR, and SOC 2 certifications.
• Microsoft partner status. Microsoft Preferred Partner.
• Customer reference, on the public NITRO Studio page. “NITRO Studio conquered many of SharePoint’s out-of-the-box limitations and made it easier to do many tasks that previously were labor-intensive and required coding, and was much more affordable than other solutions we were looking at, such as Nintex.” Rodrigo Vargas, Sr. Manager Supply Chain Quality, Ventura Foods.

For an on-premise organization currently running Nintex Workflow for SharePoint and weighing a Nintex Automation Cloud quote, NITRO Studio offers the deployment flexibility your existing environment had (including air-gapped), with a predictable flat-rate cost structure and a build experience designed for SharePoint.

The bottom line

If you’re rebuilding workflows regardless, this isn’t a vendor renewal. It’s a platform decision that will shape the next decade of how your organization automates work.

Nintex Automation Cloud is one valid destination. Nintex Automation K2 is another, and it’s the path Nintex itself recommends for regulated workloads. Third-party Nintex Cloud on-premises alternatives are a third, and they’re worth a real seat at the table.

The cost of getting this decision wrong now is a re-platforming project later. The cost of getting it right is the next decade of stable, supported automation in the environment you actually need.

Run the inventory. Get the compliance sign-off. Size the real workload. Compare destinations side by side.

If your evaluation includes a Nintex Cloud on-premises alternative that runs across all five deployment models, including air-gapped on-prem, see what NITRO Studio looks like before you commit.

Frequently Asked Questions