A purpose-built ETL platform for SAP Business One to Oracle Fusion migration — Financials, AR/AP, Sales, Purchasing, Inventory. HANA and SQL Server B1 supported. Partner add-on inventory, FBDI emitters, 60% lower than partner-led timelines.
SAP Business One served you well from 25 employees to 500. The next stage of growth needs a different platform — and the migration is where most SMBs lose six months they didn't have to.
SAP Business One was built for the SMB segment SAP acquired with TopManage in 2002 — 10 to 500 employees, sub-$500M revenue, single-country or lightly multi-country operations. It does that job well. The problems start when an SMB outgrows the design envelope: a manufacturing roll-up adds three more entities, a private-equity-backed services firm crosses $500M revenue, an IPO process exposes audit gaps, or an M&A event lands the business inside an Oracle Fusion parent. Suddenly the B1 intercompany add-on creaks, multi-GAAP requirements stretch the OJDT/JDT1 model, and the partner-built customisation stack becomes a liability rather than an asset.
Partner-led SAP Business One to Oracle Fusion migrations historically run 6–10 months because the first 3–4 months are spent re-discovering what the current B1 install actually does: which UDFs are used, which add-ons are still licensed, which Crystal Reports the controller actually opens, which Formatted Searches drive month-end. Syntra ETL inverts the sequence. Pre-built extractors for every OCRD/OITM/OJDT/OINV/ORDR table mean week-one extraction. A discovery engine that crawls SBO-COMMON, the UDF/UDO catalog, and the Crystal Report library produces a complete customisation inventory in days.
Whether you're moving a single B1 company to Fusion, consolidating a dozen partner-customised B1 instances acquired through M&A, or running a hybrid where B1 stays for one entity while the rest move to Fusion, the same engine handles it — with the same reconciliation rigor, the same FBDI emission, and the same audit trail.
And how the Syntra ETL platform addresses each one — before they consume your timeline.
SAP Business One's OACT chart of accounts is a single hierarchical structure that collides with Fusion's fixed 6-segment COA. Syntra ETL's COA analyser surfaces which OACT splits drive material reporting, proposes a Fusion-fit segment design, and routes the rest to DFFs or analytical archive.
Discovery crawls SBO-COMMON, the registered add-on catalog, UDF/UDO repository (CUFD, OUDO), and Formatted Search definitions. Every customisation gets a Fusion-equivalence recommendation: native, DFF, Application Composer, OIC, or retire. Typical outcome: 50–70% retired outright.
Some B1 customers run on SAP HANA, others on Microsoft SQL Server, M&A roll-ups often have both. Syntra ETL's extractor abstracts the backend so the FBDI emission pipeline runs identically regardless of source — and supports multi-source orchestration for consolidation projects.
Legacy report inventory, business-value classification, and Fusion-equivalent rebuild plan (OTBI, BI Publisher, FRS, Smart View). 50–70% of partner-built reports are retired during the cleanup; only the critical ones get rebuilt in Fusion-native tooling.
Every Service Layer REST consumer, DI API .NET integration, and B1iF (B1 Integration Framework) flow gets re-pointed to Oracle Integration Cloud (OIC), REST endpoints, or ESS-scheduled file feeds — with cut-over orchestration so upstream/downstream systems never miss a beat.
Decades of OJDT/JDT1 journal lines and OINV/OPCH invoice detail don't all need to land in Fusion. The archival path puts cold periods in queryable cloud storage with auditor-grade access — keeping Fusion lean and Fusion storage costs predictable.
A repeatable, governed workflow built for B1's particular SMB complexity. Typical timeline: 8–14 weeks.
Discovery engine crawls SBO-COMMON, the company schema (HANA or SQL Server), UDF/UDO catalog (CUFD, OUDO), Formatted Search definitions, registered SDK/Service Layer add-ons, and the Crystal Report / B1 Studio report library. Output: a complete customisation inventory, COA usage analysis, and a sized migration assessment.
OACT → COA segment design, OCRD business-partner de-duplication rules (customers + vendors share OCRD in B1, must split in Fusion), DFF routing decisions for retained UDFs, item-class mappings. Reviewed and signed off by finance, sales, and operations leads. Add-on retire/replace decisions logged.
Pre-built SAP B1 extractors pull OCRD, OITM, OACT, OJDT/JDT1, OINV/INV1, OPCH/PCH1, ORDR/RDR1, OPOR/POR1, OWHS, and all dependent tables via Service Layer REST or direct HANA/SQL Server JDBC. Output staged as Parquet with row hashes and partition manifests.
Crosswalks applied, OACT collapsed to Fusion COA, DFFs populated from retained UDFs, FBDI/REST payloads generated, validated against Fusion 26x release templates. Errors surfaced locally with row-level diagnostics — not in a 4-hour ESS job.
FBDI ZIPs submitted to Fusion ESS, monitored to completion, reconciled at row, sum, and hash level. In parallel, critical OTBI and BI Publisher reports rebuilt and validated against Crystal Report / B1 Studio equivalents.
1–2 close cycles in parallel (B1 + Fusion), deltas captured via Service Layer and replayed, reconciled to the cent, sign-off pack issued. SAP Business One moves to archive-only mode; production traffic now flows to Oracle Fusion.
No more bespoke SQL or Service Layer scripts. Configure scope, run, reconcile.
OJDT (Journal Entry headers), JDT1 (Journal Entry lines), OACT (Chart of Accounts), OBPL (Branch), OFPR (Financial Periods). Full account-segment context preserved, period-by-period reconciliation built in for both HANA and SQL Server B1.
OPCH (AP Invoices), PCH1 (AP Invoice lines), ORPC (AP Credit Memos), OVPM (Outgoing Payments), VPM1/VPM2/VPM3/VPM4 (payment detail), OPCH-linked OCRD vendor records. Open-invoice migration with full approval and payment-status context.
OINV (AR Invoices), INV1 (AR Invoice lines), ORIN (AR Credit Memos), ORCT (Incoming Payments), RCT1/RCT2/RCT3/RCT4 (receipt detail), OINV-linked OCRD customer records. Open-invoice aging preserved across migration.
ORDR (Sales Orders) + RDR1, OQUT (Sales Quotations) + QUT1, ODLN (Deliveries) + DLN1, OPOR (Purchase Orders) + POR1, OPDN (Goods Receipt PO) + PDN1. Full document chain preserved for in-flight order migration.
OITM (Item Master), OITB (Item Groups), OWHS (Warehouses), OITW (Item-Warehouse), OINM (Inventory Postings), OIGN/OIGE (Goods Issue/Receipt). Costing methods and warehouse balances migrated with full transaction history.
CUFD (User-Defined Field metadata), OUDO (User-Defined Object metadata), SBO-COMMON catalog, registered SDK/Service Layer add-on inventory. Catalogued for retire/replace decisions and DFF/Application Composer routing in Fusion.
A typical SAP Business One to Oracle Fusion migration runs 8–14 weeks end-to-end for a mid-market SMB carrying 7–10 years of OCRD, OITM, OJDT, and OINV history on either SAP HANA or Microsoft SQL Server B1. Single-pillar projects (Financials-only) close in 5–8 weeks. The acceleration relative to partner-led timelines (typically 6–10 months) comes from pre-built SAP B1 extractors that hit Service Layer REST endpoints or query OCRD/OITM/OJDT/OINV/ORDR/OPCH directly via JDBC, governed crosswalks for B1's flat COA into Fusion's 6-segment chart, and FBDI emitters validated against Oracle Fusion 26x. SMBs running heavily customised partner-built add-ons (SDK-based or Service Layer-based) usually add 1–2 weeks for the add-on inventory and retire/replace decisions.
SAP Business One is designed for SMBs in the 10–500 employee range with revenues typically under $500M. The most common triggers for a SAP Business One to Oracle Fusion migration are: scale outgrowing B1's design envelope (>500 employees, >$500M revenue, multi-entity consolidations getting painful in the B1 intercompany add-on); M&A onto an Oracle Fusion parent; need for sophisticated multi-ledger, multi-GAAP, multi-currency accounting that B1 only partially supports; audit and SOX requirements that come with IPO readiness; or a desire to consolidate dozens of partner-customised B1 instances onto a single Fusion tenant. Fusion's embedded AI/ML, OTBI analytics, and integrated SCM/HCM/EPM story are also pulls for growing SMBs.
Syntra ETL supports SAP Business One to Oracle Fusion migration across all core B1 modules. Financials: General Ledger (OJDT, JDT1), Chart of Accounts (OACT), Banking, Cost Accounting. AR/AP: Sales Invoices (OINV), AR Credit Memos (ORIN), AR Payments (ORCT), AP Invoices (OPCH), AP Credit Memos (ORPC), AP Payments (OVPM). Sales/Purchasing: Sales Orders (ORDR), Sales Quotations (OQUT), Deliveries (ODLN), Purchase Orders (OPOR), Goods Receipt PO (OPDN). Inventory: Items (OITM), Item Groups (OITB), Warehouses (OWHS), Stock Transfers. Production: Bills of Material, light MRP, Work Orders. Both HANA-based B1 and SQL Server-based B1 are supported via Service Layer REST, DI API, or direct database extraction.
Syntra ETL extractors are backend-aware. For SAP HANA-based B1, extracts run via the HANA SQL interface using JDBC against the company schema (e.g. SBODEMOUS), respecting HANA's column-store characteristics for fast OCRD/OITM/OJDT scans. For SQL Server-based B1, extracts run via SQL Server JDBC or ODBC against the same logical company database, with parallelism tuned to SQL Server's row-store engine. The extractor abstracts the difference so business-partner, item, and journal-entry payloads come out structurally identical regardless of backend — and the same FBDI emission pipeline runs against either source. For partner-customised B1 instances that mix HANA and SQL Server across companies, multi-source orchestration is built in.
Most SAP Business One instances have been deployed and customised by SAP Partner Edge partners, and almost every B1 install carries some combination of SDK add-ons (.NET-based), Service Layer add-ons, UDFs (User-Defined Fields), UDOs (User-Defined Objects), Formatted Searches, and Crystal Reports. Syntra ETL's discovery engine crawls the B1 SBO-COMMON catalog, queries the UDF/UDO repository (CUFD, OUDO), enumerates registered add-ons, and inventories every Crystal Report in the report library. Each is classified and given a Fusion-equivalent recommendation: native Fusion functionality, DFF, Application Composer extension, OIC integration flow, OTBI dashboard, or BI Publisher report. Customers typically find 50–70% of partner customisations are redundant under Fusion's native capabilities and can be retired outright.
It adds complexity but Syntra ETL is built for it. Because B1 is sold and implemented through the SAP Partner Edge channel, every customer's B1 deployment reflects a partner's design opinions: their own UDF naming conventions, their own bolt-on add-on architecture, their own Crystal Report style, often their own intercompany or multi-entity hack. Syntra ETL's assessment phase produces a partner-customisation inventory that names every UDF/UDO/add-on/report and proposes a Fusion-mapped disposition. This typically shortens the discovery phase that consultant-led B1 to Fusion projects spend 3–4 months on down to 2–3 weeks. The output is also useful evidence if your B1 partner contract has knowledge-transfer or early-termination clauses tied to migration.
Crystal Reports and (on HANA-based B1) B1 Studio reports don't carry over to Oracle Fusion. The Syntra ETL assessment phase inventories every Crystal Report and B1 Studio report in production use, classifies by business value and frequency of use, and proposes Fusion replacements: OTBI dashboards for ad-hoc analytics, BI Publisher for pixel-perfect operational reports such as customer invoices and purchase orders, Fusion Financial Reporting Studio for management reporting, and Smart View for Excel-tethered finance analysis. About 50–70% of Crystal and B1 Studio reports turn out to be near-duplicates or low-value and get retired outright. The remaining critical reports get rebuilt in Fusion-native tooling during the migration window so go-live includes the reporting layer.
No. Syntra ETL's SAP B1 extractors run as read-only consumers — either via the Service Layer REST API with a dedicated read-only B1 user, or via a granted database role with SELECT on the company schema. Extracts are throttled to avoid contention with B1 online users during business hours and can be scheduled into the nightly B1 batch window or pulled from a HANA replica or SQL Server log-shipped standby to eliminate any production load. No SAP Business One application changes, no B1 client-side modifications, no add-on disabling required during extraction. Sales orders keep getting entered, invoices keep getting posted, the warehouse keeps shipping — migration runs alongside live operations.
Book a 30-minute discovery call. We'll walk through your B1 backend (HANA or SQL Server), modules in use, partner-built add-on profile, and target Fusion design — and give you a concrete 8–14 week timeline and budget before the call ends.