Salesforce
Integration Services
Connect Salesforce to your ERP, finance, commerce and communication systems, so data moves once and every team works from the same record.
List the systems and the data that has to move, and we'll recommend an integration pattern.
Salesforce integration services connect Salesforce with other systems, such as ERP, finance, e-commerce, telephony and data warehouses, so records and events flow between them without re-keying. The work covers choosing an integration pattern, building it with Salesforce APIs or middleware such as MuleSoft, handling errors and security, and monitoring it after launch.
The practice
Integrations built to keep running
Techila Global Services is a Salesforce Summit Partner. We design and build integrations between Salesforce and the systems around it, and we document them so your team can run them: what each one moves, how often, what happens when it fails, and who gets told.
Which Salesforce integration pattern do you need?
Salesforce's architects describe six integration patterns. Picking the right one first avoids most of the cost and fragility later.
| Pattern | What it does | Typical use |
|---|---|---|
| Request and reply | Salesforce calls another system and waits for the answer | Check credit or stock before saving an order |
| Fire and forget | Salesforce starts a process elsewhere without waiting | Send a closed deal to ERP for invoicing |
| Batch data synchronization | Data is refreshed between systems in batches | Nightly product, price or account updates |
| Remote call-in | Another system creates, reads, updates or deletes Salesforce data | A website or app writes leads and cases into Salesforce |
| UI update on data change | The Salesforce screen updates when data changes | Agents see a status change without refreshing |
| Data virtualization | Salesforce reads external data in real time without storing it | Show ERP order history inside an account record |
Who acts, and when, in each integration pattern?
| Who acts | Timing | |
|---|---|---|
| Request and reply | Salesforce calls out | Waits for the answer |
| Fire and forget | Salesforce calls out | Does not wait |
| Batch data synchronization | Between systems | In batches |
| Remote call-in | Other system calls in | When it calls |
| UI update on data change | Salesforce screen | When data changes |
| Data virtualization | Salesforce reads out | Real time, not stored |
The pattern names and definitions are Salesforce's; the examples are typical uses.
Salesforce integration services we offer
Most projects connect Salesforce to one of a few kinds of system. Each link below goes to a page on that connection: what moves, the options and what to check first.
- ERP: Salesforce SAP integration keeps accounts, products, orders and invoices consistent between SAP S/4HANA or SAP ECC and Salesforce.
- ERP for mid-size firms: NetSuite Salesforce integration turns won opportunities into NetSuite sales orders and shows invoices, payments and fulfilments on the account.
- Email and calendar: Salesforce Outlook integration logs emails and meetings to the right records, and plans the move off Salesforce for Outlook.
- Marketing automation: HubSpot Salesforce integration explains what HubSpot's connector syncs and what it needs.
- Accounting: QuickBooks Salesforce integration keeps customers, invoices and payments consistent with QuickBooks Online.
- IT service management: ServiceNow Salesforce integration connects ServiceNow incidents to Service Cloud cases.
- Middleware: MuleSoft services when many systems share the same data.
- Every other connector: the integration directory lists the systems we have pages for.
Do you need MuleSoft, or can Salesforce connect directly?
A direct connection through Salesforce's APIs suits one or two systems with simple rules. Middleware earns its cost when many systems share the same data, when you need to reuse APIs across projects, or when you need central monitoring and security.
MuleSoft describes its Anypoint Platform as a hybrid integration platform with API management, monitoring and a library of over 1,500 pre-built connectors and integrations. See MuleSoft services if you are choosing a platform.
What makes a Salesforce integration reliable?
- One owner per field. Decide which system is the source of truth for each record and field before building.
- Error handling. Retries, a place where failed records wait, and an alert to a named person.
- Limits and volumes. Designs that stay within Salesforce's API limits at your peak volumes, not just test volumes.
- Security. Integration users with the least access they need, and credentials kept out of code.
- Release testing. Salesforce ships three major releases a year; integrations are retested in the sandbox preview, which Salesforce upgrades four to five weeks before each release.
Industry programs bring their own systems: ERP and plant data in Salesforce for manufacturing, core banking and policy platforms in Salesforce for financial services. To map your systems and choose a pattern, book a discovery call.
What happens at each stage of a Salesforce integration project?
Every integration we deliver is architect-led and runs through the same six stages, from discovery to monitoring. The order matters more than the tools: when an integration breaks, the cause is often a skipped stage, usually field ownership or failure testing.
| Stage | Key questions | What it prevents |
|---|---|---|
| Discovery | Which systems connect, what moves, how much and how often? | Designs sized for test data that fail at month-end volumes |
| Ownership | Which system owns each record and field? | Two systems overwriting each other's updates |
| Design | Does the caller need an answer now, or can the work be queued? Is one system involved, or many? | Synchronous calls that make users wait, or middleware nobody needed |
| Build | Which integration users, credentials and matching rules does each flow need? | Over-privileged users, credentials in code and duplicate records |
| Test | What happens when the other system is slow, down or rejects a record? | Silent failures that surface only when a customer complains |
| Go live and monitor | Who is alerted, what does the runbook say, and when is the next release test? | Integrations that break after one of Salesforce's three major releases a year |
From discovery to monitoring: the six stages of a Salesforce integration
- DiscoveryList the systems, objects, fields, volumes and frequency for each flow.Output: integration inventory
- OwnershipAgree which system is the source of truth for each record and field.Output: field ownership map
- DesignChoose one of Salesforce's six patterns per flow, then direct APIs or middleware such as MuleSoft.Output: pattern per flow
- BuildBuild in a sandbox with integration users that have only the access they need.Output: flows in a sandbox
- TestTest at peak volumes and with failure cases: timeouts, duplicates and rejected records.Output: tested flows
- Go live and monitorAlerts to a named person, dashboards and a runbook, then retesting before each Salesforce release.Output: monitoring and runbook
Salesforce upgrades sandbox preview instances four to five weeks before each major release, so the monitoring stage includes a retest window three times a year. Teams that run integrations themselves after launch get the inventory, the ownership map and the runbook from the earlier stages; those documents are what make an integration supportable by someone who did not build it.
What Salesforce integration costs
Integration is priced by effort: the number of systems and flows, the pattern, data volumes, error handling and how well the other system's API is documented. We do not publish an integration price range we cannot source, so the table shows published hourly rates for the people who do the work. They are third-party figures, not Techila prices.
| Role | Published rate | Source | Note |
|---|---|---|---|
| Consulting partner, senior consultant (US and Western Europe) | $200 to $350 per hour | Savvycom, updated 13 October 2026 | Vendor estimate with no stated method. |
| Consulting partner, architect (US and Western Europe) | $350 to $500 per hour | Savvycom, updated 13 October 2026 | Vendor estimate with no stated method. |
| Onshore certified partner (guideline) | $100 to $250 per hour | Codleo, dated 1 October 2026 | Partner guideline with no stated method. |
| Freelancer (guideline) | $50 to $150 per hour | Codleo, dated 1 October 2026 | Partner guideline with no stated method. |
| US developer, junior | $67 to $104 per hour | Second Talent, dated 24 September 2026 | |
| US developer, mid-level | $85 to $135 per hour | Second Talent, dated 24 September 2026 | |
| US developer, senior | $110 to $171 per hour | Second Talent, dated 24 September 2026 |
More rates, including India, are in the Salesforce developer hourly rates guide, and project budgets in the Salesforce implementation cost guide. For a quote for your systems, book a discovery call.
Common Salesforce integration challenges
- Two systems editing the same field. Without one owner per field, updates overwrite each other; ownership is agreed before the build.
- Duplicate records. Accounts and contacts created in both systems need matching rules, or the sync multiplies them.
- API limits at peak volume. A design that works with test data can fail at month-end; volumes are tested at peak.
- Silent failures. A failed record nobody sees is worse than an error; retries, a holding area and an alert to a named person catch it.
- Over-privileged integration users. Integration users get the least access they need, with credentials kept out of code.
- Salesforce releases. Three major releases a year can change behavior; integrations are retested in the sandbox preview first.
Capabilities
Which systems does Techila connect to Salesforce?
Connector pages describe common systems; most projects mix several of them.
Delivery process
How does a Salesforce integration project run?
Four steps, from a map of what moves where to an integration your team can monitor.
Proof
Recent programs.
All case studies →Want to see how a similar program would run in your org?
Discuss a similar programFAQ
Salesforce integration questions.
What teams ask before they connect Salesforce to other systems.
Work that connects Salesforce with other systems, such as ERP, finance, commerce and telephony, so data moves without re-keying. It covers choosing a pattern, building with APIs or middleware, error handling, security and monitoring.
Salesforce's architects describe six: request and reply, fire and forget, batch data synchronization, remote call-in, UI update based on data changes, and data virtualization.
No. One or two simple connections can use Salesforce's APIs directly. MuleSoft or other middleware pays off when many systems share data, APIs are reused, or you need central monitoring and security.
It depends on the number of systems, the pattern, data volumes and how well the other system's API is documented. Mapping the fields and owners first is the step that most often shortens it.
Salesforce ships three major releases a year and upgrades sandbox preview instances four to five weeks before each one, which gives time to retest integrations before production is upgraded.
Sources
Last reviewed:
- Salesforce Architects, Integration patterns (read 10 November 2026)
- MuleSoft, Anypoint Platform for enterprise integration (read 10 November 2026)
- Salesforce Help, Salesforce upgrade release schedule FAQ (read 10 November 2026)
- Savvycom, Salesforce implementation cost guide (updated 13 October 2026)
- Codleo, Salesforce implementation cost (dated 1 October 2026)
- Second Talent, cost to hire a Salesforce developer (dated 24 September 2026)
- Salesforce AppExchange, Techila Global Services consulting listing (read 10 November 2026)
Talk to an expert about Salesforce Integration Services
Tell us what you need. We reply within 1 business day.
Let's plan your next Salesforce program.
We reply within 1 business day · +1 972-701-1951
See case studies