GP and NAV to Business Central: A Migration Marketing Plan for Partners

Vinod Sanadhya
Vinod Sanadhya Founder, SignalScaler
· Published November 14, 2026 · Updated November 14, 2026 · 10 min read

Short answer: Dynamics GP migration marketing works when you split GP and NAV customers by how close their deadline is, work backwards from that date to when they must pick a partner, and lead with an offer that answers their biggest fear. For GP that fear is losing history. For NAV it is custom code nobody documented.

Most partners run one "time to move to the cloud" campaign to every GP and NAV customer they can find. It gets a few replies from people who were moving anyway and silence from the rest. This plan splits the market by urgency, builds the list from signals you can actually find, and times each wave to the buyer's own calendar. It is the order we use when we run migration campaigns for ERP partners.

What is a migration marketing campaign?

A migration marketing campaign targets companies that must replace or upgrade a system by a known date, such as an end of support. Unlike general demand generation, the audience is fixed and countable, the deadline is public, and the winner is usually the partner who helped the buyer plan before they started comparing quotes.

How urgent is each GP and NAV group right now?

Very different. As of November 2026, NAV 2017 customers have weeks left on extended support, NAV 2018 customers have about 14 months, and GP customers have three years until updates and support stop. Each group needs its own message and pace. Treating them as one list wastes the urgent ones and annoys the rest.

GroupKey dateWhere they are nowCampaign tone
NAV 2016 and olderAlready out of support (NAV 2016 extended support ended April 2026)Running unsupported; often "it still works"Risk review: what breaks first, and a calm, phased way out
NAV 2017Extended support ends 11 January 2027Too late to finish a move before the date"Stabilise now, move in 2027": support cover plus a dated plan
NAV 2018Extended support ends 11 January 2028Prime window: choosing a partner over the next few monthsPlanning: modification audit, timeline, budget for 2027
Dynamics GPUpdates, tax updates and support end 31 December 2029; security updates end 30 April 2031Aware, mostly not yet acting; many will drift into 2028Education first: options, costs and what moves; then a decision date

GP: Microsoft Learn, "Discontinuing support for Dynamics GP" (checked 14 November 2026). NAV: Microsoft lifecycle dates as reported by ERP Software Blog (October 2026) and endoflife.ai; confirm each version on Microsoft's lifecycle pages before a campaign goes out.

One correction to make in every GP campaign: GP is not "end of life" in 2029. The software keeps running, and security updates continue to April 2031. Buyers who know this stop trusting partners who say otherwise. Say what actually ends, and when.

When does each buyer need to choose a partner?

Work backwards from the deadline. Take the support date, subtract the project time, subtract two or three months for choosing a partner, and you have the date when the buyer must start talking to partners. Your campaign should reach them a quarter before that, while they are still forming a view.

GroupTarget go-liveProject time (typical)Partner chosen byStart your campaign
NAV 2018By late 20274–6 monthsSpring 2027Now (Q4 2026 to Q1 2027)
GP, planning aheadStart of fiscal year 20283–6 monthsSpring 2027Q1 2027 education, Q2 2027 offers
GP, last-minuteBefore 31 December 20293–6 monthsLate 2028 to early 2029Keep in nurture; push in 2028

Project times are planning ranges. One Microsoft partner's guide puts a typical GP to Business Central move at five to six months, and a simple small business with no integrations at about three (Stoneridge Software, August 2026). Your own go-live history is the better number to use.

The field that makes this work is the buyer's fiscal year-end month. Finance teams rarely switch ERP during year-end close, and many prefer to go live at the start of a year or quarter. If your list records the year-end for each account, you can time the first touch eight to ten months before it. Almost nobody collects this field. It is often in annual filings, job adverts for year-end roles, or simply asked on the first call.

How do you build a list of GP and NAV customers?

Start with the lists you already own, then add public signals. GP and NAV customers are not hidden: they hire people with those skills, join user groups and leave traces in old quotes. Technology databases are the weakest source, because an ERP sits behind a login where website scanners cannot see it.

For each account, record five fields before any outreach: product and version, number of companies or entities, known customisations and add-ons, main integrations, and fiscal year-end. Those five fields decide which offer and which message the account gets. If you need the list built and verified, our B2B data and enrichment service does this work.

Planning a GP or NAV campaign?

Tell us your region, how many GP or NAV customers you already support and your usual project size. We will sketch the list, the offer and the first three touches. Talk about your migration campaign →

Which offers get GP and NAV customers to reply?

Narrow offers that remove a specific fear beat broad ones like "free consultation". A GP customer worried about history replies to a data plan. A NAV customer with years of custom code replies to a modification audit. Keep the first offer small, fixed in scope and clearly useful even if the buyer never hires you.

OfferBest forWhat the buyer gets
History and data planGP customers with many years of dataWhat moves automatically, what stays in a read-only archive, and how they will still report on old years
Modification auditNAV customers with custom codeA list of each modification, marked "now standard", "use an app" or "rebuild", with rough effort
Cost of stayingOwners who think doing nothing is freeCurrent support, server, hosting and workaround costs set against a phased move
Peer sessionCautious finance teamsA short online session where one of your migrated customers explains what went well and what did not
Fixed-scope assessmentBuyers ready to planTwo to three weeks, a written plan, a timeline and a budget range

Publish the fixed-scope assessment as a consulting offer on Microsoft Marketplace too, so buyers can check its scope before they reply. One catch: listing-only offers cannot use the migration category, so list it as an assessment. Our guide to Microsoft Marketplace consulting offers explains the rules.

The history plan sells well because Microsoft's own tooling gives you a strong answer. The cloud migration from GP to Business Central online moves the chart of accounts, customers, vendors, items, open receivables and payables, open purchase orders and general ledger summary history, and an optional "historical snapshot" copies detailed GP history for reporting (Microsoft Learn, updated January 2026). Say this plainly in the first message, then let your consultant handle the exceptions on the call.

What should the outreach sequence say?

Three or four short touches over three to four weeks, each adding something useful, sent from a consultant's name rather than a marketing address. Here is the shape we use for a NAV 2018 list. The wording is an example to adapt, not a template to paste.

TouchChannelWhat it says
1 · Day 1Email"NAV 2018 extended support ends on 11 January 2028. Most of the work in a move is the modifications. We list each one and mark what Business Central now does as standard. Worth a 20-minute look at yours?"
2 · Day 4LinkedInConnection request from the consultant with a short, plain note; no pitch.
3 · Day 9EmailA one-page example of a modification audit from a past project, names removed.
4 · Day 18Email"If 2027 is too soon, when is your year-end? We will get back in touch three months before you plan."

The last touch matters more than it looks. A buyer who says "not this year" has given you a date. Log it in your CRM with a reminder, and most "no" replies turn into a planned conversation later. Our outbound lead generation service runs these sequences and the follow-up for partners. Selling into Canada or the UK? Check consent rules for your region before the first email.

How should GP campaigns handle competing ERPs?

Expect them. GP customers are also being courted by partners of other mid-market ERPs. Do not attack the others. Publish an honest comparison page from the GP user's point of view: what stays familiar in Business Central, what changes, and when another product might fit better. Buyers trust a partner who admits where a rival is stronger, and that page also gives AI assistants a balanced source to quote.

How do you measure a migration campaign?

Count by group, not in total, and measure conversations before revenue. ERP projects take months to sign, so the early numbers tell you whether the list and message are right long before a contract does.

To see how many conversations you need for the revenue you want, run your numbers through our B2B pipeline calculator.

What mistakes should partners avoid?

Frequently asked questions

When should a partner start a Dynamics GP migration campaign?

Start education now and specific offers in early 2027. Support ends on 31 December 2029, and with three to six months of project time plus partner selection, many buyers aiming for a 2028 go-live will choose a partner during 2027. Reach them before they start comparing quotes.

Is Dynamics GP end of life in 2029?

Not exactly. Product enhancements, tax updates and technical support end on 31 December 2029, but security updates continue until 30 April 2031, and the software keeps working after that. Partners should say exactly what ends and when, rather than calling it end of life.

What happens to GP history when moving to Business Central?

Microsoft's cloud migration moves master data, open transactions and general ledger summary history, and can copy detailed history into a separate historical snapshot for reporting. Many partners also keep the old GP database available read-only. Each project should agree how many years to bring across.

How do you find companies still using Dynamics NAV?

Start with your own customer, lapsed and lost-deal lists. Then look for job adverts and staff profiles that mention NAV, Navision or C/AL, add-on vendors who serve NAV users, and user-group members. Website technology scanners rarely detect an ERP, so they are a weak source.

Should NAV 2017 customers still move to Business Central?

Yes, but most cannot finish before extended support ends on 11 January 2027. The sensible message is to stabilise first, with support cover and backups in place, then plan a proper move during 2027 rather than rushing a risky one.

What is the best first offer for a migration campaign?

One that is small, fixed in scope and useful on its own: a history and data plan for GP customers, a modification audit for NAV customers, or a short fixed-price assessment. Broad "free consultation" offers get far fewer replies.

Vinod Sanadhya
Vinod Sanadhya
Founder of SignalScaler. Led marketing for a UK ERP vendor and its partner channel, and now runs outbound and inbound programmes for ERP partners and IT companies.

Marketing an ERP practice? See our marketing for ERP partners page, the wider ERP partner lead generation playbook, how we turned a UK ERP vendor's story into one message in the 123insight case study, or talk to us about your migration campaign.

More from the blog
See all posts
Back to blog →
We use cookies to understand how visitors use this site. Analytics cookies stay off unless you say yes — see our Cookie Policy for details.

Cookie Preferences

Strictly Necessary
Required for the site to function. Always on, cannot be disabled.
Analytics
Helps us understand how visitors use the site (Google Analytics). Off by default.