Dynamics GP migration — Business Central, NetSuite or Xero, done right
Microsoft has confirmed Dynamics GP end-of-life. Migrate to the right target — Dynamics 365 Business Central, Finance & Operations, NetSuite, Sage Intacct or Xero/MYOB — with every GL entry, ISV add-on and Dexterity / VBA / Modifier customisation handled properly. Fixed-price.
- Customisations audited & re-implemented — not silently dropped
- Reconciled to your last GP EOFY — not "close enough"
- GP kept read-only one year as audit safety net
- Lowest prices Fixed cost · no monthly SaaS bills · founder-led overhead
- High quality Sandbox-first · weekly demos · reconciled pre-launch
- Fast delivery Quote in 48 hours · live in weeks, not months
- Latest tech Latest APIs · v2 REST native · you own the code
- Power BI
- Xero
- HubSpot
- Salesforce
- Stripe
- Square
- Shopify
- WooCommerce
- Deputy
- ServiceM8
- Simpro
Real benefits, by solving real GP migration problems.
- EOL ConfirmedMicrosoft announced GP end-of-life · mainstream support closing Sept 2028
- Customisations KeptDexterity · Modifier · VBA · SmartList work at risk in a rushed move
- Every Year ReconciledMulti-year GL · multi-entity intercompany history mishandled by lift-and-shift
- Right-Sized TargetSold an F&O upgrade when Business Central is the actual fit
- No Partner Per-HourMicrosoft Partner per-hour billing climbing as the project drags on
Six Dynamics GP migration capabilities
From the first GP company-database extract, through SmartList recreation in BC role-centres, to the cutover landed on a clean end-of-quarter boundary with ISV add-ons replaced consciously — built so your finance team trusts the new system from day one.
-
GP → Business Central
The natural successor — Dynamics 365 Business Central is Microsoft's recommended path for most GP customers. Chart of accounts mapped to BC dimensions, customer/vendor migrated, AR/AP open items + payment history preserved, fixed assets carried. BC posting groups configured to match GP behaviour.
- GP COA → BC dimensions
- Customer · vendor · AR / AP history
- BC posting groups configured
-
GP → Dynamics 365 F&O
For larger GP installations that have outgrown SMB ERP. Dynamics 365 Finance & Operations carries heavier modules — advanced manufacturing, multi-subsidiary at scale, sophisticated inventory and field-ops. We re-design (not lift) — F&O is structurally different from GP.
- Multi-subsidiary at scale
- Advanced manufacturing · WMS
- Re-design · not lift-and-shift
-
GP → NetSuite
The vendor-consolidation path — GP to NetSuite OneWorld for multi-subsidiary AU/NZ groups, or single-entity NetSuite for those wanting to leave the Microsoft ecosystem. Often chosen when the parent group is already on NetSuite.
- NetSuite OneWorld multi-sub
- Group consolidation play
- Leaves Microsoft ecosystem
-
GP → Xero / MYOB / Sage Intacct
Right-size path — for smaller GP customers where GP was over-scoped. GP core finance to Xero or MYOB AccountRight; or Sage Intacct for mid-market multi-entity that still wants cloud-native finance without the complexity of D365 BC.
- Downsize to Xero / MYOB
- Sage Intacct for mid-market
- Connected inventory if needed
-
Data Migration & Reconciliation
Every GP module extracted with row-by-row reconciliation. GL transactions, AR/AP detail, customers, vendors, items, inventory, fixed assets, multi-entity intercompany, payroll history. Numbers reconciled against your last GP EOFY before sign-off.
- GL · AR · AP · inventory · FA
- Multi-entity intercompany
- Reconciled to last GP EOFY
-
Dexterity · VBA · ISV Migration
GP customisations audited — Dexterity code, Modifier/VBA changes, SmartList Builder views, Integration Manager maps, eOne SmartConnect/Extender configurations, Mekorma AP, Continia Document Capture. Re-implemented in the target system natively or as proper extensions.
- Dexterity / Modifier / VBA audit
- SmartList · Integration Manager
- Mekorma · eOne · Continia ISVs
A Dynamics GP migration project, end to end
Three stages. Parallel-run with daily reconciliation against live GP. Cutover on a financial-year or quarter boundary. GP stays read-only as a safety net. Delivered personally by the founder.
-
Week 0
Dynamics GP Audit
15-minute scoping call. We map the GP version, modules in use, customisation depth (Dexterity, VBA, Modifier, SmartList), ISV add-ons (Mekorma, eOne, Continia), entities + currencies + data size, target system and budget. Fixed-price quote inside 48 hours.
-
Weeks 1–N
Build & Parallel-Run
Two-week sprints with weekly demos. Migration scripts extract from GP (data, configuration, SmartList metadata); target system configured in parallel. Reconciliation reports each sprint against live GP. Customisations re-implemented natively in the target system.
-
Cutover
End-of-Quarter Cutover
Cutover landed on a clean financial boundary (end-of-month / end-of-quarter / EOFY). GP stays read-only for one financial year as audit safety. STP / BAS / multi-entity reporting continuity tested. 30 days post-cutover support included.
Before you book the scoping call
How much does a Dynamics GP migration cost?
Fixed-price after a 15-minute scoping call and a short discovery session. A focused GP → Business Central migration (single entity, vanilla modules, light customisations) takes 10–16 weeks. A multi-entity GP → BC or NetSuite migration with Dexterity/VBA customisations and ISV add-ons takes 4–8 months. Enterprise GP with heavy customisations and 5+ legal entities sits higher. You know the price before any data is touched.
How long does a Dynamics GP migration take?
Small single-entity GP → BC with vanilla modules: 10–16 weeks. Standard GP → BC with multi-entity, Dexterity customisations and 2–3 ISV add-ons: 16–28 weeks. Enterprise GP with heavy customisations and many integrations: 6–12 months. Cutover always lands on a financial-year or quarter boundary so reporting stays clean.
Which target system — Business Central, F&O, NetSuite, or Xero?
For most GP customers, Dynamics 365 Business Central is the answer — same Microsoft ecosystem, BC is the structural successor to GP, lower TCO than F&O. Dynamics 365 F&O is right only when you've genuinely outgrown SMB ERP and need advanced manufacturing or multi-subsidiary at scale. NetSuite is the consolidation play when leaving Microsoft or aligning with a parent group. Xero/MYOB are right when GP was over-scoped for actual usage. The scoping call covers all four honestly.
What about our Dexterity, Modifier, VBA and SmartList customisations?
Audited carefully. We document every customisation (often surprising the current team) and split into three buckets — (1) re-implement as a proper BC extension or NetSuite SuiteScript, (2) replace with native functionality the new system covers, (3) drop because the underlying business need has changed. SmartList views map cleanly to BC role-centre lists or Power BI reports. Integration Manager flows re-built as proper integration code.
What about ISV add-ons like Mekorma, eOne SmartConnect, Continia, Integrity Data?
All in scope. Mekorma AP automation → Continia Document Capture (on BC) or Tipalti / equivalent. eOne SmartConnect integrations → re-built as proper code or replaced with Power Automate where appropriate. Continia Document Capture transfers cleanly to BC. Integrity Data payroll → re-implemented through Xero Payroll / Employment Hero / KeyPay depending on size. Each ISV mapped or replaced consciously.
How much historical data can we migrate?
In principle, all of it — GL transactions, AR/AP open + history, customers, vendors, items, inventory, fixed assets, payroll history. In practice we ask which years actually need to be queryable in the new system (typically last 2–7 years live, older years archived as exports). Australian Tax Office requires 5 years of records — we always migrate enough to satisfy that and the auditor's next visit.
GP's industry strength is distribution, manufacturing, construction — do you handle those?
Yes. GP Distribution + Manufacturing modules map to BC Manufacturing (where appropriate) or D365 F&O Advanced Manufacturing for heavier needs. Job Cost (often heavily customised in GP) re-implemented in BC Jobs module + extensions. Field-Service maps to D365 Field Service or BC + Simpro/ServiceM8 integration. The mapping work is real — that's where we earn it.
Do we own the migration code? What happens to GP after cutover?
Yes — migration scripts, reconciliation reports, target-system configurations, custom extensions, deployment scripts, all yours in your GitHub or Azure DevOps from day one. GP stays installed read-only for one financial year as audit safety — the auditor can still pull source data when needed. After that, exported archives are kept indefinitely. Target system hosting is yours (BC is your Microsoft tenant; NetSuite is your NetSuite account).
Best value · quote in 48 hours · code is yours · zero obligation
