Dynamics NAV Data Migration
Migrate to Business Central, NetSuite, MYOB Acumatica, or a multi-app stack.
Every Dynamics NAV version has a published end-of-support date. NAV 2016 ended April 2026. NAV 2017 ends January 2027. NAV 2018 ends January 2028. We migrate your NAV data and rebuild your integrations for the new platform.
Perth-based, working with Australian businesses nationwide. We handle migration, C/AL to AL extension rebuild, and integrations. Your chosen platform partner handles the configuration.
Get a free consultation
Dynamics NAV to Business Central Migration for Australian Businesses
Dynamics NAV served Australian businesses well across distribution, manufacturing, and professional services. But every NAV version has a published Microsoft end-of-support date, and several are already past it. NAV 2016 ended April 14, 2026. NAV 2015 ended January 2025. Older versions have been unsupported for years.
HELLO PEOPLE migrates businesses from any NAV version to Business Central, NetSuite, MYOB Acumatica, or a multi-app stack. We handle the data migration side: SQL data extraction, transformation to the target schema, C/AL to AL customisation rebuild where the target is Business Central, integration reconnection, and report migration. We have done this on NAV 2009 through to NAV 2018.
Perth-based, working with businesses across Australia. We handle data migration and integration. Your chosen platform partner handles the ERP configuration.
Why businesses come to us about Dynamics NAV
These are the situations we see most often from businesses still running NAV.
Already past support, or getting close
NAV 2016 ended April 2026. If you are on an older version, you are already operating without Microsoft support, tax updates, or security patches. The risk grows every month you stay.
C/AL customisations that cannot be touched
Your C/AL modifications have become too risky to change. Every time you need to test or update them, something breaks. No one on the team fully understands the code that was written years ago.
Integrations that break on every NAV patch
The SQL-based connections between NAV and your other systems are fragile. Every patch risks breaking them. Your IT team spends more time maintaining the connections than the systems themselves.
Get Started
Still on Dynamics NAV with no migration plan?
Tell us what NAV version you are on, what C/AL customisations exist, and how much runway you have before your support end date. We will come back with a realistic scope and fixed-price quote.
Services for Dynamics NAV users
Data migration, C/AL to AL conversion, integration rebuild, and dashboards. We do not handle the ERP configuration itself, that sits with your chosen platform partner.
Migrate your NAV data to Dynamics 365 Business Central
Dynamics NAV has a clear end: Microsoft has published formal end-of-support dates for every version. NAV 2009 ended in 2020. NAV 2013/2013 R2 ended in 2023. NAV 2015 ended January 2025. NAV 2016 ended April 2026. NAV 2017 ends January 2027. NAV 2018 ends January 2028. Depending on your version, you may already be out of support.
We extract your NAV data from the SQL backend, transform to the Business Central data model, and load cleanly into your new environment. Chart of accounts, customers, suppliers, inventory, jobs, open AP/AR, and years of transaction history all migrate across. The transformation work is significant. NAV and Business Central have different table structures even though they share a code lineage.
We run the migration in a test environment first. Your finance team validates the data before anything goes near production. Issues are fixed in the ETL pipeline, not after go-live.
Custom integration services →Convert your NAV C/AL customisations to Business Central AL extensions
Every customisation built in C/AL (NAV's proprietary development language) must be rewritten in AL before it can run in Business Central. There is no automated migration path that handles complex C/AL code. It requires developers who understand both environments.
We audit your C/AL codebase during the discovery phase: what modifications exist, what they do, how complex they are, and whether the underlying functionality is already covered by standard Business Central features. Many NAV customisations become redundant on Business Central, which reduces the rebuild scope.
The remaining customisations are rebuilt as AL extensions: scoped, testable, and upgrade-safe. Unlike C/AL modifications that broke with every NAV version upgrade, AL extensions are isolated from platform updates.
Custom software development →Rebuild or extend your NAV integrations for Business Central
NAV integrations were typically built against the SQL backend or via web services. Business Central uses a REST API. Every integration that currently connects to NAV needs to be rebuilt for Business Central before go-live.
We handle this as part of the migration project: catalogue all current integrations, confirm which are still needed, and rebuild them against the Business Central API. CRM sync, e-commerce feeds, job management connections, field service platforms, and any custom systems that post data to NAV.
The rebuild is usually simpler than the original. Business Central's API is more complete and better documented than NAV's web services layer. Integrations that required workarounds in NAV often become straightforward on Business Central.
Custom integrations →Modern reporting and dashboards to replace NAV report layouts
NAV reporting runs on RDLC report layouts or Word layouts, with data typically accessed through NAV's report objects. Getting live data for management reporting requires workarounds: OData connections, scheduled data exports, or third-party BI connectors that need maintenance.
We build external dashboards connected to NAV today and rearchitected for Business Central after migration. Live P&L, divisional analysis, project profitability, cash flow, and debtor aging, accessible in a browser with no manual refresh step.
Business Central's native Power BI integration is considerably better than NAV's. If your business is already in the Microsoft ecosystem, we can connect Power BI directly to Business Central through the certified connector rather than building custom dashboards.
Dashboard & reporting software →
Where do NAV businesses migrate to?
Multi-app stack for businesses who want modern and modular. Business Central for the Microsoft-recommended path. NetSuite for a bigger change. MYOB Acumatica for Australian mid-market.
Replace NAV with a multi-app stack: Xero or MYOB plus specialist apps
You do not have to replace NAV with another ERP. Some NAV businesses, particularly those where the original NAV fit has drifted, retire the platform 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 is cheaper and simpler than a Business Central or NetSuite migration, and it avoids rebuilding C/AL customisations entirely. Each app is purpose-built, Australian-compliant, and can be swapped out later without rebuilding the whole stack. Worth evaluating if the complexity NAV ran has reduced over the years.
We migrate your NAV data into each app, then build the integration layer between them. Orders into Xero, timesheets into payroll, inventory into accounting, jobs into field service.
Migrate to Dynamics 365 Business Central, the Microsoft-recommended path
Business Central is the natural destination for NAV. The platforms share a code lineage. Microsoft actively supports the NAV to BC migration path, and the partner ecosystem has tooling that helps. For most NAV businesses, this is the right answer.
The migration is still a real project with real scope. NAV and Business Central have different table structures. C/AL customisations need converting to AL. Integrations need rebuilding against the Business Central REST API.
We handle the data migration and integration rebuild side. Your Dynamics partner handles the Business Central configuration, any AL extension builds, and user training.
Migrate to NetSuite for businesses considering a bigger change
NAV businesses with multi-entity or international complexity sometimes use the migration as an opportunity to move off the Microsoft stack entirely. NetSuite is the main candidate: cloud-native, multi-subsidiary, multi-currency, with a mature REST API.
This is a larger scope migration than moving to Business Central because the data models differ significantly. NAV to NetSuite means full re-mapping rather than the cousin-to-cousin move that BC represents.
We handle NAV to NetSuite data migration and integration rebuild. Your NetSuite partner handles the platform configuration.
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.
MYOB Acumatica suits the same business profile as Dynamics NAV: mid-market, 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.
We handle NAV to MYOB Acumatica data migration. Your MYOB Acumatica partner handles the platform configuration.
Not every NAV business needs another single ERP.
The default assumption when leaving NAV is to move to Business Central. Microsoft recommends it, the code lineage is shared, and for many NAV businesses it is the right answer.
But a growing number of Australian mid-market businesses are retiring NAV 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 avoids rebuilding C/AL customisations entirely.
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 NAV data into each app, then build the integration layer between them. Worth evaluating if the complexity NAV once ran has reduced, or if the business has simplified.
A typical connected stack replacing Dynamics NAV
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 for staff.
Field Service & Jobs
simPRO, ServiceM8, or Tradify for job management, scheduling, quoting, and invoicing. Mobile-first. Covers the job costing workflows many NAV businesses run.
Inventory & Wholesale
Unleashed, Cin7, or Dear for inventory, purchasing, and multi-warehouse stock. Handles the NAV 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. NAV 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.
Dynamics NAV 2016 to Business Central: distribution business, under the deadline
A Brisbane distribution business migrated from NAV 2016 to Dynamics 365 Business Central before the April 2026 support cutoff. Eight years of inventory and transaction data migrated. Five C/AL customisations rebuilt as AL extensions. Shopify and 3PL integrations reconnected to Business Central API.
Read the full case study →Situations we handle for Dynamics NAV users
If you recognise your situation here, we have done this before.
Businesses on NAV versions already past support
NAV 2016 and earlier are already out of support. If you are on one of these versions, you are running without tax updates, compliance patches, or technical support from Microsoft.
Businesses facing a NAV 2017 or 2018 deadline
NAV 2017 ends January 2027. NAV 2018 ends January 2028. Both are close enough that a migration project needs to start now to be done properly before the deadline.
IT managers stuck with fragile C/AL customisations
Every NAV version upgrade risks breaking your C/AL code. The testing and repair cycle takes weeks and blocks your ability to stay current. Moving to Business Central AL extensions solves this permanently.
Businesses whose NAV integrations break on patches
SQL-based and web services integrations to NAV are fragile. They break on patches. Staff maintain them manually. Business Central's REST API makes integrations dramatically more reliable.
Finance teams who cannot get real-time reporting from NAV
NAV reporting is snapshot-based. Real-time management dashboards require workarounds that create their own maintenance burden. Business Central with Power BI changes this significantly.
Businesses planning ahead with a Microsoft ecosystem
Already running Microsoft 365, Teams, and Azure? Business Central integrates natively across all of them. The case for migration is not just the end-of-support deadline — it is the platform integration benefits you gain.
How a Dynamics NAV migration project works
Every NAV environment is different. This is the structure we follow to keep migrations clean, on schedule, and low-risk.
What we bring to a NAV migration project
The specific capabilities we apply across data migration, C/AL conversion, integration rebuild, and reporting work.
NAV SQL Extraction
Direct SQL access to the NAV database across all supported versions. We know the NAV table structure, company database layout, and the variations introduced across NAV 2009 through 2018.
C/AL to AL Conversion
Manual conversion of C/AL code to AL extensions. We do not rely solely on automated conversion tools for complex logic. Every critical C/AL customisation is reviewed by a developer who understands both languages.
Business Central API Integration
Business Central REST API for all data imports and integration rebuilds. Proper API usage rather than direct database manipulation, ensuring upgrade safety post-migration.
ETL & Data Transformation
Purpose-built ETL pipelines for NAV extraction and Business Central loading. Data quality rules applied during transformation. Re-runnable for multiple test migrations.
Power BI & Dashboard Builds
Management reporting rebuilt in Power BI using Business Central's certified connector, or in React/Metabase dashboards where more custom presentation is needed.
NAV Report Migration
RDLC report layouts catalogued and rebuilt in Business Central native reports or external dashboards. We confirm what is in active use before rebuilding anything.
We were on NAV 2016 and had been ignoring the support deadline for eighteen months. HELLO PEOPLE audited our environment, told us exactly what the C/AL rebuild would involve, and delivered the whole project — data, customisations, integrations — three weeks before the support cutoff. The Business Central API integrations are far more reliable than what we had in NAV.
Why HELLO PEOPLE
We build, not just advise
We write the ETL pipelines, convert the C/AL to AL, rebuild the integrations, and migrate the reports. No subcontracting, no offshore handoffs.
Fixed-price quoting
You get a clear price after we audit your NAV environment and C/AL codebase. No hourly billing surprises mid-project.
Both sides of the migration
We know NAV well enough to extract from it reliably, and Business Central well enough to build properly on it. You need a team that is fluent in both.
Senior team, direct access
You talk to the developers doing the work. No account managers between you and the project.
Full code ownership
Every AL extension and integration we build is yours. Full source code, documentation, and the ability to take it elsewhere.
Common questions about Dynamics NAV migration
When did Microsoft end support for Dynamics NAV?
Microsoft has published specific end dates for every NAV version. NAV 2009 ended January 2020. NAV 2013 and 2013 R2 ended January 2023. NAV 2015 ended January 2025. NAV 2016 ended April 2026. NAV 2017 ends January 2027. NAV 2018 ends January 2028. If you are on NAV 2016 or earlier, you are already out of full support.
What is the replacement for Dynamics NAV?
Microsoft's official successor to Dynamics NAV is Dynamics 365 Business Central. It runs on the same core code lineage but has been rebuilt for the cloud, uses AL instead of C/AL, and runs in Azure with continuous updates. For most NAV businesses, Business Central is the right destination.
Is NAV to Business Central an upgrade or a migration?
It is a migration. Despite sharing a code lineage, NAV and Business Central have different data models, different customisation approaches, and different architectures. C/AL code does not run in Business Central. Plan it as a full migration project with proper scope and timeline.
What happens to our C/AL customisations?
C/AL code does not run in Business Central. All customisations need to be rewritten as AL extensions. Some C/AL logic is already covered by standard Business Central features, which reduces the rebuild scope. During the audit phase, we catalogue all your C/AL modifications and determine what needs building versus what is now standard functionality.
How long does a NAV to Business Central migration take?
Typically 4 to 8 months, depending on your NAV version, C/AL customisation volume, number of integrations, and data complexity. NAV 2018 migrations are the most straightforward. NAV 2009 or earlier migrations are more complex given the architectural gap. We scope the project properly before committing to a timeline.
We are on NAV 2016 — what should we do?
NAV 2016 extended support ended April 14, 2026. If you have not started migration planning, you should start now. That does not mean your NAV installation stops working today, but it means no tax updates, no compliance patches, and no technical support from Microsoft going forward. The longer you wait, the larger the gap between your NAV environment and modern Business Central.
Can our other systems keep connecting to NAV during migration?
Yes. Your existing NAV integrations keep running during the migration project. We rebuild the integrations for Business Central as part of the migration scope, and they are tested before cutover. You do not need to disrupt anything until go-live day.
Get Started
Talk to us about your Dynamics NAV situation
Tell us what version of NAV you are on, what C/AL customisations exist, and when your support deadline hits. We will come back with a clear scope and a fixed-price quote.
Talk to Us About Dynamics NAV Migration
Tell us about your NAV environment: version, data volumes, C/AL customisations, integrations, and your support deadline. 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.