Business Central vs Navision: one product line, three names

Business Central vs Navision: the same roots

Navision began in Denmark as an accounting system for small companies. It spread widely through a network of resellers who adapted it to local needs. Then Microsoft bought the company and renamed the product Dynamics NAV. It kept releasing new versions under that name for many releases.

Business Central is the successor to NAV. Core ideas carried over intact. They include the general ledger with dimensions, posting groups, journals, and documents that post to ledger entries. The Navigate function lives on as Find Entries. So a user who knew Navision well will recognize the structure beneath the newer screens.

From a Windows client to the browser

Navision and older NAV versions ran through an installed Windows client. First came the classic client and later the role-tailored one. BC runs in a web browser, on a tablet or on a phone. So there is no client software to install or patch on each computer.

The web client adds things the older clients lacked. Users can personalize pages, save filtered list views and analyze data in pivot-style analysis mode. They can also open records from Outlook and Teams. Copilot features help with tasks such as bank reconciliation. Keyboard-driven data entry, which Navision users valued, still works well.

Business Central vs Navision: C/AL changes versus AL extensions

In Navision, partners changed the base application objects directly in C/AL. That made deep tailoring easy and upgrades hard, because each change needed a manual merge into every new version. Many firms stayed on old versions for that reason, and fell further behind.

Business Central uses AL extensions. An extension adds fields, pages and logic through events, and it leaves Microsoft's code alone. So the base application can be updated underneath it. Moving up therefore means deciding which old changes you still need. Then you note which standard features now replace them, and rewrite the rest as extensions.

Servers you run versus a service Microsoft runs

A Navision install meant a database server, application servers, backups and a partner visit for every upgrade. BC online removes that layer. Microsoft hosts the service, applies two release waves a year plus monthly updates, and provides sandboxes for safe testing.

An on-premises edition of Business Central still exists for firms that must keep data on their own systems. It gets the same application features on a similar schedule. But some cloud-linked features are limited there. We explain the differences, so you make the hosting choice knowingly.

How the move from Navision to Business Central works

There are two routes. A technical upgrade converts the existing database step by step through supported versions, and it keeps all history. A fresh setup starts with a clean BC company and brings in master records and opening balances. Older and heavily changed systems usually suit the second route.

For supported NAV versions, Microsoft's cloud migration tool can copy data to Business Central online. First the database must reach a compatible level. We examine your version, your object changes and your data volume. Then we recommend a route and explain what history you keep under each.

Business Central vs Navision: questions from long-time users

Is Business Central just Navision with a new name?

It is the same product line, and much of the business logic is easy to recognize. But the technology has changed a great deal. You now get a web client, AL extensions in place of C/AL changes, and an online service that Microsoft hosts and updates. So the daily work feels familiar, while the upkeep feels very different. Most long-time users say the biggest relief is that upgrades stop being a project of their own. We walk your team through each change before go-live.

Business Central vs Navision: can our customizations move across?

Not directly. We must redesign C/AL changes to base objects as AL extensions. In practice, many old changes are dropped, because standard BC now does the job. We go through each one with you and decide. Some stay as small extensions, some become setup, and some simply retire. The result is usually a much shorter list of custom work than the one you carry today, and that makes every later update easier for your team.

Do we have to move to the cloud?

No. Business Central is available on premises as well as online. Most firms choose online to avoid running servers and to get updates automatically. But the on-premises edition remains an option where company policy requires it. We explain the trade-offs in plain terms. Then you choose with the facts in hand. If your needs change later, a move between the two editions is possible, and we can plan it with you.

Will we lose our transaction history?

That depends on the route. A step-by-step technical upgrade keeps history in the database. A fresh setup brings balances and open items, and the old system stays available for lookups. We help you weigh the two. Think about who needs old detail, and how often they look at it. That answer usually points to the right route.

Is Navision still supported by Microsoft?

Microsoft posts support dates for each Dynamics NAV version on its lifecycle pages. Older versions have passed the end of support. We can check your version against the current list and tell you where you stand. Then we plan your next step with a safe margin.

Planning a move from NAV

Once you know how BC differs from Navision, the next questions are about migration and hosting. These pages go into each, and the comparisons hub lists the other systems we have compared. If Business Central vs Navision is your open question, start with the migration page. Then tell us your NAV version and your main add-ons, and we will suggest the route that fits. For the product detail, see Microsoft's guide to migrating on-premises data to Business Central online.