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

If your ERP runs on Microsoft SQL, we can migrate it – to Business Central.

If your ERP sits on a Microsoft SQL Server, we can transfer the data – Sage, SelectLine, APplus, SAP Business One and many others. DataMigrate Pro reads the source database at table level, regardless of which vendor sits on top of it. On this page: 14 systems from the DACH market, what they can do, where Business Central works differently and when a switch pays off.

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

We read directly from your SQL database.

Most ERP changeovers do not fail because of the new system, but because of the data transfer: CSV exports, missing interfaces, a legacy provider that does not cooperate. We take the other route and read directly where the data is stored.

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, repeatable and can be run as often as you like – every run is logged and verifiable.

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.

The program logic, forms, reports and vendor-specific extensions of your legacy system are not carried over; they are created anew in Business Central. Business Central already covers much of this as standard; for the rest we write an Extension that keeps working after the semi-annual Microsoft updates. The result of the migration check shows which of your customizations belongs where.

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

Complete commercial systems for mid-sized companies.

Financial accounting, inventory management and invoicing from one Windows client. Solidly built, but grown in the DACH region and 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.

Specialists for manufacturing and make-to-order production. Deep in their field – but technically each one a separate platform with its own lifecycle.

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.

Very good within their segment, but rarely a complete ERP. In most cases a second system runs alongside – and that is exactly where the migration starts.

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 on a par. Here the ecosystem and the proximity to the rest of your IT decide, not the feature set.

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

Four phases up to the Cutover.

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

Migration check

We analyze a copy of your database: table structure, data volumes, companies, fiscal years, individual fields. The result is a reliable statement about what can be migrated, what has to be rebuilt and what that costs.

Database analysis Field inventory Effort estimate
02

Mapping and first test transfer

Source tables are mapped to Business Central objects and transferred to a test environment. You see your real data in the new system, not demo data – and you check against your own cases whether the mapping is correct.

Mapping rules Test company Reconciliation log
03

Customizations, interfaces, training

In parallel, the things that are not data take shape: document forms, reports, Extensions and interfaces. Your team works in the test environment while the mapping is brought up to date in further runs.

Extensions in AL Interfaces Key user training
04
Cutover date

Cutover with Delta-Sync

The bulk data is already in the target system. For the switchover we transfer only the changes since the last run, check the reconciliation totals and release. After that we support the first posting periods in live operation.

Delta transfer Reconciliation Hypercare
FAQ

FAQ – frequently asked questions

Our system is not on the list. What now?

The list shows the systems we encounter most often – it is not a restriction. What matters is whether the data is held in a Microsoft SQL Server. That applies to a large part of the ERP and merchandise management systems in use in the DACH region. Tell us the product and version and we will tell you whether we can read it directly.

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

Two simple indications: your IT department talks about a “SQL Server”, or your backup consists of .bak or .mdf files. References to SQL Server Express in the manufacturer’s system requirements are another sign. If in doubt, the database identifier from the backup is enough for us – the check is part of the free migration check.

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.

What happens to our individual customizations?

They are not carried over, they are re-evaluated. Experience shows that the Business Central standard covers a considerable part of what once had to be built individually in the legacy system. Whatever remains, we implement as an Extension in AL – update-safe with regard to the half-yearly Microsoft releases.

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.

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