SalesforceA won opportunity should become a clean ERP order.
Salesforce knows the deal; the ERP knows the stock, the price, the credit and the invoice. QServices connects them so orders aren't retyped, sellers see what customers owe, and anything that commits stock or money waits for a named person.
Agree this table and which side owns each row before any connector is switched on.
| Salesforce | ERP record | Direction | Matched on |
|---|---|---|---|
| Account | Customer | Both ways | The ERP customer number in an External ID field; the Salesforce ID stored in the ERP |
| Product and price book entries | Items and price lists | ERP to Salesforce | Item number |
| Opportunity or CPQ quote, when won | Sales order | Salesforce to ERP | Opportunity ID on the order |
| Order and Order Products | Order lines | Salesforce to ERP | Line by item and quantity |
| Invoices, payments, shipments | Status on the account and order | ERP to Salesforce | ERP document number |
Based on Salesforce's own integration patterns and the MuleSoft Composer account-to-customer example.
A standard sync between Salesforce and a popular ERP such as NetSuite.
Ready-made mappings and someone else maintaining them.
Coverage for mid-market ERPs like SYSPRO, Epicor or Sage is thin.
Several systems, heavy transformations and an IT team to run it.
Reusable APIs, monitoring and a route for Agentforce to reach the ERP.
MuleSoft starts at $2,000 a month, and its Pre-Commit plan needs $50,000 a year.
Moderate volumes, especially with Business Central.
Microsoft's Salesforce connector supports upsert by External ID and Bulk API 2.0 jobs.
Premium in Power Automate, Standard in Logic Apps, and limited to 900 calls per minute per connection.
Your own rules, an approval queue and an ERP with a good API.
Exactly the flows you need, run in your Azure.
Needs monitoring and an owner after go-live.
Asking Salesforce every few minutes wastes API calls. Its event features push changes instead.
Streams create, update and delete events, with a header showing who made the change so the integration can ignore its own.
Custom events kept 72 hours; 'publish after commit' only fires when the transaction succeeds.
One gRPC connection to subscribe to platform and change events, with acknowledgments.
Salesforce's architects suggest it for anything over about 2,000 records, like nightly price loads.
Salesforce list prices, October 2026. The Flex Credits rate card is revised several times a year.
Agree the object map first, then pick a route: a packaged connector for standard syncs, an integration platform such as MuleSoft for several systems, Power Automate or Logic Apps for moderate volumes, or a custom service with an approval queue.
Not always. It suits multi-system, transformation-heavy work and starts at about $2,000 a month. Many mid-sized companies do well with a connector, Power Automate or a small custom service.
Use events. Change Data Capture and platform events push changes through the Pub/Sub API, which saves API calls; a nightly Bulk API job catches anything missed.
Store the ERP customer number in an External ID field on the account and the Salesforce ID in the ERP. Upserts then match exactly instead of by name.
Actions use Flex Credits at $500 per 100,000, about $0.10 per action. Customer-facing conversations are $2 each, and per-user add-ons start at $125 a month.
It can call ERP APIs registered as External Services or through MuleSoft. We stop it at a draft so a named person approves anything that commits stock or money.
Facts on this page checked on 23 October 2026.
Founder and CEO
Chief Sales Officer
Join our live webinar on Sept 24 and see five
ways to automate meetings, approvals, and
document search with tools already in your
tenant.
