Migrate from SAP Business One to Odoo

What survives the migration

Plain-English breakdown of what we move, what we re-map, and what gets rebuilt in Odoo's framework rather than ported.

Our phased approach

1. 1

   Discovery week

   1 week, fixed-price

   Senior consultant audits your B1 installation — version, modules, customisations, integrations, user count, BOM/routing complexity. Output: written migration plan + fixed-price quote. SDK customisation inventory is the longest line item.

2. 2

   Sandbox migration

   6–10 weeks

   Migration scripts built against B1 SQL (or B1 HANA) databases, run into sandbox Odoo, reconciled to the cent. Your finance team validates partners, items, BOMs, balances, and representative transactions. Iterations expected — B1 data depth means edge cases surface during validation.

3. 3

   Odoo configuration in parallel

   5–8 weeks (overlapping)

   Country localisation, e-invoicing (e.g. ZATCA, FatturaPA, France PPF), tax codes, approval workflows, multi-company setup, integrations. SDK customisations rebuilt in Python during this phase, tested in sandbox.

4. 4

   User training

   2–3 weeks

   Role-based training in sandbox Odoo. B1 users typically have deep platform familiarity; the curve to Odoo is gentle but takes time. Recorded modules per role for ongoing reference. Test drives on production-like data — not toy demos.

5. 5

   Cutover weekend

   1 long weekend

   B1 closes for new transactions Friday evening. Final migration runs Saturday and Sunday (longer than typical because of B1's data volume). Reconciliation Sunday/Monday with finance + auditor sign-off. Tuesday morning: team starts in Odoo.

6. 6

   Parallel-run period

   3–4 weeks

   Both Odoo and B1 accessible. New transactions in Odoo only; B1 read-only. We monitor every flow, fix anything that surfaces, validate at least one month-end close in Odoo before decommissioning B1.

7. 7

   Stabilisation

   60 days post go-live

   On-call engineering for 60 days (longer than other migrations because B1 deployments are typically larger and edge cases take longer to surface). Weekly status. By day 60, finance has closed two month-ends in Odoo, manufacturing has run a full MRP cycle, and we transition to normal support.

Typical timeline

14–24 weeks end-to-end for typical mid-market SAP B1 migrations. Variables: (1) user count and data volume — 100-user B1 with 8 years of history takes 20+ weeks; (2) SDK customisation count — each non-trivial customisation adds 1–2 weeks; (3) manufacturing depth — multi-level BOMs and detailed routings add 2–4 weeks; (4) multi-entity complexity — each additional company adds 1–2 weeks. We commit to a specific timeline at the end of discovery.

Indicative cost

USD 35,000–90,000 fixed-price for end-to-end migration + Odoo go-live for typical mid-market scope. Discovery week: USD 4,000–6,000 fixed. Add USD 8,000–25,000 per substantial SDK customisation rebuild, USD 10,000–30,000 for substantial integration work. Compare to running SAP B1 Professional 50 users + maintenance + partner support: typically USD 80,000–140,000/year. Three-year TCO advantage to Odoo: USD 200,000–400,000.

Risks and mitigations

• Risk: SDK customisation rebuild scope

  Mitigation: SDK customisations are the longest-tail risk. Discovery week explicitly inventories each customisation: what it does, who uses it, what business outcome it produces. Most customisations end up classified as 'Odoo default covers this' (40–60%) or 'rebuild as 50% smaller Python module' (30–40%). Pure ports are rare.

• Risk: Hidden SBO Hana dependencies

  Mitigation: B1 HANA installations sometimes have Hana-specific stored procedures or calculation views invoked by integrations. We do a HANA dependency audit during discovery; surface every non-standard object before sandbox phase. Resolves the 'integration X mysteriously broken' day-of-cutover scenario.

• Risk: Multi-company inter-company elimination logic

  Mitigation: B1 multi-company customers often have group reporting structures with specific elimination rules. We design Odoo's multi-company hierarchy and elimination logic during configuration phase with your finance team; validate against historical B1 consolidations before cutover.

• Risk: Auditor reluctance on cutover timing

  Mitigation: SAP B1 customers usually have established audit relationships. Discovery week includes a call with your auditor on cutover timing — Q1 post year-end is preferred, mid-quarter is workable, Q4 is risky. We've migrated B1 customers audited by Big 4 and large mid-tier firms without findings.

• Risk: Manufacturing cutover during active production

  Mitigation: Manufacturers can't shut down for cutover weekend. We design a phased manufacturing cutover — open work orders complete in B1, new work orders start in Odoo from a specific date. Parallel period covers the overlap. Production team's input on timing is critical.

• Risk: Approval chain continuity

  Mitigation: B1 approval procedures often encode multi-level company hierarchy. We design Odoo's approval workflows in discovery with your CFO; map each B1 approval rule explicitly. Pending B1 approvals at cutover are migrated as Odoo approvals in flight.

• Risk: Crystal Reports nobody documented

  Mitigation: Standard B1 installation has 30–80 Crystal Reports. Most aren't used regularly but somebody uses each one. We require a report inventory during discovery: per role, which reports run weekly. Anything load-bearing rebuilt as Odoo report — usually 10–15 reports, not 30–80.

• Risk: Sage SAP-specific integrations (Boyum, B1iF, B1if)

  Mitigation: Third-party B1 add-ons (Boyum B1UP, B1 Print and Delivery, etc.) audited during discovery. Most have direct Odoo equivalents; some are replaced with simpler custom solutions. Boyum scripting specifically doesn't port — those workflows get rebuilt.

Who should migrate

Mid-market businesses (50–500 users) on SAP Business One Professional, where the cost-to-value ratio has tipped. Particularly: cost-sensitive manufacturers comfortable that Odoo's MRP II matches their needs; multi-entity groups where multi-company consolidation is core; businesses outside the SAP partner-deep regions (DACH, Italy) where the SAP ecosystem advantage is less relevant; businesses without a 3–5 year path to S/4HANA. Not a fit: businesses with hard financial-controls regulatory requirements where SAP's audit framework is contractually required, or businesses planning to grow into S/4HANA.