When your legacy system ends
Support and product deadlines have already been set for several widely used ERP systems. These dates belong in your migration planning.
| Legacy system | Status | Date |
|---|---|---|
| Microsoft Dynamics NAV 2017 | end of extended support | 12 January 2027 |
| Microsoft Dynamics NAV 2018 | end of extended support | 12 January 2028 |
| Sage 100 (desktop) | no further updates | since 1 January 2025 |
| abas ERP 20 | discontinued | since 31 December 2024 |
| SAP Business ByDesign | no longer sold to new customers | since 20 April 2026 |
| SAP ECC | end of mainstream maintenance | 31 December 2027 |
Whatever the system, the German e-invoicing mandate applies: from 1 January 2027 companies with prior-year revenue above €800,000 must issue e-invoices, from 1 January 2028 all companies.
Which system are you replacing?
Microsoft Dynamics
In 2026, we replaced Rauschenberger’s Dynamics CRM with Odoo 19 for seven entities in Germany and Spain. Scripts transferred all contacts and more than 200 email templates. Outlook remains in use and is connected to Odoo. The Rauschenberger case study describes the project.
For Dynamics NAV and Business Central, we use the same method: scripted transfer of master data, open items and templates, DATEV export and a test migration before cutover. We do not currently have a published NAV or Business Central replacement reference. The guide Odoo vs. Dynamics 365 Business Central compares the systems.
Sage and Lexware
The desktop version of Sage 100 has received no updates since 1 January 2025. Accounting often sits in one system and orders and inventory in another. We move customers, suppliers, products and open items and set up the DATEV export. More in the guides Odoo vs. Lexware and Odoo vs. Sage.
Xentral and weclapp
Maintaining the online shop, inventory and accounting separately creates extra work for retailers. During migration, we transfer products, stock and customers and connect the shop to Odoo. Prantl shows how a store checkout and online shop can share one product catalogue. For a system comparison, see Odoo vs. Xentral.
Excel and home-grown tools
For orders, prices and stock held in Excel, we first establish which spreadsheets are authoritative. Duplicate records are cleaned up before the data is imported into Odoo.
abas and proALPHA
For abas, proALPHA and other manufacturing-focused systems, a preliminary assessment examines bills of materials, routings and product variants. This establishes what standard Odoo can handle. The manufacturing page explains the standard scope and possible development work.
SAP Business One, Business ByDesign and SAP ECC
We cannot currently provide a published SAP replacement reference. The migration check reviews your requirements and gives you a written assessment. For subsidiaries, Odoo can also act as a second-tier ERP alongside the parent’s SAP system. The interface overview explains how we classify these integrations.
How the migration works
- Inventory: We review the data, functions and interfaces in your existing system and list what needs to be transferred, cleaned up or retired.
- Mapping: We map legacy fields to their Odoo equivalents. Where there is no match, we agree with you whether a custom field is needed.
- Test migration: Data is first imported into a test environment. Your accounting team checks balances and open items, while sales reviews customer records and templates.
- Cutover: We take the final state from the old system and switch over. The old system stays readable for the statutory retention period; whether an archive export is enough, we agree with your tax adviser.
- Post-go-live support: After go-live we support you for 30, 60 or 90 days, depending on the package.
How long a migration takes
Migrations use the same packages and timeframes as our other implementations.
| Starting point | Package | Time to go-live |
|---|---|---|
| One area, for example inventory out of Excel | Quick Start | 4–6 weeks |
| One company, 4–8 modules, one interface | Implementation | 8–16 weeks |
| Company group with several legal entities | Transformation | 3–9 months |
At Rauschenberger, CRM, sales and invoicing for seven entities went live after three months. Accounting is being implemented in a second phase.
Tender and requirements document
We respond to your requirements document item by item, identifying standard functionality, configuration or development for each requirement. For tenders, we follow your response format and deadlines. The quote lists Enterprise licence costs separately over five years.
Management can plan the move before legacy support ends. Finance receives the migration’s fixed price and five years of licence costs together. IT can verify the migration before cutover, with access to the legacy system retained for the statutory period.
Migration check
Tell us your current system, the number of legal entities and your preferred cutover date. We will reply within one business day with a proposed next step. See the pricing page for packages and prices.