Skip to main content

Microsoft Dynamics 365 Business Central

Dynamics NAV to Business Central migration and upgrade

Define the migration path, risks and acceptance before delivery starts. For old, heavily customised or integration-heavy environments, the right route depends on the actual legacy state — not a standard promise.

Review your migration situation

Make the migration decisions before committing to delivery.

Target platform
Business Central Online or another agreed target state.
Customisations
keep, replace with standard functionality, replace with an app, redesign or retire.
Data and history
what moves, what is transformed and what remains available in the legacy system.
Integrations and add-ons
dependencies, replacements and ownership.
Local functionality
reporting, banking, payroll, EDI and other country-specific requirements where relevant.
Cutover and acceptance
test evidence, readiness, responsibilities and the agreed target state.

Migration Assessment: a defined scope and migration path before execution.

The paid Migration Assessment defines the technical state, appropriate migration path, risks, assumptions and execution scope. The output is a decision-ready migration definition and a commercial basis for the next stage.

  • current and target state;
  • recommended migration approach;
  • assumptions and dependencies;
  • data, customisation and integration risks;
  • migration and cutover approach;
  • test and acceptance basis;
  • estimate range and recommended delivery model.

Possible migration routes

  • Technical upgrade / conversion

    Retain and convert the parts of the existing solution that still make sense, while moving the system to the agreed Business Central target.

  • Reimplementation / cleaner restart

    Use standard Business Central, selected apps and redesigned processes where carrying legacy customisation forward creates more cost or risk than value.

  • Hybrid route

    Keep selected legacy logic, replace other areas with standard functionality or apps, and migrate the data/history that the business actually needs.

The assessment determines the route; JEMEL does not force every system through the same migration method.

Delivery after assessment

  1. Build and test

    Configure and develop the agreed target, prepare migration/data work, rebuild required integrations and support structured testing against the agreed acceptance basis.

  2. Rehearsed cutover

    Plan and rehearse the production transition, including responsibilities, sequence, validation and contingency appropriate to the actual system.

  3. Post-go-live support

    Agree the post-go-live support model according to the system and project. Priority Support and Application Management are available where ongoing readiness and maintained system knowledge are required.

Senior responsibility for difficult technical change.

JEMEL combines implementation and migration experience with software-building capability. The responsible specialist remains directly involved, while additional specialists can deliver defined parts when required.

  • 20+ years — with Microsoft Dynamics, from Navision and Dynamics NAV to Business Central
  • 150+ — implementation, migration and upgrade projects
  • Core team — MB-800-certified senior specialists

Review your migration situation.

If the route is already clear, we can scope delivery. If material uncertainty remains, the next step is a paid Migration Assessment.

Review the migration