Case study · Manufacturing
Off an ageing NAV, without losing what works
Many manufacturers still run Dynamics NAV with years of modifications, on servers that are getting old. This is how we moved them to Business Central online: reviewing every modification, rebuilding the ones that matter as extensions and migrating the data safely.
Project overview
A modification-aware upgrade from NAV to Business Central.
- Industry
- Manufacturing
- Client
- Confidential
- Solution
- ERP upgrade and migration
- From
- Dynamics NAV 2009–2018
- To
- Business Central online
- Timeline
- 16–28 weeks
- Team
- 5 people
- Approach
- Rebuild modifications as extensions
- History
- Migrated or archived
Expected business outcomes
What the client set out to gain
The main gains are removing old infrastructure and being able to take Microsoft updates again.
-
30–60%
Fewer custom modifications
Modifications replaced by standard features that didn't exist when NAV was set up.
Target range after code review; depends on the original customisation
-
Twice a year
Microsoft updates applied
Extensions keep the base application untouched, so updates arrive automatically.
Business Central online release cadence
-
Zero
On-premises servers to maintain
The application runs in Microsoft's cloud.
Unless a local integration server is kept
Business challenges
How NAV systems looked before
NAV served the business well, which is why it is still there.
Code
Years of modifications made directly in the base code, some undocumented.
Infrastructure
A server in the office or a data centre, running an old version of SQL Server and Windows.
Updates
Upgrades were skipped because each one meant redoing the modifications.
Integrations
Scanners, EDI and reports connect in ways only one person understands.
Risk
Support for the old version has ended, and the people who built it have moved on.
Proposed solution
What the upgrade covers
An upgrade is mostly a review: what to keep, what standard now covers, and what to retire.
-
Modification review
Every modification listed, explained and classified as keep, replace with standard or retire.
-
Extensions in AL
Kept modifications rebuilt as extensions that survive Microsoft updates.
-
Data migration
Master data, open documents and balances migrated, with history kept or archived.
-
Integrations
Scanners, EDI and other connections moved to Business Central APIs.
-
Reports
Custom reports rebuilt or replaced by standard reports and Power BI.
-
Testing
Automated tests for extensions and a full test cycle with key users.
Project requirements
What the client asked us for
The request was to get off an unsupported version without disrupting production. The key decision is which modifications are still needed; many were built for problems standard Business Central now solves.
We plan the go-live around the production calendar, usually over a weekend with a tested rollback, so the factory never waits for the system.
What the project had to deliver
- 01Off unsupported software and servers
- 02Only the modifications that still matter
- 03Updates from Microsoft without rework
- 04A go-live that doesn't stop production
Key challenges & considerations
What made it harder, and what we did
-
Undocumented modifications
What we did
Every modification was listed and questioned: kept as an extension, replaced by a standard feature, or retired.
-
Old data with inconsistencies
What we did
Data was cleaned during two full rehearsal migrations, with the differences reviewed by finance each time.
-
Integrations built on direct database access
What we did
Integrations that read the database directly were rebuilt on Business Central's APIs.
-
Key users who are also running production
What we did
Testing was scheduled around production, with key users released for short, planned sessions.
What we watched for
- Question every modification before rebuilding it
- Rehearse the migration twice
- Plan go-live around production
- Document the extensions properly this time
Development process
Review, rebuild, rehearse, go live
Two rehearsal migrations before the real one are what make go-live weekends calm.
-
Code and process review
Every modification traced to the process it supports and classified.
-
Extension development
Kept modifications rebuilt in AL with automated tests.
-
Data migration rehearsals
Two full practice migrations with reconciliation of balances and stock.
-
User testing
Key users test their daily processes end to end on migrated data.
-
Go-live weekend
Final migration, checks and sign-off, with a rollback plan ready.
Technology stack
From C/AL to AL and the cloud
Modern Business Central development practices replace direct base-code changes.
ERP
- Business Central online
- AL extensions
- Sandbox environments
Migration
- Cloud migration tools
- Data upgrade scripts
Quality
- Automated tests
- Azure DevOps pipelines
Reporting
- Standard reports
- Power BI
Quality assurance & deployment
Proved on the client's own data before go-live
An ERP is trusted when the numbers agree. Configuration and extensions were tested in a sandbox on the client's own data, and finance signed off the figures before cut-over.
- Sandbox testing of every process on the client's own data
- User acceptance testing with key users, by scenario
- Migration rehearsals, reconciled to the old system
- Automated tests for extensions, run before each release
- Permission sets checked role by role
Deployment
- 01User testingKey users test their daily processes end to end on migrated data.
- 02Go-live weekendFinal migration, checks and sign-off, with a rollback plan ready.
- 03Cut-over planA rehearsed cut-over with a checklist, opening balances signed off by finance, and a rollback point.
- 04Hypercare and warrantyConsultants on hand through the first month-end, and six months of free bug fixing.
Final deliverables
Modern, supported and still familiar
The business runs on Business Central online with only the modifications it still needs, each built as an extension that survives updates.
Users recognise their processes, the old servers are switched off, and future improvements can be made without an upgrade project every few years.
- Supported and updated automatically
- Fewer, cleaner modifications
- No servers to maintain
- Integrations on supported APIs
Handed over to the client
- 01Configured Business CentralProduction and sandbox environments
- 02ExtensionsSource code and documentation
- 03Migrated dataReconciled and signed off
- 04Key-user trainingWith process guides
- 05Six-month warrantyFree bug fixing after delivery
Success metrics
How success is measured
| Measure | Outcome | How it is measured |
|---|---|---|
| Fewer custom modifications | 30–60% | Target range after code review; depends on the original customisation |
| Microsoft updates applied | Twice a year | Business Central online release cadence |
| On-premises servers to maintain | Zero | Unless a local integration server is kept |
Verified reviews
What clients say about our Dynamics work
Verified reviews from our clients on the same kind of work, published on Clutch.
-
Custom Software Development
Web-Based Coupon App Development
The work produced by the team was of exceptional quality.
Jon Thies
CTO, Model Rocket Feb 2022 – Mar 2023
-
Custom Software Development
Mobile & Web Platform Development & Design
Silver Scintilla was responsive, respectful, and enjoyable to work with, quickly addressing any questions or requests.
DeShawn Brown
CEO & Founder, Lithios Jun 2021 – Nov 2022
-
Custom Software Development
Web-Based HRM System Development
Silver Scintilla provided the best solution with scalable functionality, personalized features, and robust security.
Suheb Khan
Director, Collaborative Insight Technologies Jul 2020 – Jun 2022
Related
Services we used on this project
Free discovery call
Have an idea? Let's turn it into AI-powered software.
Book a free discovery call with our experts. Share your idea and we will help you shape the scope, timeline and budget, under NDA.
- Free consultation
- NDA before we talk
- Transparent estimate