YOUR SITUATION · LEGACY ESCAPE

Your system is going out of support. Here is exactly which clock you are on.

Microsoft publishes a lifecycle date for every version of GP, NAV, AX, SL, and CRM on-premises. Most partner sites talk about this in vague terms. We would rather show you the actual date.

Three cohorts, three different urgencies

Which one of these are you actually in?

Not every "out of support" system is in the same amount of trouble. Knowing which cohort you're in is the first real decision, before any migration conversation starts.

Already dead
AX (all versions), CRM 2015/2016, NAV 2009–2016, SL 2015, GP 2013–2016 R2, BC on-prem v13/v14, support has already ended
Deadline inside 30 months
NAV 2017 (Jan 2027), GP 2018 (Jan 2028), NAV 2018 (Jan 2028), SL 2018 (Jul 2028), the window to act is now
  • 1
    Commercial cliffs are already in effect for GPNew customers could not license GP after 1 Apr 2026. Tax and regulatory updates stop 31 Dec 2029. Perpetual user additions across GP, NAV, and SL end 30 Apr 2031.
  • 2
    "Already dead" does not mean the system stopped workingIt means Microsoft's obligation to fix anything new has ended. The system runs; the safety net does not.
  • 3
    A 9 to 15 month migration plus 3 to 6 months of partner selection is typicalWorking backwards from any 2027–2028 deadline, the realistic window to start is already narrow.
Pick your system

Each legacy product has its own path, its own traps, and its own timeline.

Dynamics GP

Mainstream support ended 14 Jul 2026. Tax and regulatory updates run through 2029.

→

Dynamics NAV

NAV 2017 support ends 11 Jan 2027. NAV cannot move to the cloud in a single hop.

→

Dynamics AX

Every AX version is already unsupported. The path forward is Finance & Operations.

→

Not sure which version, or on SL / CRM on-prem?

Check your exact support date across every legacy Dynamics product.

→
Two traps worth knowing before you start

The surprises that usually show up mid-project, not before it.

The NAV two-hop

  • 1
    NAV cannot go straight to the cloudMicrosoft's supported path requires upgrading to Business Central on-premises first, then moving online.

The GP 2018 hotfix trap

  • 2
    One tax update can silently change your lifecycleApplying any tax update to GP 2018 moves the install to 18.5+ and onto Modern Lifecycle, which requires taking one of three annual updates going forward.
Read the full NAV two-hop breakdown →
Common questions

What we get asked before anyone has picked a product page yet.

Q.Our system still works fine. Why would we move now?

Nothing forces you to move the day support ends. The cost of waiting is real but gradual: no security patches, shrinking specialist talent, and add-on vendors quietly dropping support first.

Q.How do we know which cohort we're actually in?

Check your exact version against the support countdown, or tell us your product and version on a call and we'll tell you directly.

Q.Are Dynamics SL and CRM on-premises covered here too?

Both are real legacy-escape situations. Dedicated pages for each are coming; until then, talk to us directly and we'll walk you through the same three-cohort framework for your product.

Q.What if our implementation already started and something's gone wrong?

That's a Rescue conversation, not a Legacy Escape one. See the Rescue hub.

Not sure which situation is yours

Get a straight read on your migration, not a pitch deck.

Tell us your product and version. We will tell you honestly which cohort you are in and what a realistic timeline looks like.

Book a 30-minute call

With someone who has run this kind of migration before.

→

Run the situation diagnostic

Four minutes, no email required to see the result.

→