info@ioi.gmbh Book an appointment +49 (0)214 8402 3000 Mon – Fri 09:00 – 17:00 CET

ERP migration to Business Central for any system on Microsoft SQL Server

With an ERP migration we bring master data, open entries, inventory and documents from your legacy system into Business Central. If your ERP runs on a Microsoft SQL Server, we read the data directly from the database. The bulk data runs weeks in advance; at go-live only the changes follow. Between the last and the first posting lie hours, not days.

14
source systems described
0   €
is what the migration check costs
1   weekend
between the last and the first posting
Basics

What is an ERP migration and how does it differ from an upgrade or a new implementation?

In an ERP migration you change the system and take all your data with you. Besides master data, that includes all open entries, inventory and documents. The program logic is rebuilt from scratch in Business Central. “Upgrade” and “new implementation”, on the other hand, mean something different and regularly cause misunderstandings in planning.

Upgrade

An upgrade stays within the product family. If you move from Navision or Dynamics NAV to Business Central, you raise the version. By now several years lie between the products. For this we have a dedicated, more automated path that carries over objects and code.

New implementation

With a Business Central new implementation you set up the system without taking over data. That is the right choice if the legacy system contains hardly any usable data or a company is starting from scratch.

Cloud or on-premises

Business Central is available as a cloud service from Microsoft and as an installation on your own servers. We serve both targets. The decision for your path is made early, because it determines interfaces, operations and updates. Do you want to keep data sovereignty entirely in-house? Then on-premises is the first choice. If you would like to spare yourself your own servers, backups and version maintenance, go to the cloud. There Microsoft updates twice a year.

When is the switch due?

The trigger rarely comes from the ERP itself. Often support for the version in use runs out or your server has reached the end of its life. In some cases the obligation to use the new e-invoice requires formats that are not available in the existing system or only with extra effort. On top of that there is often grown, never documented code that has long since blocked the way to a new version of the legacy system. If you have to invest anyway, you should not put the money into the old architecture.

Preparation

Answer a few questions for yourself before the migration check. What should Business Central be able to do after the switch? What could the legacy system not do, but would make your daily work easier? Typical answers are mobile working or reports in Power BI. Who from the departments tests as a key user and who decides? You do not have to prepare the inventory of your data and the data audit yourself. The migration check takes care of that.

Now you know which path is yours? We look into your database.

The migration check costs nothing and answers exactly the questions from the tiles above: upgrade, new implementation or migration, cloud or on-premises, and how much history comes along. All you need is a copy of your database.

Answer to the question of what can be migrated
Field inventory including undocumented custom fields
A concrete cost statement before you sign
Result after one to two weeks
Procedures

We read directly from your SQL database.

Most ERP changes fail at the data transfer, rarely at the new system. CSV exports and missing interfaces become an issue here just as much as a previous vendor that does not cooperate. That is why we read directly where your data lives.

01 · Access

Directly on the source database

We work on a copy of your SQL database, at table and field level. You need neither an export interface from the legacy vendor nor an approval from their maintenance contract.

02 · Mapping

Every table gets a mapping rule

Every source table is mapped to the matching Business Central tables. The mapping is documented and can be run as often as you like. Each run logs record counts and reconciliation totals in source and target. So the commitment of “100% data integrity” is backed by a log that you and your auditor can read.

03 · Cutover

First the bulk data, then only changes

The bulk data runs weeks before the changeover. Shortly before Go-live we transfer only the changes. Downtime in day-to-day business shrinks to hours instead of days.

Important to know

Data is transferred, not software.

Program logic, forms, reports and vendor-specific extensions of your legacy system are not carried over. They are rebuilt in Business Central, and much of it is already part of the standard. For the rest we write an extension that keeps running after the semi-annual Microsoft updates. Which of your customizations belong where is stated in the result of the migration check.

What was never documented in the legacy system shows up at the latest in the field inventory of the migration check. Custom fields and custom tables are in the database, even if nobody remembers who created them.

Clarified free of charge
in the migration check, before any order is placed
Source systems · Group 01

Complete commercial systems for mid-sized companies.

These include systems from financial accounting or merchandise management. They are solidly built and have grown in the DACH region. Often, however, they are tied to the desktop.

Sage 100

Based on: Microsoft SQL Server · Windows client

SelectLine

Based on: Microsoft SQL Server · Windows client

mesonic WinLine

Based on Microsoft SQL Server · dedicated client and web

Infoniqa ONE 200

Base: Microsoft SQL Server · focus CH and AT

Source systems · Group 02

Manufacturing and project ERP.

These are specialists for production and make-to-order manufacturing. Functionally, these systems are built deep. Technically, however, each one brings its own platform with its own life cycle.

APplus 8

Base: Microsoft SQL Server · web-based (.NET / IIS)

ams.erp

Basis: Microsoft SQL Server · lot size 1+

oxaion open / easy

Java client · IBM i history · SQL installations directly readable

Majesty ERP Gen2

Base: Microsoft SQL Server · .NET · medical technology

Source systems · group 03

Industry and specialist systems.

In their field these systems are strong. They are rarely a complete ERP, though. Often a second system runs alongside. This is exactly where the migration comes in.

JTL-Wawi

Base: Microsoft SQL Server · multichannel retail

DOMUS ERP & CRM

Base: Microsoft SQL Server · real estate

eserp

Basis: Microsoft SQL Server · installers and service

BMD NTCS

Basis: Microsoft SQL Server · accounting AT

Source systems · group 04

International platforms.

Technically, these systems can keep up with Business Central. What tips the balance is then the ecosystem and the proximity to the rest of the IT.

SAP Business One 10.0

Microsoft SQL Server or SAP HANA · Windows and web client

Haufe X360 / Acumatica

Base: Microsoft SQL Server · cloud ERP

Data scope

What is transferred – and what is created anew.

The exact scope depends on the source system. The division is the same in every project, however: we transfer the data automatically, the program logic is rebuilt in Business Central.

Master data

Customers, vendors, items, contacts, G/L accounts, dimensions, locations, prices and discounts.

Automated
Open entries

Open customer and vendor entries with due dates, payment terms and application references.

Automated
Inventory and lots

Inventory levels, serial and lot numbers, valuation and traceability, as far as they are maintained in the source system.

Automated
Documents

Open quotes, sales orders and purchase orders as well as posted sales and purchase documents as history.

Automated
Posting history

G/L entries and journals for several fiscal years. We define the scope and depth together – not every piece of history has to go into the new system.

By arrangement
Documents and attachments

Document archives, attachments and file references. The storage target is usually SharePoint or the Business Central attachment system.

By arrangement
Custom program logic

Vendor-specific modules and special logic that has grown over time are rebuilt in Business Central – with standard functionality or as an Extension.

Rebuilt
Forms and reports

Document forms and reports are rebuilt, usually as Word layouts, reports or Power BI analyses.

Rebuilt
Interfaces

POS systems, shops, DATEV, shipping providers, warehouse and production systems are switched over to the Business Central interfaces.

Rebuilt
Standard scope of the migration Scope is defined per project Will be rebuilt in Business Central
Process

Five phases from database analysis to hypercare.

The first step costs nothing and is deliberately technical: only once we have seen your database do we talk about effort and dates.

01
free of charge

Planning and migration check

We analyze a copy of your database, including the table structure and all data volumes. That covers companies, fiscal years, custom fields, and conspicuous duplicates and data gaps. In parallel we define the target environment with you and how far back the history goes. At the end you know what can be migrated and what has to be rebuilt, including cost. The result is ready after one to two weeks.

Database analysis Field inventory Target environment Effort estimate
02

Data mapping

For every source table a rule is created that maps its fields to the matching Business Central table. We take into account the necessary type conversions, default values and lookups. Custom fields and custom tables from the field inventory get their place as well, in the standard or in an extension. Every mapping run is repeatable, so the first version is allowed to have gaps.

Mapping rules Field transformation Extensions
03

Cleanup and test migration

With the first mapping we transfer your real data into a test environment. You check with your own cases whether the assignment is right. Duplicates in customers or items, orphaned records and deactivated accounts show up in the reconciliation log. There is no automatic duplicate check; with targeted value mapping, however, duplicates can already be merged during the transfer. Before the next run you decide whether to clean up, merge or deliberately leave them behind.

Test company Reconciliation log Data cleanup
04

Customizations, interfaces, training

In parallel we build the things that are not data, that is document forms, reports, extensions and interfaces. Your team works in the test environment while the mapping is refined in further runs.

Extensions in AL Interfaces Key user training
05
Cutover date

Go-live and hypercare

The bulk data is long since in the target system. On the cutover date we transfer only the changes since the last run. We check the reconciliation totals once more, then you release. We stay on board until one month after go-live. Questions go directly to the team that built your mapping.

Delta transfer Reconciliation Hypercare
Cutover

Go-live without a big bang

Most guides know two ways to the cutover date. Both hurt.

Big bang over the weekend

Last posting on Friday, data transfer on Saturday and Sunday, hope on Monday. If the import stalls, it stalls with the whole company behind it, and there is no time left for the way back.

Parallel operation with double entry

Both systems run, every posting is entered twice. That means weeks of double work, and in the end nobody knows which state is the right one.

Continuous reconciliation until the cutover date

Our way separates bulk data and changes. We transfer the bulk data to the test environment weeks before the switch; after that DataMigrate Pro only pulls in the delta. Until the cutover date your team works productively exclusively in the legacy system, without double entry. At go-live the latest state is transferred, reconciled and released. For Navision and NAV sources a longer lunch break is usually enough for this; for other systems we plan on a few hours. And if something does come up during the switch, the legacy system keeps running unchanged, because we only read from a copy.

Test and train before you switch

Change management sounds like a workshop, but here it means something tangible. Your key users see their own customers, items and open orders in Business Central long before the cutover date is fixed. They check the cases that really occur in daily work instead of practicing on demo data. Because the reconciliation keeps running, nobody trains on a state that is three weeks old.

Anyone who has already done their work in the new system before go-live enters the Monday after differently. Resistance to a new ERP is rarely aimed at the software, mostly at one’s own uncertainty. That can be reduced in the test company.

As soon as Business Central is live, CloneMyCompany takes over copying individual companies between environments. A fresh copy of production lands in the sandbox, for example for the next training round or a test run before the year-end close.

Cloud migration and GDPR

Whether Business Central runs in-house or in the Microsoft cloud changes little about the course of the migration. The questions of your data protection officer, however, differ considerably.

You install DataMigrate Pro in your own environment, on a server in-house or in your Microsoft tenant. The data takes the direct route from the legacy system to Business Central. Nothing is cached on another server. We only have the access to your database that you expressly grant us.

The same applies to a cloud target. The copy of your database stays with you; only the mapped data goes into your Business Central companies. For our projects, Business Central Cloud is hosted in the Europe West region with a data center in Frankfurt. With on-premises as the target, the process with delta sync remains identical.

How long the copy of your database is kept for the project is up to you. We record the data processing agreement and the agreed deletion period in writing before the first run.

Risks

Typical risks of an ERP migration and how we mitigate them

The risks of an ERP migration have been the same for years. What is new is that most of them can be defused before the cutover date.

Risk
The previous vendor provides no export or ties it to the maintenance contract.
Our answer

We read from a copy of your SQL database, without an export module and without the manufacturer’s approval.

Risk
Data errors and duplicates only come to light after go-live.
Our answer

The first test transfer runs with real data. Whatever stands out in the reconciliation log is clarified before the next run.

Risk
Nobody knows any more what the special logic in the legacy system actually does.
Our answer

The field inventory in the migration check shows every custom field and every custom table. For each customization we clarify together whether the Business Central standard covers it or an extension is needed.

Risk
The cutover weekend falls apart.
Our answer

Delta sync instead of a big bang. Downtime is a matter of hours, and the legacy system stays untouched as a fallback.

Risk
All or nothing with the history.
Our answer

Master data, open entries and inventory come across in full. We transfer G/L entries for two to three fiscal years. Older years remain audit-proof in the legacy system or in an archive company.

Risk
Interfaces are only considered at the end.
Our answer

DATEV, cash registers, shops and shipping providers are on the plan from phase 04, in parallel with the mapping.

Risk
Data gets lost during the move.
Our answer

Every run counts records in source and target and compares the reconciliation totals. If something is missing, you see it in the log before you release.

Risk
The team does not come along.
Our answer

Key users work with their own data in Business Central from the first test transfer. Anyone who has prepared the cutover date themselves will support it.

Duration and cost of an ERP migration

Duration

The migration check is done in one to two weeks. After that the schedule is on the table. How long your project runs is determined by data volume and interfaces. On top of that comes the scope of the customizations that are rebuilt as extensions. Thanks to repeatable runs, the data transfer itself is rarely the bottleneck. As a rule, everything around it takes longer.

If your data comes from a system outside the Dynamics family, plan for a project duration of several months. As a rule it stays below six months. The range arises mainly from how far the data structure of the legacy system is from Business Central.

Cost

Before the migration check you spend not a single euro. At its end there is a concrete cost statement before you sign anything. The data transfer with DataMigrate Pro has a fixed frame, the rest of the project depends on the scope.

As a guide: most migration projects range between €25,000 and €100,000. Depending on scope and complexity it can be below or above.

A customer from the North American gaming industry saved around two thirds of the cost with us, compared with offers in the six-figure range. The case study shows how.

On the other side of the calculation are the costs that can drop away with go-live, provided the history comes along. These include servers, backups and the maintenance contract for the legacy system. In addition, KfW funding under programs 511 and 512 lowers the cost of ERP modernization.

Examples, not a price list

Three projects as an order of magnitude

The following figures are examples from completed projects and not a price quote. What your migration costs is stated at the end of the migration check – until then you pay nothing.

Example

One company, standard scope

from approx. €25,000

One source system, one company, manageable history, no or few custom developments.

  • Migration check free of charge
  • Master data, open entries, inventory
  • G/L entries for two to three fiscal years
  • Delta sync until the cutover date
Example

Large data volumes, a lot of special logic

up to approx. €100,000

Extensive history, many custom fields and grown special logic that has to be rebuilt.

  • Field inventory across the entire legacy system
  • Extensive extension development
  • Several test transfers
  • Hypercare until one month after go-live
Collaboration

Three ways of working together in self, full or hybrid mode

Not every company wants the same from us. Some want the tool, others the result. That is why there are three modes.

Self mode

You migrate, we supply the tool

Your IT team or your current Microsoft partner licenses DataMigrate Pro and controls mapping, test runs and delta sync itself. From us come onboarding, documentation and help when things get stuck. Partners use the tool in their own projects and receive a partner discount on the license.

  • License for DataMigrate Pro
  • Onboarding and documentation
  • Support when things get stuck
  • Partner discount on the license
Hybrid mode

You steer, we back you up

Common with IT departments and partners who want to build the mapping themselves and bring us in for review and cutover. Any split between self and full mode is possible.

  • Review of your mapping
  • Support for the test transfers
  • Cutover together
  • Also together with your partner

If you are still hesitating

We hear three sentences in almost every first conversation.

“We are already well looked after.”

Good. Then ask your partner why the switch has been on the agenda for years and no test company with your data exists yet. If the answer is not convincing, changing partners is less effort than you think.

“We are in the middle of a migration.”

All the better. In most projects the data transfer is right at the end of the list. That is exactly what DataMigrate Pro is made for. Your partner can use the tool themselves or we take over this part of the project.

“We cannot afford that.”

Before the migration check you pay nothing. Afterwards you know what it costs and can compare in peace.

Who is responsible for your migration

Our founders came into migration projects as freelancers where the proverbial cow had to be got off the ice. From this experience came first the approach with continuous data reconciliation, then DataMigrate Pro and, in 2024, IO Integrated GmbH & Co. KG.

References

Examples of our work

Three completed projects, each with starting point, process and result.

NAV 2013 R2 directly to the Business Central cloud

A North American company in the gaming industry moved from NAV 2013 R2 to the Business Central cloud in two weeks – at around a third of the cost of comparable offers.

Read the case study

NAV 2009 directly to Business Central

Vita Tahedl GmbH migrated from NAV 2009 directly to the Business Central cloud. The case study shows project process, stumbling blocks and result.

Read the case study

Designwerk from Business Central v14 to v28

Designwerk, a company of the Volvo Group, moved from Business Central v14 to v28 on-premises with DataMigrate Pro – including code conversion and without downtime for the line.

Read the case study
Further reading

More routes to Business Central.

DataMigrate Pro

The migration engine in detail: mapping, Delta-Sync, logs.

To the product page →

Dynamics NAV and Navision

The automated path for all NAV and Navision versions.

View upgrade paths →

New implementation

Set up Business Central from scratch, without data migration, on a monthly subscription.

View the new implementation →

CloneMyCompany

Copy companies, test them and restore them.

To the product page →

Send us your database, not your requirements specification.

In the migration check we look at a copy of your legacy system and tell you specifically what comes across to Business Central, what has to be created anew and what that costs. Free of charge and with no sales team in between.

Any ERP system on Microsoft SQL Server as a source
No export interface from the previous vendor required
Delta-Sync instead of a switchover weekend
Auditable log for every migration run
FAQ

Frequently asked questions about ERP migration

Our system is not on the list. What now?

The list shows the systems we come across most often. It is not a boundary. What matters is whether the data sits in a Microsoft SQL Server. That applies to a large part of the ERP and merchandise management systems common in the DACH region. Tell us product and version, and we will tell you whether we can read directly.

How can we tell whether our system runs on Microsoft SQL?

There are a few simple indications. Your IT usually talks about an “SQL server” and your backup consists of .bak or .mdf files. References to SQL Server Express in the vendor’s system requirements are also a sign. In case of doubt, the database identifier from the backup is enough for us. The check is part of the free migration check.

Can we keep working normally during the migration?

Yes. We read from a copy of your database; the legacy system stays productive and unchanged. Until the cutover date you keep posting there as usual, and DataMigrate Pro pulls the changes into the test environment.

Do we have to clean up our data before the migration?

Not beforehand, but before the cutover. The first test transfer shows in the reconciliation log where duplicates, orphaned records or deactivated accounts are. You decide what comes along before the next run. There is no automatic duplicate check; with targeted value mapping, however, duplicates can already be merged during the transfer.

What happens to our individual customizations?

They are not carried over, but they are reassessed. In our experience the Business Central standard covers much of what once had to be built individually in the legacy system. What remains we implement as an update-safe extension in AL.

What are the biggest risks in an ERP migration?

A previous vendor who blocks the export, data errors that only show up after go-live, undocumented special logic and a cutover weekend with no way back. How we mitigate each point is in the section “Typical risks” above.

Migration or new implementation, which is better?

New implementation if the legacy system contains hardly any usable data. Migration if customers, items, entries and documents are still needed. We offer both; the decision is made in the migration check based on your database.

Do we need the consent of our current provider for this?

Not for reading your own data. We work on a copy of your database and need neither an export module nor a release from your current maintenance contract. You should of course check what your license and maintenance contract says about termination – we are glad to help with a checklist.

Do you migrate the posting history as well?

Technically yes. It is not always sensible. We often transfer master data, open entries and inventory in full, and the G/L entry history for two to three fiscal years, while the older years remain audit-proof in the legacy system or in an archive company. We decide this together in the migration check.

How long does a change like this take?

The migration check is done in one to two weeks. The project itself depends on the data volume, the number of interfaces and the extent of the customizations. The switch itself is short thanks to Delta-Sync: as a rule, less than a weekend passes between the last posting in the legacy system and the first posting in Business Central.

And payroll?

Business Central does not include German or Austrian payroll accounting as standard. In practice, payroll stays with the existing specialist system or with the tax advisor and is connected via a posting interface. That is how it is handled in most Business Central installations in the DACH region.

We are coming from Dynamics NAV – does the same apply?

For NAV and Navision there is a separate, considerably more automated path: including the transfer of objects and the conversion from C/AL to AL. The details are on the DataMigrate Pro product page; the paths for each source version are listed there in the section on upgrade paths.