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.
If your ERP runs on Microsoft SQL, we can migrate it – to Business Central.
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.
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.
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.
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.
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.
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
Sage 100
Complete business solution for medium-sized companies, grown out of Sage Office Line: financial accounting, inventory management, production and CRM in one Windows client. Customizations are made via the AppDesigner and via partner solutions.
Difference to Business Central
Sage 100 is an installed client system with a DACH focus and its own release cycle. Business Central runs in the browser, is updated by Microsoft twice a year and cleanly separates standard and customization via Extensions.
Why a switch pays off
The best time is the one when you would invest anyway: a version change or a new server. Instead of extending the old architecture, you end up on a platform with Microsoft 365, Power BI and a large app marketplace.
SelectLine
Order processing, inventory management, accounting, payroll and CRM as a modular kit for small and medium-sized businesses. Widely used through a dense specialist dealer network, known for a quick start and inexpensive licenses.
Difference to Business Central
The range of functions ends where things get complex: multi-level manufacturing, project billing, intercompany postings, consolidation, several currencies and languages. Business Central has this as standard.
Why a switch pays off
Usually it is growth: a second location, more companies, foreign customers, a warehouse that needs structure. Added to that is mobile working – in Business Central without the detour via a terminal server.
mesonic WinLine
ERP and CRM suite for small and medium-sized companies: financial accounting, cost accounting, fixed assets, payroll, invoicing, inventory management and production. Licensed in modules, deeply rooted in Austrian and German accounting law.
Difference to Business Central
WinLine comes with its own client and extension technology and its own partner network. Business Central builds on the Microsoft platform: operation in Azure, sign-in via Entra ID, native Office integration, extensions from AppSource.
Why a switch pays off
If IT as a whole is moving towards Microsoft 365, a Microsoft ERP is the shorter route. Payroll usually stays with the specialist – Business Central does not include German or Austrian payroll accounting in the standard.
Infoniqa ONE 200
Business suite for medium-sized companies: financial and payroll accounting, order processing, HR and controlling, multi-company capable and multilingual. Strong in Swiss financial and payroll processes, including swissdec-certified payroll.
Difference to Business Central
The strength lies in accounting; in manufacturing, project execution and supply chain the depth is limited. Business Central covers the operational chain and is localized for more than 100 countries.
Why a switch pays off
Typical for groups with German or international entities that do not want to run two systems. Payroll can stay in the specialist system, the posting data flows into Business Central via an interface.
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
APplus 8
Web-based ERP for mid-sized manufacturing companies: production planning and detailed scheduling, costing, quality assurance, service, CRM as well as connections to CAD and PLM. Designed for series and variant production.
Difference to Business Central
APplus is closer to manufacturing than the Business Central standard, but it is a closed platform with its own customizing model. In Business Central, the manufacturing depth is added through APS and MES apps from AppSource.
Why a switch pays off
Version and platform changes within APplus are projects in themselves. If you are migrating anyway, it makes sense to move the foundation to a platform whose updates and operation Microsoft takes care of.
ams.erp
ERP for one-off, make-to-order and variant production: mechanical and plant engineering, special-purpose machinery, steel construction. Everything revolves around the project – concurrent costing, project controlling, change orders and assembly processing.
Difference to Business Central
ams.erp thinks in terms of the order, Business Central in terms of the document and the posting. Projects, resources and manufacturing are included in the standard; for genuine batch-size-1 depth, Extensions or industry apps are added.
Why a switch pays off
A change is worthwhile when the problem is not the manufacturing logic but operations, client technology and integration: cloud instead of your own servers, analyses in Power BI, documents and communication in Microsoft 365.
oxaion open / easy
ERP for manufacturers and technical service providers. “easy” is the compact variant for smaller operations, “open” the platform-independent Java generation – historically coming from the IBM i world (AS/400), with correspondingly long-lived installations.
Difference to Business Central
A dedicated Java client and a dedicated application server compared with a browser ERP in Azure. Customizations sit in Business Central Extensions written in AL, which withstand the semi-annual updates.
Why a switch pays off
Usually it is about modernizing the platform, especially when IBM i legacy components are still running. With SQL Server installations we access the data directly; with IBM i data we clarify access in the migration check.
Majesty ERP Gen2
Complete ERP system for medical technology and machining: sales, purchasing, production and logistics plus lot and serial number management, release and quality management for regulatory requirements, and a production control station.
Difference to Business Central
Majesty is an industry specialist with regulatory depth for two industries. Business Central is a generalist: batches, serial numbers and traceability in the standard, GxP and validation requirements via certified apps.
Why a switch pays off
Relevant as soon as several locations, foreign subsidiaries or group reporting come into play. The industry requirements are then covered by validatable Extensions, and the base becomes viable internationally.
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
JTL-Wawi
Inventory management for online retail: connection to Amazon, eBay and your own shops, item and stock management, warehouse logistics via JTL-WMS, shipping processing and point of sale. Very strong in fulfillment.
Difference to Business Central
JTL-Wawi is not a financial accounting system – posting runs through the export to DATEV or to the tax advisor. Manufacturing, projects, fixed assets and consolidation are missing. Business Central includes financial accounting in its core.
Why a switch pays off
As soon as sales, accounting and controlling are meant to be one system instead of being reconciled monthly. The channels remain: Business Central connects shops and marketplaces via connectors, including Shopify as standard.
DOMUS ERP & CRM
Software for the real estate industry: rental and condominium management, property accounting, service charge and utility billing, maintenance and CRM. Designed for property managers and portfolio holders.
Difference to Business Central
DOMUS is tailored to the property, Business Central to the company. The real-estate-specific processes are added there via Add-ons; the commercial and group-capable basis comes from the standard.
Why a switch pays off
Of interest above all when property management is only one part of the business – alongside construction, facility services, trade or investments – and group accounting is currently spread across two systems.
eserp
ERP for installation and service companies – security technology, electrical engineering, plant engineering – with integrated document management and CRM, maintenance contracts, asset history and control of the field service.
Difference to Business Central
eserp is tailored to field service work. Business Central has service contracts, service orders and resources as standard; for scheduling and mobile technicians, Dynamics 365 Field Service or industry apps are added.
Why a switch pays off
When service, project business and accounting are to grow together and growth calls for analyses that an industry solution cannot deliver – including Power BI and mobile apps on the same data.
BMD NTCS
Business software with a focus on accounting: bookkeeping, financial statements, cost accounting, payroll, fixed assets and practice organization, supplemented by ERP and CRM modules. Widely used among tax consultancies in Austria.
Difference to Business Central
BMD comes from accounting, Business Central from day-to-day operations: purchasing, warehouse, production, projects, service. BMD plays to its strengths in closing and tax matters.
Why a switch pays off
For companies that have outgrown the accounting perspective. A common target picture: operational processes in Business Central, annual financial statements and tax still with your advisor, connected via an interface.
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
SAP Business One 10.0
SAP’s ERP for smaller companies and subsidiaries: finance, purchasing, sales, warehouse, manufacturing and service in one package. Version 10.0 runs either on Microsoft SQL Server or on SAP HANA.
Difference to Business Central
Business Central is Microsoft-native: working from Outlook, Excel and Teams, Power Platform, operation in Azure, enhancements as AL Extensions via AppSource instead of SDK Add-ons – and two releases per year that Microsoft installs.
Why a switch pays off
Usually a question of licensing and platform direction: if you do not want to follow the HANA route and the rest of your IT is Microsoft, Business Central saves you an entire integration layer. With SQL Server installations we read directly from the database.
Haufe X360 / Acumatica
Cloud ERP from the Haufe Group for mid-sized companies, based on the platform of the US vendor Acumatica and localized for the DACH market: finance, inventory management, CRM, projects, manufacturing, service and e-commerce. Operated in Microsoft Azure.
Difference to Business Central
Architecturally similar in modernity, but a different ecosystem: extensions and partners come from the Acumatica environment. Business Central sits in the Microsoft ecosystem – AppSource, Power Platform, Copilot – with a considerably denser partner network in the DACH region.
Why a switch pays off
This is rarely about missing functions, but about perspective: availability of consultants and developers, choice of apps, depth of integration with Microsoft 365 and a roadmap that fits the rest of your IT.
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.
AutomatedOpen entries
Open customer and vendor entries with due dates, payment terms and application references.
AutomatedInventory and lots
Inventory levels, serial and lot numbers, valuation and traceability, as far as they are maintained in the source system.
AutomatedDocuments
Open quotes, sales orders and purchase orders as well as posted sales and purchase documents as history.
AutomatedPosting 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 arrangementDocuments and attachments
Document archives, attachments and file references. The storage target is usually SharePoint or the Business Central attachment system.
By arrangementCustom 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.
RebuiltForms and reports
Document forms and reports are rebuilt, usually as Word layouts, reports or Power BI analyses.
RebuiltInterfaces
POS systems, shops, DATEV, shipping providers, warehouse and production systems are switched over to the Business Central interfaces.
RebuiltFour 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.
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.
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.
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.
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.
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.
More routes to Business Central.
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 →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.