Premium office space
A sourced reference · Every claim linked to its origin

Your legacy Nintex migration,
mapped.

If your team has already decided to move off legacy Nintex, this guide is for you. It brings the deadlines, the realistic platform options, and what a migration actually involves into one place, each point sourced to Microsoft, Nintex, and practitioners who have already made the move.

Am I affected? See the deadlines
Every factual claim on this page links to its original source. The relevant dates are set by Microsoft and Nintex and are subject to change; please confirm them against the respective vendor documentation before acting.
Deadline status · live
SCHEDULE COMPLETED

All milestones in effect

The retirement schedule has now fully reached its active phase.

MICROSOFT-DRIVEN SCHEDULE
AS OF JUL 28, 2026
At a glance

  • Microsoft permanently removed the engine The SharePoint 2013 workflow engine left every existing Microsoft 365 tenant on April 2, 2026. That engine is what legacy Nintex ran on. Microsoft Source

  • Support ended Dec 2025 Nintex Workflow for Office 365 reached end of support on December 31, 2025. No further patches or fixes. Nintex Source

  • No one-click conversion Content tools move your data. You rebuild the workflow logic and forms by hand. There is no simple migration path. Nintex FAQ

  • An open destination With a rebuild required either way, the destination is an open decision. Power Automate, Nintex's modern cloud, WEBCON and others each fit different needs.

  • Not everyone moves today Modern Nintex Automation Cloud and most on-premises setups fall outside this particular deadline for now.

  • Strategic Window This is an opportunity to clean house. Retiring "ROT" (Redundant, Obsolete, Trivial) workflows can save months of effort.

Who this is for

A guide for teams already on the move

This resource assumes the decision to migrate off legacy Nintex has already been made. It focuses on planning and running that migration well, not on making the case for it.

check_circle

This guide is for you if

  • checkYou have already decided to move off legacy Nintex, and now need to plan and run the migration.
  • checkYou are the IT or platform lead, a SharePoint or Nintex administrator, an enterprise architect, or the person accountable for the project.
  • checkYou want the deadlines, the platform options, and the realities of migration in one sourced place.
info

It's less relevant if

  • removeYou are still deciding whether to move at all. This guide does not argue that case.
  • removeYou run modern Nintex Automation Cloud, which the 2026 deadline does not affect.
  • removeYou are looking for a product pitch rather than a neutral, sourced reference.
Free download · No spam

The Complete Nintex
Exit Playbook

Discovery and ROT triage, complexity scoring, platform mapping against runtime and compliance constraints, and phased cutover runbooks. Written for teams running the whole migration, not just reading about it.

description30+ pages · PDF · Free download

Get the playbook

Enter your work email and it opens immediately, no waiting on a follow-up.

By submitting, you agree to be contacted about this. See our Legal & Disclaimers.

No spam. Unsubscribe anytime.

01 · Assessment

Which Nintex products are affected by the 2026 changes?

"Nintex" is not a single product. The 2026 retirement affects some versions directly and leaves others untouched. Identify your setup below to understand where your organisation stands.

Tick every Nintex product you actually run, then generate your report. In short: Nintex Workflow for Office 365 is directly in the deadline's path, modern Nintex Automation Cloud isn't targeted by this retirement, and on-premises sits in between.
Tick the products you run above to begin.
02 · The Countdown

Every deadline that matters

These are the dates that decide when things stop working. Microsoft and Nintex control every one of them, and each row links to the primary source so you can confirm it yourself.

Modern Migration Calendar
Migration Strategy

The 12-Month Reality

A typical migration project spans 12 months, phasing from initial audit to final user acceptance testing. The deadlines shown below represent the absolute hard stops determined by Microsoft and Nintex.

Months 1-2: Comprehensive Audit & ROT Analysis

Months 3-8: Technical Reconstruction & Re-architecting

Months 9-12: Testing, Training & Final Cutover

APR 2, 2024 In effect

SharePoint 2013 engine switched off for new tenants Microsoft

New Microsoft 365 tenants can no longer build workflows on the legacy 2013 engine, the same engine Nintex Workflow for Office 365 depends on.

NOV 1, 2024 In effect

SharePoint Add-Ins blocked for new tenants Microsoft

As Microsoft retires the SharePoint Add-In model, new tenants lose the add-in support that older Nintex Forms structures rely on.

DEC 31, 2025 In effect

Nintex Workflow for Office 365 reached end of support Nintex

No further patches, security updates, or troubleshooting from Nintex. Running past this date means operating unsupported software.

APR 2, 2026 In effect

The hard stop: engine removed from existing tenants Microsoft

Complete removal of the SharePoint 2013 workflow engine from all existing M365 tenants. Dependent workflows fail permanently, and old definitions become viewable only as raw XML.

// On-premises Nintex does not stop the moment support ends. But once you are on an unsupported Microsoft platform, there are no further security patches or fixes. Always confirm dates against Microsoft's own lifecycle pages before acting.
03 · The background

What's driving the 2026 move

You've made the decision to migrate. This section covers the context behind that decision and the factors worth carrying into your planning, each attributed to its source.

R1 · COMPLIANCE

The deadline leaves no choice

For teams on Nintex Workflow for Office 365, the Microsoft retirement schedule is an operational hard stop. Procurement, onboarding, IT requests, and approval flows built on the legacy engine simply stop working once it's removed on April 2, 2026.

WHO'S SAYING IT // Microsoft's own SharePoint 2013 workflow retirement notice
R2 · COMMERCIAL

Pricing models to plan for

Even Nintex's server-based licensing has long capped usage. Moving to modern cloud platforms changes how that gets metered: consumption- or user-based models with overage fees. Buyers report sharp increases against historical baselines.

WHO'S SAYING IT // TrustRadius & Vendr pricing pages; migration vendors
R3 · ARCHITECTURAL

Technical factors to weigh

Administrators cite friction in the cloud platform: workflows keyed to display names, hybrid gateway HA challenges, and hard file/size limits. These are practitioner reports, not universal facts, but they drive migration choices.

WHO'S SAYING IT // Practitioner write-ups & Nintex community notes
R4 · LOGICAL

A rebuild is required either way

There's no one-click conversion between the legacy engine and any modern platform, Nintex's own included. Once a full rebuild is unavoidable, the extra cost of switching vendors entirely drops sharply, encouraging market evaluation.

WHO'S SAYING IT // Nintex migration FAQs & migration tooling docs
Strategic balance
FOR BALANCE

Reasons some organizations stay

Not everyone leaves. Nintex offers supported paths to its modern products with upgrade tooling and migration assistance. If your team already knows the Nintex stack and can absorb the licensing model, staying in-platform can be the lowest-effort route. Nintex Source

The honest version: the right move depends on your complexity, budget, and skills. It does not depend on any single vendor's framing.

04 · The Landscape

Where teams are heading next

These are the main directions teams evaluate, described by fit and trade-off rather than ranked. The right destination depends entirely on your requirements.

STAY IN MICROSOFT grid_view

Microsoft Power Automate

A common path for organizations already invested in Microsoft 365. It uses a different logical model, so you rebuild workflows rather than translate them.

check_circle Deep M365 integration; no new vendor to onboard
check_circle Reminders, escalation and long waits are achievable with scheduled flows and stored state; the cost is design effort, not a missing feature
warning Hard 30-day cloud-flow run limit Docs
STAY WITH NINTEX automation

Nintex Automation Cloud

Nintex's own modern products, with vendor-provided upgrade tooling. Familiar to existing Nintex teams, though still not a lift-and-shift.

check_circle Vendor migration tooling; least conceptual re-learning
warning Pricing models are often the core reason teams migrate
SPECIALIST BPM account_tree

Dedicated process platforms

Platforms such as WEBCON use state-machine engines built for long-running, multi-stage approvals, sits closer in spirit to legacy Nintex.

check_circle State-machine models suit non-linear processes Source
warning A new vendor relationship and learning curve
RESIDENT SOLUTION home_storage

SharePoint-native replacements

Tools such as Crow Canyon NITRO Studio keep data inside your existing SharePoint/M365 boundary, critical for sovereignty.

check_circle Data stays within your tenant; flat-rate pricing Source
warning Ideal use case is narrower; evaluate carefully
“Power Automate's biggest structural weakness at enterprise scale is fragmentation.”
AH
Akbar Hussain
On rebuilding enterprise Nintex workflows Medium Article
05 · Decision Matrix

How to choose the right platform

Don't start from a product. Start from your requirements, and score every candidate against the same questions.

add_circle

Neutral selection criteria

If a platform can't answer these to your satisfaction, it's not your platform, no matter who recommends it.

  • 1
    How long do your longest-running workflows and approvals need to stay open?
  • 2
    Is your pricing predictable at your real transaction volume, including overages?
  • 3
    Where must your data physically live for compliance?
  • 4
    Who maintains these workflows, citizen developers or professional developers?
  • 5
    How many workflows are genuinely active versus redundant or obsolete?
  • 6
    What integrations and forms must survive, and how are they rebuilt?
  • 7
    What's the total effort to rebuild, test, and retrain, not just to license?
  • 8
    What's your exit cost if this platform's terms change later?
06 · Execution Phasing

What a migration actually involves

A structured, phased approach that puts continuity ahead of speed. The early phases exist to de-risk the later, expensive ones.

report_problem
The single most common surprise: it's never a lift-and-shift. Content tools move your lists and data; the workflow logic and forms are rebuilt by hand, every time.
01

Discovery & inventory

Scan the tenant to catalog every active and legacy workflow before assuming anything about scope.

Typical artifacts Assessment tooling, workflow reports, custom PowerShell
02

Triage & ROT analysis

Identify redundant, obsolete, and trivial workflows that haven't run recently, then retire them instead of migrating them.

Typical artifacts Usage reports, last-run date logs
03

Logic auditing

Analyze workflow definitions to score complexity and flag custom scripts or actions that won't have a direct equivalent.

Typical artifacts XML exports, complexity scoring, legacy docs
04

Architectural mapping

Assign each surviving workflow to a target platform based on runtime limits and compliance.

Typical artifacts Mapping sheets, compliance checklists
05

Core data migration

Move lists, libraries, and permissions with content tools. Note: these move data, not logic.

Typical artifacts Content migration utilities (e.g. ShareGate)
06

Workflow reconstruction

Rebuild logic on the new engine, optimizing for the target's strengths rather than copying the old shape verbatim.

Typical artifacts Target designers, state machines, Dataverse
07

Testing & Cutover

Regression test, run user acceptance testing, and train administrators before cutover.

Typical artifacts Test suites, CoE kits, admin training
REALITY CHECK

"Lift-and-shift" usually isn't real

Because the legacy engine and every modern target use fundamentally different architectures, there's no one-click conversion. Content tools move data, but not logic. Nintex Source

Practitioners report that a straight lift-and-shift looks cheaper on paper but carries technical debt, while re-architecting is more work up front but tends to hold up better long-term. Reddit Discussion

07 · Take it with you

Playbooks, guides and templates

Everything you need to plan and run the migration, in one place.

Ebookmenu_book

The Enterprise Nintex Exit Playbook

A field manual for migrating large workflow estates: discovery, ROT triage, complexity scoring, and phased cutover runbooks.

View the PDFarrow_forward
Guideformat_list_numbered

The Step-by-Step Migration Guide

From still-on-legacy-Nintex to a clean cutover: the sequence in order, with the trap to avoid at each step.

View the PDFarrow_forward
Worksheetcalculate

Migration Cost & Effort Estimator

Build a defensible number: workflow volume, complexity mix, rebuild hours, and three-year licensing.

View the PDFarrow_forward
Templategrid_view

Workflow Inventory & Readiness Template

Inventory, score, and triage every workflow before you migrate, with a scoring rubric and sample rows.

View the PDFarrow_forward
Reportfact_check

The Nintex Exposure Report

Which 2026 deadlines apply to your setup, what breaks if you wait, and recommended next steps.

View the PDFarrow_forward
08 · Common Inquiries

The questions everyone keeps asking

Drawn from community threads, practitioner write-ups, and vendor documentation.

Can I just lift-and-shift my Nintex workflows? expand_more
No, not to any modern platform. The legacy engine and modern engines use different logical models, so every workflow and form gets re-architected and rebuilt. Migration "accelerators" convert basic logic, but complex steps still need manual work.
Will a tool like ShareGate migrate my workflows? expand_more
Content migration tools reliably move SharePoint lists and libraries. They do not convert workflow logic or form code. Migrations split into tracks: content tools for the data, and designers for rebuilding logic by hand.
What actually breaks first if I do nothing? expand_more
The sequence follows the Microsoft schedule: new-tenant restrictions first, then Nintex O365 end of support on Dec 31, 2025, then the hard removal of the 2013 engine on April 2, 2026.
09 · Documentation

Every source we pulled from

Grouped by who published it so you can weigh its perspective.

Official & first-party

Primary

Community & experience

Real World