Preserve critical workflows
Identify the distribution, finance, inventory, warehouse, and integration processes that must be protected before the solution is changed.
Australian NAV migration planning
Dynamics NAV to Business Central migration in Australia
Based in Sydney, NSW, LeXurey helps Australian organisations assess a controlled move from Microsoft Dynamics NAV to Dynamics 365 Business Central. Discovery establishes the current application, connected systems, data choices, testing needs, and people impact before the agreed migration scope is documented.
NAV versions and application code
Assess common environments including NAV 2009, NAV 2013 / R2, NAV 2015, NAV 2016, NAV 2017, and NAV 2018, then identify C/AL customisations that may need redesign or conversion to AL extensions.
Integrations and dependencies
Catalogue APIs, web services, EDI, ecommerce, warehouse, reporting, payment, and other connected systems so each dependency can be assessed for retention, replacement, redesign, or retirement.
Data and history choices
Agree which companies, master data, open transactions, balances, historical records, and archives are in scope rather than assuming every record will move.
Testing and cutover
Define user-acceptance responsibilities, test scenarios, reconciliation, issue handling, cutover sequencing, and acceptance evidence for the agreed scope.
Training and adoption
Confirm the user groups, role-based training allowance, delivery approach, and timing in the Statement of Work so operational teams can prepare for the change.
Post-go-live support
Set the agreed hypercare period, hour cap, support channel, escalation path, and transition into any separately agreed ongoing support arrangement.
Planned weekly live Q&A · 30 minutes
NAV-to-Business Central Readiness Clinic
Bring one question about NAV versions, must-preserve workflows, customisations, integrations, data, user roles, testing or cutover. LeXurey is preparing a focused online clinic with practical general guidance and live Q&A; no system access is required.
Proposed Wednesdays
19 Aug–30 Sep 2026
12:30–1:00 pm
Sydney time (AEST)
Online Q&A planned
Join details only after LeXurey confirms the session
The structured readiness check is the monitored path for qualification and follow-up. Email is a secondary request-details option. Until LeXurey confirms the online session and sends joining details, neither action is an event registration or confirmation, licence order, eligibility decision or reservation of the offer.
Migration planning guides
Understand the path before defining the project
These practical guides explain the main cost, version, data, and customisation decisions behind a NAV-to-Business Central move. Current Microsoft documentation and discovery evidence still determine the final route.
NAV migration cost and timeline in Australia
Build an evidence-based estimate that separates licences, delivery, data, customisation, testing, cutover, and ongoing operation.
Read the guideNAV 2009–2018 migration paths
Compare Microsoft-documented technical routes and the decisions that shape a full migration or reimplementation.
Read the guideC/AL to AL conversion checklist
Inventory, assess, redesign, convert, test, and hand over the custom application behaviour that still matters.
Read the guideThe free agreed scope
What the $0 implementation may include
All implementation professional services expressly listed in the signed Statement of Work are provided free of charge. Depending on assessment, the agreed baseline may include services in these categories.
Agreed data migration
Limited to the companies, records, history, and volumes expressly stated in the Statement of Work.
One structured UAT cycle
A defined user-acceptance cycle for the agreed in-scope solution, with customer testers and validation responsibilities documented.
Agreed training allowance
The number of sessions or hours, audiences, and delivery approach are confirmed in the Statement of Work.
Capped post-go-live hypercare
A defined period, hour limit, and support channel for the agreed post-cutover support window.
2-minute offer eligibility check
See whether your NAV environment fits the offer
These short answers help LeXurey assess your NAV environment, expected licence count, operational priorities, and delivery timing. Applying does not reserve the offer.
No passwords or system access
Offer FAQ
Free, scope, licences, and timing—explained clearly
Is the implementation really free?
Yes. The implementation professional-services fee is $0 for the exact scope written in the signed Statement of Work. The selected customer pays the required first-year Business Central licence fees. Third-party costs, approved expenses, and work outside the agreed scope are not free.
Who is eligible for the offer?
The offer is for one customer moving from Microsoft Dynamics NAV to Business Central. There is no minimum licence-count requirement. LeXurey assesses technical fit, scope clarity, customer readiness, delivery timing, and the required Business Central licence order before confirming eligibility.
When does the offer close?
The offer closes on 9 September 2026 or as soon as one eligible customer accepts it, whichever happens first. An enquiry, readiness check, or assessment does not reserve the place. The place is secured only after written eligibility confirmation and signature of the required agreements.
What does the agreed baseline include?
It is the clearly defined solution needed to support the critical business outcomes accepted for the initial implementation. Depending on assessment, it may include agreed configuration, data migration, one structured UAT cycle, training, cutover, go-live support, and capped hypercare. Only items expressly recorded in the Statement of Work are included.
Will every NAV customisation and historical record be migrated?
Not automatically. Discovery determines which business outcomes should be retained and whether standard Business Central, an extension, an integration, or a revised process is appropriate. The included companies, record types, history periods, data volumes, customisations, and integrations must be expressly agreed.
What happens after the system is stable?
A stable Business Central foundation is the first step. The customer may later choose separately scoped improvements such as reporting, integrations, warehouse workflows, process optimisation, automation, or AI-enabled exception handling. These improvements are optional and are not required to receive the free agreed implementation.
Do Business Central licence fees continue after the first year?
Yes. Continued use of Business Central requires an active Microsoft subscription. The offer requires the selected customer to pay the first-year licence fees; renewals, future pricing, licence changes, and any ongoing LeXurey services are governed by the applicable terms at that time.
Can a migration be guaranteed to have no disruption?
No responsible provider can guarantee a disruption-free migration. LeXurey manages operational risk through discovery, agreed responsibilities, testing, reconciliation, cutover planning, and defined hypercare. The signed Statement of Work records the final approach and acceptance criteria.