Salesforce + SAP Business One Integration
Connect Salesforce to SAP Business One so sales can quote and close in the CRM while stock, pricing, and financials stay authoritative in the ERP — without anyone re-entering an order.
What Does This Integration Do?
Salesforce is where deals are worked; SAP Business One is where stock, pricing, and financials are authoritative. Without a link, reps quote from yesterday's price list and someone in the back office retypes every closed-won opportunity into B1 as a sales order.
This integration keeps accounts and business partners aligned, posts won Salesforce opportunities into SAP Business One as sales orders, and returns stock levels, pricing, delivery progress, and invoice and payment data to Salesforce so sales can answer customer questions without opening the ERP.
What Syncs, and Which Way
Most Salesforce + SAP B1 projects sync the same core objects. The ERP stays system of record for anything financial — that's the usual starting rule.
Accounts & Business Partners
Both directions
Matched on a shared reference, with SAP B1 as system of record
Items & Stock
SAP B1 → Salesforce
Item master, price lists, and available quantities visible to reps
Sales Orders
Salesforce → SAP B1
Closed-won opportunities and approved quotes posted as B1 sales orders
Invoices & Payments
SAP B1 → Salesforce
Invoice, balance, and payment status on the account record
Delivery Status
SAP B1 → Salesforce
Fulfilment progress so sales answers without asking operations
Credit Limits
SAP B1 → Salesforce
Credit blocks flagged before a rep promises terms the ERP won't allow
How We Build It
SAP B1 exposes the Service Layer and DI API; Salesforce exposes REST, Bulk, and Platform Events. A middleware tier between them is almost always the right architecture.
| Approach | What it is | Best for | Watch out for |
|---|---|---|---|
| SAP B1 Service Layer | REST/OData API exposing B1 business objects | Modern builds, higher volumes, real-time posting | HANA-first (SQL from v10); needs development skill |
| SAP B1 DI API | COM-based API for reading and writing B1 objects | SQL deployments and legacy environments | Older technology; slower at scale |
| Salesforce REST & Platform Events | Record-level access plus event-driven publishing | Triggering on close, pushing status back to the account | Daily API call limits vary by Salesforce edition |
| Custom middleware | Purpose-built orchestration (n8n, Make, or code) between both | Queueing, retries, transformation, and error visibility | Needs a partner who can maintain it (that's us) |
Why middleware rather than a direct link: ERP writes fail for real business reasons — a credit block, a closed posting period, an item that no longer exists. A middleware tier lets those failures queue, retry, and surface as alerts instead of disappearing silently between two systems.
How Much Does It Cost?
A Salesforce + SAP Business One integration typically costs between $8,000 and $28,000 to implement, depending on object count, direction, and B1 deployment.
| Approach | Implementation | Ongoing |
|---|---|---|
| One-way opportunities to SAP B1 sales orders | $8,000 – $13,000 | Support retainer only |
| Bi-directional with stock, pricing & invoice status | $13,000 – $21,000 | Support retainer, platform fee if an iPaaS is used |
| Multi-company or on-premise B1 build | $20,000 – $28,000+ | Support retainer only, no platform fee |
The number moves most on object count, whether records sync one-way or bi-directionally, and whether SAP B1 is cloud or on-premise (on-premise needs a secure agent or VPN, which we handle as part of the build). We quote a fixed price after a scoping call.
How Long Does It Take?
Master data is the schedule driver — if accounts and items don't share a reference across the two systems, that reconciliation happens before anything syncs.
Standard CRM to ERP flow
Accounts, items, and won opportunities creating B1 sales orders.
Bi-directional / on-premise build
Two-way master data, stock and pricing back, secure connectivity, multi-company.
What Does Our Integration Process Look Like?
Every engagement follows the same five stages — you get a fixed-price scope and a mapping sheet you sign off before we build.
Discover
We map your Salesforce objects, SAP B1 version and deployment, and volumes.
Map
We document every field, direction, transformation, and error rule before building.
Build
We implement against a B1 test company and a Salesforce sandbox.
Test
We run real transactions — credit blocks, closed periods, retries, and duplicates.
Support
We monitor after go-live, with alerting, logging, and a named contact.
Frequently Asked Questions
Through SAP B1's Service Layer (or the DI API on older SQL deployments) on one side, and Salesforce's REST and Platform Event APIs on the other, with a middleware layer handling transformation, queueing, and retries.
Yes. On-premise B1 is reached through a secure agent, VPN, or an exposed Service Layer endpoint. We handle that network setup as part of the build.
SAP B1, in almost every case — credit limits and financial history live there. Sales still creates prospects in Salesforce, promoted to a B1 business partner at a defined point.
Yes. Item master, price lists, and available quantities are pushed into Salesforce on a schedule, so reps quote from current data rather than a stale export.
Most projects run $8,000 to $28,000 depending on object count, direction, and deployment. See the cost table above for a full breakdown.
Yes. Rescue work is a large share of our practice, and we run a dedicated SAP Business One integration practice alongside our CRM work.
Ready to Connect SAP Business One to Salesforce?
Every won deal retyped into the ERP is a delayed order and a stock promise nobody checked. A scoped integration removes that work permanently — and you'll know the exact cost before we start.