Services

ERP implementation, upgrades and migration

Projects with a defined scope, named milestones, acceptance criteria and a realistic cutover plan. Whether you are moving from Dynamics NAV to Business Central, from on-premises to the cloud, or from spreadsheets to a first ERP, the method is the same: understand the processes, fit the standard, migrate clean data, test properly, support the go-live.

Request a proposal Book a discovery call

Illustration of a legacy system panel migrating to a new system along a route with milestones

The problem we solve

Upgrades get postponed because the last project hurt

Many organisations are running versions of Dynamics NAV or Business Central that are years out of support, on servers that are due for retirement, with customisations nobody fully understands. Everyone agrees the system should be upgraded; nobody wants to repeat the disruption of the original implementation.

The way to de-risk a migration or implementation is not a bigger project team but a better-scoped one: a thorough assessment up front, a fit-gap that favours standard features, data cleansed before it is migrated, test cycles planned with the business, and a cutover rehearsed before the real weekend.

A NAV version that no longer receives updates, running on ageing infrastructure
Heavy customisations that block the standard upgrade path
Master data (items, customers, vendors, BOMs) known to be inconsistent
Integrations with web shops, EDI partners or warehouse systems that nobody wants to touch
Previous projects that overran because scope was never agreed in writing

Who this is for

Organisations on Dynamics NAV or an older Business Central version planning a move to Business Central online
Companies moving ERP workloads from on-premises servers to Microsoft cloud
Growing businesses replacing spreadsheets, accounting packages or a legacy system with a first ERP
SAP Business One customers planning upgrades, HANA migrations or new companies
Groups adding entities or countries to an existing Dynamics 365 or SAP environment

What the service covers

Our implementation and migration projects follow a structured path from assessment to post-go-live support. The Netherlands-facing project lead owns scope, governance, planning and client communication; certified consultants at the Ibadan hub perform configuration, development, data migration scripting and testing under supervision. You get one plan, one status report and one accountable lead.

We favour standard functionality and documented extensions over bespoke code, so that the system you go live with is one that can be updated routinely afterwards. Every project ends with a defined hypercare period and a handover into managed support if you want it.

Activities within the service

Initial assessment and requirements discovery with key users
Fit-gap analysis and process mapping where in scope
Migration and upgrade planning: technical path, customisation inventory, licensing and infrastructure
Configuration, extension development and integration rebuild
Data migration: mapping, cleansing rules, trial loads, validation and reconciliation
Test planning, user acceptance testing support, cutover coordination and go-live
Post-go-live hypercare and transition into managed support

Platforms covered

Dynamics NAV to Business Central
Business Central on-premises to cloud
Dynamics AX to Finance and Supply Chain Management
SAP Business One
Spreadsheet or legacy systems to a first ERP

Common use cases

Dynamics NAV to Business Central online

Customisations assessed, replaced by standard features or rebuilt as AL extensions, data migrated with the cloud migration tooling or scripted loads, and users trained on the modern client.

Business Central on-premises to cloud

Infrastructure dependencies, integrations and printing reviewed; a staged migration with rehearsal cutover and a documented rollback point.

First ERP for a growing wholesaler

Processes from quote to cash and purchase to pay mapped, Business Central configured to the standard with a minimal set of extensions, and item and customer data cleansed before load.

Adding a foreign entity to an existing environment

A new company set up with localisation, intercompany and consolidation configured, and reporting extended to include it.

SAP Business One upgrade or HANA migration

Version upgrade or move to HANA planned with add-on compatibility checks, test cycles and a cutover window agreed with operations.

Practical deliverables

Assessment report and migration or implementation roadmap with options and recommendation
Scope statement with dependencies, milestones, responsibilities and acceptance criteria
Fit-gap document and solution design for in-scope processes
Configured system, extensions and integrations with technical documentation
Data migration plan, trial-load results and reconciliation reports
Test plan, test scripts, cutover runbook and hypercare report

What you can expect

A supported, updatable system with far fewer bespoke modifications
Migrated data you have reconciled and can trust
A cutover with a rehearsed plan and a known rollback point
Users who were involved in testing and are ready on day one

How an engagement runs

Assess
Current system, customisations, integrations, data and processes reviewed; options and a recommended path documented.
Scope and plan
Scope, milestones, acceptance criteria, team, governance and commercial terms agreed in writing before build starts.
Design and build
Fit-gap, configuration, extensions, integrations and migration scripts delivered in planned iterations with reviews.
Test and rehearse
System test, user acceptance test and at least one cutover rehearsal with reconciled trial data.
Go live and support
Cutover executed to the runbook, hypercare with daily check-ins, then handover to steady-state support.

Scope and delivery boundaries

Project duration depends on scope, data quality and the availability of your key users; we give a planned timeline in the proposal and report against it, but we do not quote generic durations
Scope changes are handled through a documented change process with impact on time and cost made explicit
Infrastructure provisioning (servers, networks, Microsoft tenant set-up) is coordinated with your IT provider unless agreed as part of the project
Third-party add-ons and ISV solutions are included only where the vendor supports the target version

Frequently asked questions

How long does a NAV to Business Central migration take?

It depends on the NAV version, the number and depth of customisations, data volume, integrations and how much time your key users can commit. The assessment gives you a planned timeline specific to your situation; we do not quote standard durations because they are rarely accurate.

Can we keep our customisations?

Some, yes; many are better replaced. Each customisation is classified: covered by standard functionality today, replace with an extension or app, or rebuild as an AL extension. You decide with full visibility of the cost of keeping each one.

How do you make sure migrated data is correct?

With mapping and cleansing rules agreed up front, several trial loads, and reconciliation reports (trial balance, open items, inventory value and quantity, open orders) signed off by your finance and operations leads before the final cutover.

What happens after go-live?

A hypercare period with daily check-ins and prioritised fixes, followed by a handover to managed support or your internal team, including documentation and open-item lists.

Do you work with our existing hosting or Microsoft partner?

Yes. Many projects involve an IT provider for infrastructure or a licensing partner. Responsibilities are written into the project plan so that handoffs are clear.

Plan your upgrade or implementation with a clear scope

Share where you are today and where you need to be. We will propose an assessment that results in options, a recommendation and a planned, scoped project.

info@neuronsuite.com +234 702 019 7438 Monday to Friday, 08:00 to 17:00