Salesforce ↔ ERP Integration (SAP, NetSuite, Oracle): The Honest Playbook
Every Salesforce-to-ERP integration eventually becomes the most fragile part of your stack. Here is the honest playbook to design it correctly the first time, and to fix the one you inherited.
The Salesforce-to-ERP integration is the most-underestimated and most-fragile piece of every mid-market stack. On paper, it is "just an integration." In practice, it is where sales, finance, supply chain and IT all meet, disagree, and blame each other. Here is the honest playbook to design one correctly the first time, and to rescue the one you already have.
The 3 Integration Layers You Cannot Skip
- Master data: customers, products, price books. This is where 80% of pain lives.
- Transactional data: quotes, orders, invoices, payments. High-volume, deadline-sensitive.
- Analytical data: revenue, backlog, forecast rollups. Read-only, less time-sensitive.
The Golden Rule: One Master Per Field
Every field must have one master system. Not "usually," not "when synced", always. Typical assignment:
- Customer legal name, tax ID, credit terms → ERP owns.
- Sales rep assignment, opportunity stage, activity history → Salesforce owns.
- Product SKU, list price, tax code → ERP owns.
- Product marketing description, images → Salesforce owns.
Any field with no clear owner becomes a data-quality war. Kill the ambiguity on day one.
Real-Time vs Batch: The Cheat Sheet
- Real-time (API): quote → order push, order status → Salesforce updates.
- Micro-batch (5–15 min): pricing updates, inventory availability.
- Nightly batch: financial rollups, closed invoices, aged AR.
Do not real-time what does not need it, you pay for the reliability engineering forever.
MuleSoft vs iPaaS vs Custom
- MuleSoft: the Salesforce-native answer. Best when you already own it or need reusable APIs across many systems.
- iPaaS (Boomi, Workato, Celigo): lower entry cost, faster time-to-value for a single integration.
- Custom (Apex + REST/SOAP): viable for simple stable integrations. Becomes a maintenance nightmare at scale.
Failure Modes to Design Around
- ERP down for 15 minutes → your Salesforce orders queue and retry, not fail.
- Bad data from Salesforce → the ERP quarantines instead of crashing.
- Duplicate customer created in both systems → matching rule reconciles, not multiplies.
- Timezone drift on order dates → normalize to UTC everywhere.
Regional Notes
- France, Germany: mandatory e-invoicing (Factur-X, ZUGFeRD) changes ERP integration scope. See France, Germany.
- Belgium, Luxembourg: Peppol invoicing is standard. See Belgium, Luxembourg.
- Switzerland: multi-canton VAT rules. See Switzerland.
- US & Canada: sales tax integration (Avalara, Vertex) is separate but adjacent. See US, Canada.
Frequently Asked Questions
How long does a Salesforce ↔ ERP integration take?
Well-scoped: 3–5 months. Enterprise, complex master-data: 9–18 months.
How much does it cost?
Focused integration: $80k–$250k. Enterprise: $250k–$1M+. MuleSoft licenses add real money on top.
Can we integrate without MuleSoft?
Yes, many mid-market integrations use Boomi or Workato successfully.
What is the biggest mistake?
Trying to sync every field. Sync the 30 that matter; leave the rest.
Get a Fixed-Price Integration Assessment
Our integration service starts with a two-week discovery that returns a fixed-price integration plan. Book a 30-minute call.
If this sounds like your CRM, let's look at it together.
Thirty minutes, no deck, no pitch. You leave with a diagnosis either way.