SERVICES / 01
Modernise the application. Keep the business logic that earns you money.
Legacy business applications accumulate years of customisation that nobody fully documents. We inventory it, separate it from the platform, convert what should survive and retire what should not — with the data reconciled before anyone goes live.
TYPICAL ESTATE · Dynamics NAV, customised
TARGET · Dynamics 365 Business Central
ALSO · Other legacy line-of-business apps
OUTPUT · Converted, tested, documented
Know exactly what the old system does.
Inventory every customisation, add-on, report and integration. Decide, line by line, what to keep, replace or drop.
Pull the custom logic out of the core.
Business-specific code is separated from the standard platform so upgrades stop being a rewrite.
Rebuild as extensions, connections and clean data.
Retained logic becomes versioned extensions. Integrations are rebuilt through one layer. Data is migrated and reconciled against the old system before anyone goes live.
Upgrade on the platform's schedule, not in panic.
With customisations isolated and integrations monitored, platform updates become routine.
Several Microsoft products are leaving support.
01 — WHY NOW
| Product | Milestone | Date |
|---|---|---|
| Dynamics NAV 2017 | End of extended support | 12 January 2027 |
| Dynamics NAV 2018 | End of extended support | 12 January 2028 |
| Dynamics GP | End of mainstream support | 31 December 2029 |
| Dynamics GP | Final security updates | 30 April 2031 |
Source: Microsoft Lifecycle.
A support deadline is not an order to migrate immediately — some businesses will delay, buy extended assistance or choose another platform. It is, however, the right moment to know precisely what your customisations do and what a move would cost. That is what the assessment answers.
NAV and GP are different migrations. NAV estates typically involve converting C/AL customisations to AL extensions; GP uses a different data-migration route. We scope them separately and never assume one package fits both.
The Technical Migration Assessment.
An assessment can provide the evidence for a migration decision. Its fee, duration and outputs are agreed before it begins.
Customisation inventory
Every object, add-on and report, with its business purpose and owner.
Keep / replace / drop map
What converts, what the standard platform now covers, what is retired.
Integration inventory
Every inbound and outbound connection, including the undocumented ones.
Data-quality profile
Duplicates, orphaned records, inconsistent masters — quantified.
Estimate and scope
A priced, staged plan for the workstream, with acceptance criteria.
The migration workstream
Convert
Retained customisations rebuilt as versioned extensions.
Migrate
Data moved in rehearsals, not once.
Reconcile
Opening balances, stock and open orders matched to the legacy system and signed off.
Test
Scripted tests against the acceptance criteria; defects logged and closed.
Cut over
Planned window, rollback plan, hypercare period.
Illustrative scenario
ILLUSTRATIVE SCENARIO — NOT A CUSTOMER PROJECT
A wholesale distributor runs a heavily customised NAV 2017 with a warehouse system, a B2B web shop and EDI feeds from three major customers. The assessment finds 140 customised objects, of which 60 are covered by standard Business Central features, 55 are converted to extensions and 25 are retired. Integrations are rebuilt through one layer, data is rehearsed three times, and cutover happens over a weekend with a signed reconciliation report.
Working with partners
Working as a Dynamics partner with a migration backlog? See how we deliver under your brand →
Businesses
Tell us what you are running.
A short conversation about your systems, your constraints and your timeline. No sales deck.
Technology partners
Need defined delivery capacity?
Describe the workstream, the platform and the timeline. We will tell you plainly whether we are the right fit.