Oracle NetSuite and SAP Business ByDesign are two of the few genuinely multi-tenant cloud ERPs that have served the upper mid-market for more than a decade. NetSuite, acquired by Oracle in 2016, is the larger of the two by installed base and the more aggressive on global multi-subsidiary, multi-currency and OneWorld international consolidation. ByDesign is SAP's older but mature multi-tenant cloud product, with a stronger German Mid-Market orientation and out-of-the-box GoBD and DATEV connectivity. This comparison frames where each genuinely fits in a DACH selection, with practical attention to roadmap signals from both vendors — particularly SAP's evolving focus on S/4HANA Cloud Public Edition as the strategic mid-market product.
Overall positioning
Oracle NetSuite: launched in 1998 as NetLedger, now operated as a wholly owned Oracle product with over 40,000 customers globally and a growing DACH installed base. Sold and implemented through a partner network combining Oracle-direct, NetSuite Solution Providers and Big-4-style consultancies (Accenture, Cognizant, regional specialists such as Aaztec and OPEN ICT). Strong fit for fast-scaling companies, multi-country subsidiaries and US-headquartered groups operating in DACH. SAP Business ByDesign: launched in 2007 as SAP's purpose-built multi-tenant cloud ERP, with roughly 4,000 customers worldwide and a meaningful DACH share concentrated in German Mid-Market operators between 100 and 1,000 employees. Sold through SAP and a focused DACH partner network including All for One, FIS and itelligence-derived units of NTT DATA Business Solutions. Both products target similar size brackets, but the buyer mind-set differs: NetSuite attracts globalising scale-ups and multi-country operators; ByDesign attracts German-headquartered Mid-Market companies that want SAP brand assurance with cloud delivery and out-of-the-box German compliance.
Functional comparison
Both products cover the full mid-market ERP scope as native multi-tenant SaaS. NetSuite strengths: OneWorld for multi-subsidiary, multi-currency and multi-legislation deployments, considered an industry benchmark for global consolidation; the SuiteCommerce stack for B2B and B2C e-commerce; a wide ISV ecosystem via SuiteApp marketplace; and a US-centric reporting heritage that suits US-parented groups. ByDesign strengths: German localisation that handles GoBD natively, native DATEV connectivity used heavily by Steuerberater, native ZUGFeRD and XRechnung; strong project-based accounting and services functionality inherited from SAP's Business One and PSA lineage; tight integration with the wider SAP ecosystem via SAP Cloud Platform Integration. Where parity exists: core financials, multi-currency, multi-entity consolidation at mid-market depth, EU VAT including OSS/IOSS, modern REST APIs, mobile UI. The differentiation centres on geography and process orientation: NetSuite is the stronger choice for multi-country, US-flavoured operations; ByDesign is the stronger choice for German-only or DACH-only operations with deep Steuerberater involvement.
Architecture and deployment
NetSuite architecture: true multi-tenant SaaS on Oracle Cloud Infrastructure, with two major releases per year and a robust SuiteCloud development platform (SuiteScript in JavaScript, SuiteFlow visual workflow, SuiteAnalytics). Customisation is well-supported but disciplined: changes survive upgrades by design. Integration through REST and SOAP APIs and the SuiteCloud Connect framework. SAP Business ByDesign architecture: also true multi-tenant SaaS, on SAP's own infrastructure, with quarterly upgrades. Extensibility through the SAP Cloud Applications Studio (key-user and PDI partner extensions) and integration via SAP Cloud Platform Integration. Roadmap reality: NetSuite continues to receive aggressive product investment and clear strategic prioritisation from Oracle. ByDesign development has slowed in recent years as SAP focuses on S/4HANA Cloud Public Edition as the strategic mid-market product. ByDesign remains supported, but prospects should factor the slower roadmap into a five- to seven-year horizon. Customisation discipline: both reward staying close to standard; SuiteScript customisations and ByDesign PDI extensions both impose meaningful discipline at upgrade time.
Selection considerations
Choose NetSuite if: you operate across multiple countries with multi-currency consolidation as a core requirement; you are a US-parented group rolling out a global ERP; you are a fast-scaling company anticipating international expansion; or you need a mature SaaS commerce stack alongside ERP. Choose SAP Business ByDesign if: you are a German or DACH-headquartered Mid-Market operator with strong Steuerberater involvement; you want GoBD, DATEV, ZUGFeRD and XRechnung out of the box; you anticipate consolidation into an SAP parent; or your scope is dominated by services and DACH-centric financials. Implementation effort: a 200-user NetSuite project runs 6 to 12 months and EUR 400,000 to 1.2 million all-in; ByDesign at comparable scope is similar, often slightly faster for German-only deployments. Partner network: NetSuite's DACH network is growing and now capable for German-only deployments; ByDesign's DACH base is smaller but experienced. Roadmap: factor SAP's strategic focus on S/4HANA Cloud Public Edition into any ByDesign selection — supported but no longer the SAP mid-market spearhead.
What are the main differences between the two systems?
The key differences in architecture, industry fit, customization depth and licensing model are compared in the main section of this page. The exact configuration depends on the industry, company size class and customization depth of the specific ERP setup. A well-founded answer always requires a look at the individual business processes and the strategic IT roadmap.
Which system is better suited for the mid-market?
Mid-market suitability differs by company size (SMEs with 50 employees, classic mid-market with 250 employees, upper mid-market with 1,000+). Suitability per size class is presented in the main section — see also ERP for the mid-market. The exact configuration depends on the industry, company size class and customization depth of the specific ERP setup.
How long does a migration between the two systems take?
ERP migrations typically take 6–18 months. With significantly different data models, it can take longer. Read more under ERP implementation.
What do existing customers say about the two systems?
The Trovarit ERP study and vendor references provide qualitative data. You will find our own reviews on the vendor pages above. The exact configuration depends on the industry, company size class and customization depth of the specific ERP setup.
What customization options do the two systems offer?
Customization depth varies greatly — cloud solutions are usually more restricted, while on-premise systems can often be fully adapted at source-code level. See the main comparison section for details. The exact configuration depends on the industry, company size class and customization depth of the specific ERP setup.
