Dynamics GP Data Migration
Migrate to Business Central, NetSuite, MYOB Acumatica, or a multi-app stack.
Microsoft has set December 31, 2029 as the end of support for Dynamics GP. That is a fixed date. We migrate your GP data and rebuild your integrations for the new platform. Full SQL extraction, transformation, and load.
Perth-based, working with Australian businesses nationwide. We handle migration and integration. Your chosen platform partner handles the ERP configuration.
Get a free consultation
Dynamics GP Migration & Replacement for Australian Businesses
Dynamics GP has been a reliable ERP for Australian mid-market businesses for decades. But Microsoft has drawn a line: December 31, 2029. That is the end of product updates, tax releases, and technical support. Security patches extend to April 2031, but from January 2030 you are on your own for compliance and functionality.
HELLO PEOPLE manages GP migrations to Dynamics 365 Business Central, NetSuite, and MYOB Acumatica. Full SQL extraction, data transformation, Dexterity customisation rebuilds, report migration, and integration reconnection — all managed as a single project with a fixed price after auditing your environment.
We are Perth-based and work with businesses across Australia. Every project starts with a review of your GP environment before we scope or quote anything.
Why businesses come to us about Dynamics GP
These are the situations we see most often from businesses still running GP.
A fixed end-of-support date with no migration plan
December 31, 2029 is published on Microsoft's own website. If you are on Dynamics GP, you have a deadline whether the business has started planning for it or not.
Dexterity customisations that make every upgrade painful
Each GP upgrade requires testing and often repairing your Dexterity customisations. It takes weeks per cycle and adds risk every time. The work will not stop until you move to a platform with a modern extension model.
Reporting that requires GP Report Writer and manual Excel
Management Reporter and GP Report Writer produce point-in-time reports that get emailed around in Excel. Finance cannot give the business real-time visibility from GP without significant workaround.
Get Started
Still on Dynamics GP with no migration plan?
Tell us what version you are on, what customisations exist, and when you need to be off GP. We will come back with a realistic migration plan and fixed-price quote.
Services for Dynamics GP users
Data migration, integrations, dashboards, and custom extensions. We do not handle the ERP configuration itself, that sits with your chosen platform partner.
Migrate your Dynamics GP data to Business Central, NetSuite, or MYOB Acumatica
Microsoft has formally announced end of support for Dynamics GP on December 31, 2029. That is a fixed date, not a vague future direction. Security patches continue until April 2031, but after December 2029 there are no product updates, tax table releases, or technical support.
We extract your complete GP data set: chart of accounts, customers, suppliers, inventory, jobs, payroll history, open AP/AR, and transaction history. We transform to the target platform schema and load cleanly into Dynamics 365 Business Central, NetSuite, or MYOB Acumatica. Every entity mapped and validated before production cutover.
GP uses SQL Server, which makes data extraction straightforward. The complexity is in the transformation work — GP data models are quite different from Business Central, and GP customisations built over many years do not carry across directly.
Custom integration services →Connect your existing apps to Dynamics GP while you plan the move
If your GP migration is 12 to 18 months away, your business systems still need to work reliably in the meantime. We build integrations that connect Dynamics GP to your CRM, e-commerce platform, job management tools, or field service systems.
GP has a well-structured SQL backend and supports integration service layers. Common integrations include syncing customer and order data between GP and Salesforce or HubSpot, pushing e-commerce orders into GP for invoicing, and connecting field service platforms for billing.
These integrations are scoped with the migration in mind. Where possible, we build middleware components that can be rearchitected for Business Central at migration time rather than rebuilt from scratch.
Custom integrations →Modern dashboards and reporting built from your GP data
GP Report Writer gets the job done for standard financial reports, but real-time management visibility requires something more. Getting live data out of GP typically means scheduled SQL queries, Excel-linked reports, or Management Reporter — all with a manual refresh step between the data and the decision.
We build external dashboards connected to GP via SQL: live P&L, divisional performance, cash flow forecasting, debtor aging, inventory velocity, and project profitability. Browser-accessible, with role-based permissions and no manual refresh cycle.
These dashboards are also migration-ready. We build the data layer so it can connect to Business Central or your new platform after cutover, preserving your reporting investment through the change.
Dashboard & reporting software →Custom tools and workflow extensions built around Dynamics GP
Many GP environments have accumulated Dexterity customisations, third-party add-ons, and SQL-based tools over years of operation. These work, but they create drag on upgrades and lock you into older GP versions.
We build external tools that sit alongside GP and address the functional gaps without adding more technical debt to the GP layer: customer portals, approval workflows, data entry interfaces for field staff, and reporting tools that connect back to GP for financial data.
Where your customisations are the primary blocker to migration, we audit what you have and plan the equivalent build on Business Central or your chosen replacement platform.
Custom software development →
Where do Dynamics GP businesses migrate to?
Multi-app stack for businesses who want modern and modular. Business Central for Microsoft's recommended path. NetSuite for complex multi-entity. MYOB Acumatica for Australian mid-market.
Replace GP with a multi-app stack: Xero or MYOB plus specialist apps
You do not have to replace GP with another big ERP. Some GP businesses, particularly those at the smaller end of the mid-market, retire GP entirely by moving to a connected stack of best-of-breed apps: Xero or MYOB for core accounting, Deputy or Employment Hero for HR and payroll, simPRO or ServiceM8 for field service, Unleashed or Cin7 for inventory.
This approach is cheaper and simpler than a Business Central or NetSuite migration, and it avoids the multi-year single-vendor commitment. Each app is purpose-built, Australian-compliant, and can be swapped out later without rebuilding the whole stack.
We migrate your GP data into each app, then build the integration layer between them. Orders into Xero, timesheets into payroll, inventory into accounting, jobs into field service. Worth evaluating if the complexity you ran on GP has reduced over the years, or if the business has simplified.
Migrate to Dynamics 365 Business Central, the Microsoft-recommended path
Microsoft explicitly recommends Business Central as the successor to Dynamics GP. It is cloud-native, runs on Azure, integrates across Microsoft 365, and receives continuous updates rather than annual upgrade projects. For most GP businesses, it is the natural landing point.
The migration from GP to Business Central is not a simple upgrade. GP and Business Central have different data models and different architectures. It is a migration project with real scope.
That said, Business Central handles everything GP did: multi-entity, job costing, manufacturing, distribution, project accounting. We handle the GP to BC data migration and integration rebuild. Your Dynamics partner handles the Business Central configuration and any extension work.
Migrate to NetSuite for growing, multi-entity, or international businesses
For GP businesses that are growing fast, have complex multi-entity structures, or operate across borders, NetSuite is often a better fit than Business Central. It is fully cloud-native, scales well, and has a mature API that makes post-migration integrations straightforward.
GP businesses migrating to NetSuite typically do so because their complexity has outgrown what GP or Business Central can handle cleanly. NetSuite handles consolidated financials across entities, multi-currency, and project accounting in a way that does not require complex customisation.
The data migration from GP to NetSuite is more involved than to Business Central, the data models differ significantly. We scope NetSuite migrations with that complexity factored in. Your NetSuite partner handles the implementation.
Migrate to MYOB Acumatica for Australian mid-market businesses
For Australian businesses that want cloud ERP functionality with strong local compliance, MYOB Acumatica is worth serious consideration. Australian payroll, STP, BAS, and superannuation are natively supported. The MYOB partner network in Australia is well-established.
MYOB Acumatica suits the same business profile as Dynamics GP: multi-entity, inventory management, job costing, and distribution. For businesses that do not already run deep in the Microsoft ecosystem, it avoids the Microsoft 365 dependency that Business Central assumes.
The migration path from GP to Acumatica requires the same data extraction and transformation work as any other target. We handle that side. Your MYOB Acumatica partner handles the platform configuration.
Not every GP business needs another single ERP.
The default assumption when leaving GP is to move to Business Central. Microsoft recommends it, it is the Microsoft path, and for many GP businesses it is the right answer.
But a growing number of Australian mid-market businesses are retiring GP by moving to a connected stack of specialist apps instead. Xero or MYOB for core accounting. Deputy or Employment Hero for HR and payroll. simPRO or ServiceM8 for field service. Unleashed or Cin7 for inventory. Each app does one thing well, costs less than a full ERP, and can be swapped out later.
The catch is integration. The apps only work as a coherent business system when they are properly connected. That is what we do. We migrate your GP data into each app, then build the integration layer between them. Worth evaluating if the complexity you ran on GP has reduced, or if the business has simplified.
A typical connected stack replacing Dynamics GP
An example of what a modern multi-app architecture looks like. Specific apps depend on your industry and workflows. We help you choose the right pieces.
Core Accounting
Xero or MYOB for the general ledger, AP/AR, bank feeds, invoicing, and BAS. Australian-built, STP-compliant, with rich ecosystems of connected apps.
HR & Payroll
Deputy or Employment Hero for rostering, time and attendance, leave, and payroll. Native Australian compliance, with mobile access that GP Payroll could never match.
Field Service & Jobs
simPRO, ServiceM8, or Tradify for job management, scheduling, quoting, and invoicing. Mobile-first. Covers the job costing workflows many GP businesses run.
Inventory & Wholesale
Unleashed, Cin7, or Dear for inventory, purchasing, and multi-warehouse stock. Handles the GP inventory use cases with a modern API and cloud access.
Integration Layer
This is where we come in. We build the connections between each app so your stack works as one business system. GP data migrated in, then integrations that keep everything in sync. Monitored, alerted on failure.
Unified Reporting
One dashboard layer pulling data from Xero, payroll, field service, and inventory into a single view. Live P&L, cash flow, team utilisation, job profitability. What GP Report Writer could never do.
Dynamics GP to Business Central: manufacturing business, 12 years of data
A Perth manufacturing business migrated from Dynamics GP 2016 to Dynamics 365 Business Central. Twelve years of financial and inventory data migrated. Dexterity production scheduling customisation rebuilt as a Business Central AL extension. Four GP Report Writer reports rebuilt in Power BI. Live before the GP 2016 extended support deadline.
Read the full case study →Situations we handle for Dynamics GP users
If you recognise your situation here, we have done this before.
Businesses with a confirmed GP end date
December 31, 2029 is a fixed date. If you are on Dynamics GP, you have a migration deadline whether you have started planning or not. Businesses that begin now have time to do it properly.
Businesses on older GP versions with no upgrade path
GP 2016 extended support ended July 2026. GP 2018 ends January 2028. If you are on an older version, you may already be out of support or approaching it fast.
Finance teams dealing with GP upgrade overhead
Every GP version upgrade is a project. Dexterity customisations need testing and often repairing. Third-party add-ons need re-validation. It takes weeks every cycle. That overhead will only stop when you migrate.
Businesses with disconnected systems
Your CRM, job management, and e-commerce platform connect to GP via fragile SQL-based integrations. They break on patches. Staff maintain them manually. You want a clean break onto a platform with real API support.
IT managers building the business case
The CFO has not asked about GP yet, but the December 2029 deadline is close enough that you need a realistic scope, timeline, and budget before it becomes urgent. We can help you build the case.
Businesses with heavy Dexterity customisations
Dexterity customisations do not migrate to Business Central. You need an audit of what you have, a plan for what needs rebuilding, and a team that can deliver both the migration and the custom build.
How a Dynamics GP migration project works
Every GP environment is different. This is the structure we follow to keep migrations clean, on schedule, and low-risk.
What we bring to a GP migration project
The specific technical capabilities we apply across migration, customisation rebuild, and reporting work.
GP SQL Extraction
Direct SQL access to the Dynamics GP database. We know the GP table structure across versions, including company databases, system databases, and the GP data dictionary for custom fields.
Business Central API & Dexterity Rebuild
Migration to Business Central using the BC API for data import. Dexterity customisations assessed and rebuilt as AL extensions on the new platform.
ETL & Data Transformation
Purpose-built ETL pipelines extracting from GP SQL, applying data quality rules, transforming to the target schema, and loading cleanly. Re-runnable for test migrations.
Report Rebuild & Power BI
GP Report Writer and Management Reporter reports rebuilt in the target platform native tools or in Power BI and React dashboards. We inventory all reports in use before deciding what to rebuild versus retire.
Integration Rebuild
SQL and file-based GP integrations rebuilt on the target platform API. More reliable than the original integrations, monitored, and with automated alerting on failure.
Custom Tools & Portals
External web applications built to extend GP today and transition to your new platform after migration. Customer portals, approval workflows, and data entry tools that do not add more complexity to GP.
We had been aware of the GP end-of-support date for two years but kept deferring because of the Dexterity customisations. HELLO PEOPLE audited the whole environment in two weeks, told us exactly what needed rebuilding, and delivered a complete migration to Business Central six months before the deadline. Nothing was lost.
Why HELLO PEOPLE
We build, not just advise
We write the ETL pipelines, rebuild the Dexterity customisations, migrate the reports, and reconnect the integrations. No subcontracting, no offshore handoffs.
Fixed-price quoting
You get a clear price after we audit your GP environment. No hourly billing that spirals mid-project.
Australian compliance covered
Australian payroll, BAS, STP, and superannuation requirements are handled on whichever platform we migrate you to. We work in these systems every week.
Senior team, direct access
You talk to the people doing the work. No account managers or ticket queues between you and the project team.
Full code ownership
Every integration, extension, and dashboard we build is yours. Full source code and documentation.
Common questions about Dynamics GP migration
When does Microsoft end support for Dynamics GP?
Microsoft has formally announced end of support for Dynamics GP on December 31, 2029. Security updates and patches will continue until April 30, 2031, but product updates, tax table releases, and technical support all stop at December 31, 2029. This is a fixed, published deadline.
What is Microsoft recommending as the replacement for Dynamics GP?
Microsoft explicitly recommends Dynamics 365 Business Central as the successor to GP. Their documentation, partner communications, and migration tooling all point in that direction. For most GP businesses, Business Central is the right destination. Some businesses use the migration as an opportunity to evaluate NetSuite or MYOB Acumatica instead.
Is GP to Business Central an upgrade or a migration?
It is a migration. GP and Business Central are architecturally different products. The data models do not align, Dexterity customisations do not run in Business Central, and the customisation model (AL extensions) is different from what GP uses. Plan it as a full migration project, not an upgrade.
What happens to our Dexterity customisations?
Dexterity customisations do not carry to Business Central. During the audit phase, we catalogue every Dexterity customisation in your environment. We then confirm which are still needed and rebuild them as AL extensions on Business Central. Some GP customisations are covered by standard Business Central features, which reduces the rebuild scope.
What about our GP Report Writer and Management Reporter reports?
Neither GP Report Writer nor Management Reporter reports migrate automatically. We take a full inventory of reports in use, confirm which are needed, and rebuild in Business Central native reporting, Power BI, or React dashboards depending on the report type. Standard financial reports are usually addressed by Business Central native tools. Complex analytical reports and management dashboards are better handled externally.
How long does a Dynamics GP to Business Central migration take?
Typically 4 to 8 months depending on data volume, Dexterity customisation complexity, number of integrations, and report rebuild scope. Businesses that are on older GP versions (pre-2016) with significant customisation should plan for the longer end. We scope the project properly before committing to a timeline.
Can we keep the business running during the migration?
Yes. You continue using GP throughout the project. The test migration runs in a sandbox environment. Both systems run in parallel during the validation period. Cutover happens at an agreed date, usually aligned with end-of-month or end-of-financial-year. GP stays accessible in read-only mode for historical reference after cutover.
What if we are still on GP 2016 or an older version?
GP 2016 extended support ended July 2026. GP 2015 ended April 2025. If you are on either of those versions, you are already out of full support. That does not mean the software stops working, but it means no tax updates, no compliance updates, and no technical support. Starting the migration project as soon as possible is the right move.
Get Started
Talk to us about your Dynamics GP situation
Tell us what version of GP you are on, what customisations exist, and when you need to be off the platform. We will come back with a clear plan and a fixed-price quote.
Talk to Us About Dynamics GP Migration
Tell us about your GP environment: version, data volumes, Dexterity customisations, integrations, and your target migration date. We will come back with a realistic plan and fixed-price quote.
Prefer a quick chat? Call 0425 531 127 – we're Perth-based and we answer the phone.