Migrating SAP Business ByDesign to Odoo – Your Plan After the ByDesign Wind-Down
SAP made it clear in 2024 that Business ByDesign is no longer a strategic investment. The product still receives maintenance and support, but no substantive new development. Existing customers – about 3,000 worldwide, with a meaningful number in the German Mittelstand – face a strategic decision about how to proceed in 2026 and beyond.
SAP recommends ByDesign customers move to SAP S/4HANA Cloud. That is the technically natural path, but not economically attractive for every customer. S/4HANA Cloud is materially more expensive than ByDesign, has higher implementation requirements, and primarily targets larger organisations. For many ByDesign customers, Odoo Enterprise is the better alternative – functionally comparable, materially cheaper on licensing, and with an established migration path.
Quick verdict: ByDesign customers with fewer than 250 employees and no strategic commitment to SAP S/4HANA roadmaps should evaluate Odoo Enterprise as a serious alternative. The migration is methodically proven and typically 30 to 50 percent cheaper than a move to S/4HANA Cloud. Running ByDesign for another two or three years buys time but does not solve the problem.
What does the ByDesign wind-down actually mean?
SAP has not announced a shutdown of ByDesign. The product continues to receive maintenance, security updates, and compatibility patches – but no feature development, no investment in new modules, no roadmap that can compete with S/4HANA Cloud. Concretely:
- Your ByDesign installation continues to run technically, likely for many years to come
- New requirements (AI features, new localisations, new compliance features) will not be implemented in ByDesign
- The partner ecosystem is shrinking as consultancies redirect investments toward S/4HANA Cloud
- The talent pool for ByDesign specialists is thinning – experienced consultants migrate to S/4HANA
- Medium-term, ByDesign becomes an end-of-life platform – the only question is when SAP communicates that officially
Waiting in 2026 for SAP to make a clearer statement risks being forced into a time-pressured migration two or three years from now.
The three migration paths
Path 1: SAP S/4HANA Cloud, Public Edition
SAP's official recommendation. Advantages: stays inside the SAP ecosystem, existing SAP knowledge in team and partners remains usable, data migration from ByDesign is supported by SAP.
Disadvantages: licensing typically 50 to 100 percent higher than ByDesign, implementation effort materially higher (S/4HANA Cloud requires a RISE with SAP commitment with longer contract terms), feature set is optimised primarily for larger companies. For ByDesign customers with 50 to 200 employees, often oversized.
Path 2: SAP Business One
In justified cases a step backward: B1 is materially cheaper than S/4HANA Cloud but does not fully cover ByDesign's feature breadth. Often the choice for organisations that want to retain the SAP brand while stepping back on TCO.
Path 3: Odoo Enterprise
Functionally comparable to ByDesign, materially cheaper on licensing, implementation in a clear mid-market-friendly cost range. For most ByDesign customers with fewer than 250 employees, the economically most attractive alternative.
Why Odoo is a genuine ByDesign alternative
ByDesign covers CRM, sales, purchasing, inventory, manufacturing, accounting, and HR – all in one integrated cloud platform with German localisation. Odoo Enterprise covers the same functional area plus integrated webshop, helpdesk, marketing automation, and project management. The functional comparison:
| Function area | SAP Business ByDesign | Odoo Enterprise |
|---|---|---|
| German accounting (GoBD, DATEV) | ✓ | ✓ |
| CRM and sales | ✓ | ✓ extended |
| Inventory and logistics | ✓ | ✓ extended |
| Manufacturing / MRP | ✓ | ✓ |
| HR / employee records | ✓ | ✓ |
| Webshop | ✗ | ✓ |
| Marketing automation | ✗ | ✓ |
| Helpdesk / service desk | limited | ✓ |
| Project management | basic | ✓ |
| AI features | sparse | ✓ |
Functionally, Odoo wins this comparison – not by going deeper everywhere, but by including additional modules at no extra cost.
Migration methodology
Migrations from ByDesign follow a consistent methodology in our practice:
1. Data extraction via ByDesign Web Services
ByDesign offers a comprehensive SOAP and OData API. We extract:
- Master data: customers, suppliers, items, price lists, employees, accounts
- Transactional data: open orders, inventory, open items, accounting data for the past 24 months
- Configuration: tax rules, posting logic, document number ranges, workflows
- Attachments and documents: PDF scans, images, contracts
2. Mapping into Odoo's data model
ByDesign and Odoo differ structurally – ByDesign uses SAP's business-object model, Odoo its own module-based data model. We translate:
- Business partner IDs: ByDesign business partners split into Odoo customers, suppliers, or both
- Charts of accounts: transferred to SKR03 or SKR04, with mapping of ByDesign-specific accounts
- Tax rules: translation of ByDesign tax codes into Odoo tax rules
- BOMs: ByDesign material masters become Odoo products and BOMs
3. Customisation evaluation
ByDesign customers often have customisations implemented through SAP Cloud Applications Studio (CAS) – custom fields, workflows, reports. We assess each:
- Covered by Odoo standard? → no reimplementation needed
- Business-process critical? → reimplement in Odoo (Python, XML, Studio)
- Rarely used? → cut for platform hygiene
4. Test run and balance reconciliation
Full test migration into a sandbox. Balance reconciliation against ByDesign reports, sample-based master-data verification, end-to-end testing of key business processes by the customer team.
5. Cutover and hypercare
Clean cutover (quarter- or year-end). 60 days of intensive post-go-live support.
Typical project length: 16 to 28 weeks for a mid-market ByDesign setup.
Cost comparison
| Path | Licensing / year (50 users) | Implementation | 3-year TCO |
|---|---|---|---|
| ByDesign continued | ~€60,000–90,000 | – | €180,000–270,000 |
| S/4HANA Cloud | ~€90,000–150,000 | €100,000–250,000 | €370,000–700,000 |
| SAP Business One | ~€36,000–55,000 | €50,000–120,000 | €158,000–285,000 |
| Odoo Enterprise | ~€18,000–30,000 | €35,000–80,000 | €89,000–170,000 |
The numbers make the economic argument clear: at a 50-person setup, migrating to Odoo saves €200,000 to €500,000 over three years compared to S/4HANA Cloud.
Risks and how we contain them
Risk: data loss during migration Mitigations: complete test migration in a sandbox, multiple balance reconciliations, parallel run of two to four weeks, read-only access to ByDesign for 12 months after cutover.
Risk: functional gaps between ByDesign and Odoo Mitigations: detailed functional gap analysis before implementation start, clear list of what is transferred, reconfigured, or cut.
Risk: user adoption Mitigations: pre-go-live training, power-user programme per department, hypercare with short response times in the first 60 days.
Risk: business interruption Mitigations: cutover at fiscal year-end, intensive preparation of the cutover weekend, contingency plan with rollback path.
Final take
The ByDesign wind-down is a strategic prompt, not an emergency. You have time to make a sound decision – but should use that time for the decision itself, not for postponing it.
Odoo Enterprise is, for most ByDesign customers in the German Mittelstand, the economically most attractive alternative. We have run the migration multiple times, know the typical pitfalls, and deliver a transparent effort estimate.