Dynamics GP, NAV & BC to NetSuite migration
For GP or NAV users who need to move, and Business Central users who need more from their system. We compare your options first, then plan the migration if NetSuite is the right fit.
When Microsoft Dynamics starts costing you
Changes to the Dynamics roadmap may mean a major move for your business. If you need to re-implement anyway, it’s worth comparing your options before deciding which system comes next.
A migration you can audit
Nothing reaches production until it has balanced in a sandbox.
- A side-by-side comparisonNetSuite versus Business Central for your case, in writing. We don’t sell licences for either.
- GP & NAV extractionDecades of Dynamics data extracted, profiled and mapped.
- Customisation auditDexterity, C/AL and extensions become requirements: standard, rebuilt or retired.
- Reconciled balancesOpening positions tied back to Dynamics before cutover.
- One system, one vendor conversationERP, CRM-lite and reporting in one place instead of a licensing diagram.
- Planned exitSupport contracts and archive access sequenced properly.
Moving from Dynamics GP, NAV or BC to NetSuite?
Talk through your current system, data and timeline with a solution architect. It’s free, it takes 30 minutes and there’s no sales pitch.
What switching buys you
Nothing vanishes
Open items and the history you choose come across and reconcile.
Days, planned
One freeze over a month-end – your team keys nothing twice.
Room the old system never had
Entities, currencies, reporting – the ceiling stops existing.
Sign-off, in writing
Every control account tied to source before go-live.
Five checkpoints
No checkpoint passes without your sign-off.
Assess – we profile the current system and agree what moves, what’s archived and when.
Map – every field and value gets a documented home in NetSuite before anything is loaded.
Rehearse – the full migration runs into a sandbox first – never straight to production.
Reconcile – balances tie back to the old system, account by account, and finance signs off.
Cut over – one freeze, one final load, go-live with a rollback ready.
What to know before you start
- !Business Central is the default path – question the default. Microsoft’s migration tooling makes BC easy to choose and easy to under-scope; if BC fits you better, we’ll say so and step back.
- !Old Dynamics data needs archaeology. GP and NAV estates carry years of module add-ons and posting quirks; profiling comes before promises.
- !A forced move is still a real project. End-of-roadmap pressure tempts rushed decisions. The timeline should come from scope, never from a support deadline alone.
- !Deadlines are real but survivable. Dynamics GP end of life dates follow Microsoft’s published lifecycle; the risk is an unplanned exit, not the date itself.
- !A Microsoft Dynamics migration can be phased by product. A Dynamics NAV migration often runs finance first while GP or BC entities follow later, so group reporting continues throughout. We sequence the entities and modules around your year end, rather than forcing the business to fit the project plan.
Dynamics GP, NAV & BC Migration FAQs
Should we move to Business Central or NetSuite?
How long does Dynamics to NetSuite take?
Can you extract from an old GP install nobody maintains?
Last reviewed: 12 October 2026 · Written by the Suite Generation team
Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.
