Dynamics NAV to Business Central Migration in Hong Kong: A Practical Guide

A Dynamics NAV-to-Business Central migration is more than a database transfer. Organisations must review their NAV version and customisations, decide which operational data to move, test day-one finance and inventory processes, and plan user adoption. Tectura has published regional NAV migration examples for a manufacturer and a retail/F&B group; each involved different versions, workflows and countries.

‍

Full migration, reimplementation and preview-tool status

For Dynamics NAV to Business Central online, Microsoft describes a full-migration route and a reimplementation route. Both begin with upgrading the NAV environment to Business Central 14 on-premises; a full migration then requires further supported upgrades and conversion of relevant C/AL customisations to AL extensions. Reimplementation focuses on selected business data rather than carrying forward all legacy code and history. Importantly, Microsoft’s dedicated Business Central 14 Reimplementation tool is still a preview feature, which Microsoft says is not intended for production use. Any live migration plan must be based on the supported tools, applicable versions and scope confirmed for that project. Microsoft’s NAV migration guidance.Business Central 14 preview-tool status.
‍

‍

Catalogue what must move

Prepare an inventory of companies, account balances, customers, suppliers, item records, open transactions, reporting requirements and audit history. Identify historical information that must remain accessible even if it is not moved into the live ERP. Document interfaces with warehouse systems, EDI, e-commerce and specialist applications.

Test the processes that matter

Focus testing on month-end close, purchasing approvals, stock movements, sales order processing and key reports. Use representatives from each department and record both expected outcomes and exceptions. Define a cutover plan, user training and the responsibilities of the client and implementation partner.

Choose a measured next step

Tectura has published Dynamics NAV migration projects in regional manufacturing and retail. A discussion can begin with your current NAV version, which history and customisations the business needs, and what must be tested before cutover. Tectura can help assess migration scope and the supported production approach before a delivery plan is agreed.

What belongs in a NAV migration decision log?

Use a decision log rather than assuming every feature must be retained. For each customisation, record the business owner, reason it was introduced, how frequently it is used, whether standard Business Central functionality or an extension can replace it, and whether it must be ready for day one. Put obsolete reports and little-used workflows in a separate retirement list.

Segment migration data into four categories: opening balances and open transactions; active master records; historic transactions required for operational reporting; and archives needed only for audit or occasional lookup. Each category can have a different migration or retention approach. Agree reconciliation tests and who signs them off.

The cutover plan should cover a parallel or mock run where appropriate, a final data extraction, reconciliation checkpoints, users’ access to historical information and a rollback or contingency decision. The existence of Microsoft migration tooling does not remove the need to validate legacy code, upgrade paths and extensions for the particular NAV version.

Tectura’s published migration examples cover two different operating contexts: an industrial equipment manufacturer with 750+ employees and 60+ Business Central users migrating from NAV 2017 across Hong Kong, Mainland China and Germany; and a retail/F&B group with 20+ shops and 70+ users migrating from NAV 2009 with LS Retail across Hong Kong, Mainland China and Japan. These figures describe the projects, not a standard timeline or cost. See the Business Central project examples.

‍

Frequently Asked Questions

‍

Can every NAV customisation be moved unchanged?

Not necessarily. Legacy code and customisations may need redesign or conversion into supported extensions.

‍

Does every company need to migrate all historical transactions?

No single rule applies. Define the migration dataset according to operating, reporting, legal and audit requirements.

Discuss NAV migration planning with Tectura.  Contact Tectura Hong Kong