ERP with Salesforce Integration
Salesforce is the dominant CRM platform in the upper Mid-Market and enterprise segments in DACH, particularly in industries with complex selling cycles such as industrial machinery, B2B services, life sciences and software. Once Salesforce is the system of record for sales, the integration with the ERP becomes a board-level operational concern: forecast accuracy, quote-to-cash cycle time, customer master data quality and credit-management discipline all depend on whether the two systems stay aligned. This page describes the integration patterns used in DACH organisations, the native connector landscape, the role of MuleSoft and the GDPR considerations that apply when personal data flows between Salesforce and an ERP running in Germany.
Native connectors
The strongest native Salesforce-ERP connectors are those built or sponsored by the ERP vendor itself. NetSuite, owned by Oracle, has a native Salesforce connector (Oracle NetSuite for Salesforce / Celigo NetSuite-Salesforce) covering account, contact, opportunity, order and invoice synchronisation; the connector is mature and operationally well understood. SAP S/4HANA Cloud has a documented integration with Salesforce via the SAP Sales Cloud and via direct connectors maintained by SAP and partners. Microsoft Dynamics 365 has multiple partner-built Salesforce connectors but the native option is less prominent because Microsoft positions Dynamics 365 Sales as the alternative to Salesforce. For mid-market ERPs in DACH — weclapp, Sage, Xentral — the native Salesforce connector is typically thinner or absent, and integration relies on iPaaS or custom development.
MuleSoft as integration substrate
MuleSoft, acquired by Salesforce in 2018, is positioned as the default iPaaS for Salesforce-centric integration estates. The MuleSoft Anypoint Platform offers pre-built connectors for the major ERPs (SAP, Oracle, NetSuite, Microsoft Dynamics, Workday) and a comprehensive API management layer. For upper-Mid-Market and enterprise organisations standardising on Salesforce, MuleSoft is the typical recommendation from Salesforce itself; the trade-off is licence cost, which scales with API call volume and connector count. Alternative iPaaS platforms — Boomi, Workato, Celigo — cover similar Salesforce-ERP territory and are often chosen by organisations that have an established iPaaS footprint not centred on Salesforce. The integration design itself does not change much by iPaaS vendor; the choice is driven by existing platform commitments and licence economics.
Account, opportunity and order synchronisation
A typical Salesforce-ERP integration covers four object families. Accounts and contacts synchronise bidirectionally with the ERP customer master, with explicit ownership rules: Salesforce typically owns CRM attributes (industry, lead source, account team) while the ERP owns commercial attributes (credit limit, payment terms, VAT identifier, tax classification). Opportunities synchronise from Salesforce to the ERP only when they progress to a defined stage (typically Quote or Closed Won); reverse flow is rare. Quotes and orders may originate in Salesforce CPQ (Configure-Price-Quote) and flow to the ERP for fulfilment; ERP-generated invoices and shipment confirmations flow back into Salesforce for sales visibility. Master-data deduplication is a recurring operational issue and should be addressed with a stable external-key strategy that survives MDM cycles on either side.
GDPR, hosting and compliance
Salesforce data for German customers is hosted in the EU (with the Hyperforce architecture, Salesforce Germany operates a Frankfurt instance), but the ERP integration introduces additional data flows that must be documented in the Article 30 records-of-processing. The lawful basis for processing must be consistent between Salesforce and the ERP; consent withdrawals and right-to-erasure requests must propagate bidirectionally; data-processing agreements (Auftragsverarbeitungsvertrag) must cover both Salesforce and any iPaaS provider in the data path. For organisations operating under specific industry rules — financial services under BAIT, healthcare under the Patientendaten-Schutz-Gesetz — additional contractual and technical safeguards apply, and the integration design should be reviewed by the data protection officer before go-live.
Related Topics
Frequently Asked Questions
Should we use MuleSoft or a cheaper iPaaS?
For organisations already committed to Salesforce as the strategic platform and operating multiple Salesforce-centric integrations, MuleSoft typically pays back through the breadth of pre-built connectors and the alignment with the Salesforce roadmap. For organisations with a single Salesforce-to-one-ERP integration and a tighter budget, Boomi, Workato or Celigo offer comparable capability at lower entry cost. The integration design itself is largely vendor-neutral.
Can Salesforce and an ERP-CRM module run in parallel?
Yes, with explicit ownership rules. The common pattern is that Salesforce owns the sales process from lead through opportunity, and the ERP-CRM (SAP Sales Cloud, Microsoft Dynamics 365 Sales, weclapp CRM) plays a lighter post-sale role around contract administration and after-sales service. Running both as full sales pipelines in parallel produces forecast confusion that the sales operations team will find difficult to reconcile.
Which native ERP-Salesforce connector is the most mature?
NetSuite's Salesforce connector (often deployed via Celigo) is widely regarded as the most mature out-of-the-box option, covering account, contact, opportunity, order and invoice flows with extensive configurability. SAP's Salesforce integration is solid in S/4HANA Cloud with the SAP-published guidance, and a healthy partner ecosystem extends it. For Microsoft Dynamics 365 and German-localised Mittelstand ERPs, partner-built connectors and iPaaS are the typical path.
How are quote-to-cash flows handled with Salesforce CPQ?
Salesforce CPQ holds the quote configuration, product bundles, discounting rules and approval workflow. On quote acceptance, the integration creates a corresponding sales order in the ERP, typically with the configured line items, pricing and customer assignment carried across. The ERP then handles fulfilment, invoicing and revenue recognition; invoice status and payment information flows back to Salesforce for sales visibility. The two systems should agree explicitly on which is authoritative for prices and discounts at the moment of order creation.