The best Salesforce integration tool depends on the job. To connect your own systems, the usual shortlist is MuleSoft, Workato, Boomi, Celigo and Zapier. To ship an integration into each customer's Salesforce org, SaaS companies choose between a unified API (Merge, Apideck), an embedded iPaaS (Paragon, Prismatic, Workato's Embedded Platform), a code-first platform (Ampersand, Nango) or a native managed package.
Last verified: September 17, 2026, by Sunny Chauhan. Prices were rechecked on each vendor's pricing page and on Vendr; limits against Salesforce's Developer Limits and Allocations Quick Reference (Winter '27).
Which Salesforce integration tool fits your job?
Salesforce integration tools fall into four jobs, and a tool built for one job rarely fits another. The table below maps each job to the vendors buyers most often shortlist and the section of this guide that compares them.
| Your job | Shortlist | Section |
|---|---|---|
| Connect Salesforce to systems your company runs (ERP, HRIS, billing) | MuleSoft, Workato, Boomi, Celigo, Jitterbit, Zapier | Best iPaaS platforms |
| Ship your product's integration into each customer's Salesforce org | Merge, Apideck, Paragon, Prismatic, Workato's Embedded Platform, Ampersand, Nango, or a native managed package | SaaS companies |
| Move Salesforce data into a warehouse for analytics | BigQuery Data Transfer Service, Snowflake Openflow, Data Cloud zero copy, Fivetran, Airbyte, Hevo, Skyvia | Warehouses |
| Hire a firm to design and build the integration | Accenture, Deloitte Digital, Capgemini, Coastal (TCS), Grazitti, Cloudity, Merkle, 360 Degree Cloud | Partners |
Salesforce integration means connecting Salesforce to other systems so data flows between them: an ERP (NetSuite, SAP), a marketing platform (Marketo, HubSpot), billing (Stripe, Zuora), a warehouse (Snowflake, BigQuery), or a SaaS product whose users work in Salesforce.
How do SaaS companies ship a Salesforce integration to each customer's org?
A SaaS company that needs to read opportunities and custom quote objects from each customer's Salesforce org and write usage data back has four options: a unified API, an embedded iPaaS, a code-first integration platform, or a native managed package installed in each customer's org. None of them requires a dedicated ETL team. They differ in where the logic runs, how custom objects are handled and what you are billed per.
The matrix below uses only what each vendor publishes on its own pricing page or docs, checked September 17, 2026. Where a vendor does not publish a fact, the cell says so.
| Option | Example vendors | Where the integration logic runs | Custom objects (vendor's own page) | Documented sync | Billing unit (list price) |
|---|---|---|---|---|---|
| Unified API | Merge, Apideck | Vendor's cloud, one normalized CRM model across many CRMs | Merge: "Access custom fields" on the contract-priced Professional plan; docs add Remote Data, Remote Field Classes and Field Mapping | Merge: Launch "Daily"; Professional and Enterprise "Customizable" | Merge: first 3 production Linked Accounts free, $650 per month for up to 10, then $65 per Linked Account |
| Embedded iPaaS | Paragon, Prismatic, Workato's Embedded Platform | Vendor's cloud, workflows configured per customer | Paragon: Standard and Custom Field Mapping in its plan comparison; Dynamic Field Mapping on Enterprise only | Paragon Managed Sync: "up to every minute" | Paragon: custom quote, usage scales with tenants (customer orgs). Prismatic: volume per-instance pricing, "never billed on API calls or executions". Workato: no public list price |
| Code-first (deep) integration platform | Ampersand, Nango | Vendor's cloud, integration defined in code | Ampersand: "Unlimited custom objects and custom fields" on every tier, same price for standard or custom | Ampersand: real-time Subscribe actions from the Catalyst tier; per-customer sync frequency on Accelerate | Ampersand: Launch free (up to 5 customers in production), Catalyst from $999 per month (2 GB included, then $50 per GB, up to 25 customers), Accelerate custom (up to 200). Nango: Free, or Pay-as-you-go with $50 per month in credits, $0.29 per connection, $0.72 per compute hour, $0.50 per GB |
| Native managed package | Built in-house or by a partner | Inside each customer's Salesforce org (Apex, Lightning components, metadata) | Reads and writes the org's standard and custom objects directly, subject to the user's CRUD and field-level security | Apex triggers, Platform Events and Change Data Capture inside the org | Your build cost (your engineers or a partner's quote) and your own maintenance; no per-connection fee to a third party |
Every one of these options spends the customer org's API allocation when your servers call into Salesforce. Salesforce states that "API calls made from installed managed packages, count against your org limit", so a native package is not exempt either. What a managed package changes is that logic running as Apex inside the org, such as a trigger that updates a related record, does not need an inbound API call at all.
What does each option cost at 50 customer orgs?
At 50 connected customer orgs, list prices alone already separate the options. These figures use published list prices only and exclude usage charges and negotiated discounts.
- Merge Launch: $650 plus 40 additional Linked Accounts at $65 is $3,250 per month.
- Nango Pay-as-you-go: 50 connections at $0.29 is $14.50 per month, which sits inside the plan's $50 monthly credit, so connection fees alone do not raise the bill above $50 before compute ($0.72 per hour) and data ($0.50 per GB) charges.
- Ampersand: Catalyst caps at 25 customers, so 50 customers needs the custom-priced Accelerate tier.
- Paragon: custom quote based on tenants.
- Native managed package: no per-org platform fee; the cost is the build plus ongoing maintenance and releases.
What a native managed package build actually involves
Disclosure: Sunny Chauhan is founder and CEO of Appnigma (the author's company), an engineering service that builds native Salesforce and HubSpot integrations and managed packages for SaaS companies. Those builds all need the same engineering work: Apex callouts through Named Credentials with no hardcoded endpoints or secrets, CRUD and field-level security enforcement, bulkified trigger handlers, Custom Metadata Types for configuration, real test coverage, and a clean security review. Warmly.ai, one published customer, launched its native managed package in about a week.
How do you choose between the four options?
The choice comes down to three questions about your integration, answered in order.
- Do you need the same normalized objects across many CRMs, with few custom objects? A unified API such as Merge or Apideck fits.
- Do you need per-customer custom objects and write-back, but want the logic in your own cloud? Compare a code-first platform (Ampersand, Nango) with an embedded iPaaS (Paragon, Prismatic).
- Do you need the integration inside the customer's org (in-transaction logic, a UI inside Salesforce, installation from AppExchange, a packaged External Client App)? Build a native managed package, in-house or with a partner.
For real-time designs inside the org, the choice between Platform Events and Change Data Capture sets your event allocations.
Is Ampersand a good replacement for MuleSoft for product integrations?
Ampersand and MuleSoft solve different problems, so the swap only makes sense for product integrations. MuleSoft Anypoint is Salesforce's enterprise integration and API management platform for connecting systems your own company runs, and it is strong at governance at that scale. Ampersand is built for integrations a SaaS company ships to its customers, with custom objects included on every tier.
The price anchors are far apart. Vendr reports a MuleSoft median of $68,695 per year (72 purchases, range $7,977 to $281,462). Ampersand's Catalyst tier starts at $999 per month, about $11,988 per year at list price. Ampersand's own comparison cites MuleSoft at about $250,000 per year; the Vendr median is roughly a quarter of that.
Merge vs Paragon vs Ampersand: which handles Salesforce custom objects best?
On their own pricing pages, Ampersand is the most explicit about custom objects: every tier includes "Unlimited custom objects and custom fields", and reading or writing a custom object costs the same as a standard one. Merge lists "Access custom fields" on its contract-priced Professional plan, while its Launch plan has "Basic functionality included". Paragon's pricing page does not mention custom objects; it gates Dynamic Field Mapping, the feature for mappings your customers configure themselves, to Enterprise. Ampersand's own comparison states that Paragon gates custom objects to Enterprise, which Paragon's page does not say.
What Salesforce auth changes affect every integration (2025 to 2026)?
Two Salesforce changes shape how any product integration authenticates into a customer's org. Both give admins explicit control over which external apps can reach their org.
- Early September 2025: Salesforce restricted the use of uninstalled connected apps. Users who had already authorized a non-device-flow app keep access; admins can install the app or grant the "Approve Uninstalled Connected Apps" permission.
- Spring '26: Salesforce restricts Connected App creation by default "across both the UI and Metadata API, except through package installation". Re-enabling creation requires a request to Salesforce Support, and Salesforce directs new inbound integrations to External Client Apps.
For a SaaS vendor, this makes packaging part of the integration plan: an app installed through a package is the supported path. The Connected App vs External Client App comparison covers the differences in detail.
What are the best iPaaS platforms for Salesforce integration?
The best iPaaS for Salesforce integration is MuleSoft for enterprise API governance, Workato for business-led automation, Boomi for connector breadth with a pay-as-you-go entry, Celigo for prebuilt SaaS and NetSuite flows, and Zapier for simple record-level triggers. The table shows each vendor's pricing model and a dated price anchor.
| Platform | Strongest at | Pricing model and price anchor (checked September 17, 2026) |
|---|---|---|
| MuleSoft Anypoint (Salesforce) | API management and governance at enterprise scale | Vendr median $68,695 per year, 72 purchases, range $7,977 to $281,462 |
| Workato | Business-user-led, low-code automation across many SaaS apps | No list price ("Talk to sales"); Vendr median $64,544 per year, 341 purchases, range $20,000 to $183,999. See how Workato pricing works |
| Boomi | Connector breadth | Pay-As-You-Go $99 per month plus usage; subscription tiers have no list price and route to "Talk to sales" per Integrate.io's Boomi pricing analysis |
| Celigo | Prebuilt templates for common SaaS pairings, including NetSuite | Priced by "endpoints and flows, not per task or transaction" |
| Jitterbit | ERP and on-premise connectivity | Custom quote |
| Tray.ai | Low-code automation | No public price; contact sales |
| Zapier and Make | Simple record-level triggers, configured not built | Zapier Professional starting from $19.99 per month, task based |
| Integrate.io | Predictable Salesforce ETL pricing | Core $1,999 per month with a 60-second pipeline frequency |
The distinction that matters most is whether you are integrating Salesforce for your own company or shipping a Salesforce integration to your customers. The first is a buying decision and the table above applies. The second is a product decision, covered in the SaaS section above, where per-customer fees scale with every customer you add.
Salesforce also ships its own integration tools that run from inside the platform.
| Tool | What it is | Best for |
|---|---|---|
| Salesforce Connect | Data virtualization: external data appears as Salesforce objects without copying it in | Read-mostly external sources queried in real time |
| Heroku Connect | Bi-directional sync between Salesforce and Heroku Postgres | Custom apps that need a relational mirror of Salesforce data |
| MuleSoft Composer | Low-code automation configured from Salesforce | Admin-driven flows across a few connected systems |
How do Salesforce daily API request limits affect an integration?
Salesforce Enterprise Edition and Professional Edition with API access get 100,000 API requests per 24 hours, plus 1,000 per Salesforce license, plus any purchased API Call Add-Ons. Unlimited and Performance Edition add 5,000 per license instead of 1,000, and Developer Edition gets 15,000. Salesforce's own example: an Enterprise Edition org with 15 licenses has 115,000 requests; by the same formula a 50-seat Enterprise org has 150,000.
Per the Quick Reference, the APIs that count are "the Lightning Platform REST API, the Lightning Platform SOAP API, Bulk API, Bulk API 2.0, and most Connect REST APIs", and "API calls issued by certain Salesforce connected apps (for example, the Salesforce mobile app) don't count". Platform Events and Change Data Capture have their own separate allocations. Calls from installed managed packages count against the org limit too.
How many calls one record sync takes depends on the tool. HubSpot's own Salesforce connector documents that "a single contact sync can take up to four API calls per record, but this number can vary". The table below assumes 5 calls per record to show how volume adds up in a 50-seat Enterprise org.
| Scenario | Daily API calls used | Share of a 150,000 daily allocation |
|---|---|---|
| 10,000 record syncs per day x 5 calls | 50,000 | 33% |
| 30,000 record syncs per day x 5 calls | 150,000 | 100% |
| 50,000 record syncs per day x 5 calls | 250,000 | Above the allocation; plan for purchased API Call Add-Ons |
Salesforce publishes these allocations clearly, which makes them a planning input: check the customer's edition and license count before you choose a sync design, and move in-org logic to Apex or events where it removes inbound calls. The Developers Blog guide to monitoring API usage shows where to watch consumption.
How often do Salesforce integration tools sync?
Documented sync intervals range from real time to once a day, and most vendors publish them on their pricing pages or docs. The table lists the intervals each vendor states.
| Tool | Documented interval |
|---|---|
| Ampersand | Real-time Subscribe actions from the Catalyst tier |
| Paragon Managed Sync | "Up to every minute" |
| Integrate.io Core | 60-second pipeline frequency |
| Heroku Connect (demo plan) | 10-minute minimum polling interval, per Heroku |
| BigQuery Data Transfer Service | 15-minute minimum between recurring transfers, 24-hour default |
| Hevo (Free plan) | 1-hour scheduling |
| Skyvia Data Integration | Free and Basic once a day, Standard once an hour |
What is the best tool to move Salesforce data to BigQuery or Snowflake?
For BigQuery and Snowflake, start with the warehouse vendor's own Salesforce connector and check its documented limits; use managed ELT when those limits do not fit. A full walkthrough is in getting Salesforce data into BigQuery or Snowflake.
Salesforce to BigQuery
Google's BigQuery Data Transfer Service Salesforce connector supports Sales Cloud only, uses Bulk API V1 and supports fields in Bulk API V1 version 64.0. It does not transfer objects with binary fields (Attachment, ContentVersion, Document, StaticResource, Scontrol, EmailCapture, MailMergeTemplate), its minimum recurring interval is 15 minutes, and incremental transfers cannot sync deletes.
When those limits bite, managed ELT is the usual path. Fivetran automatically excludes Salesforce formula fields from synced tables because they cannot be synced incrementally with reliable integrity (a separate formula option is documented), uses both the REST and Bulk APIs, and its free usage covers up to 500,000 monthly active rows for connections. Hevo Starter costs $299 per month billed monthly ($265 billed annually), with a Free plan up to 1M events per month. Skyvia Data Integration Basic costs $99 per month ($79 billed annually). Airbyte, Stitch, and Google Cloud Data Fusion or Dataflow are the other common routes.
Salesforce to Snowflake
The Snowflake Openflow Connector for Salesforce Bulk API is generally available. It uses Bulk API 2.0, replicates standard and custom objects, and authenticates only through the OAuth 2.0 JWT Bearer Flow with an external client app. It does not support custom Salesforce domains, relationship traversal, hard deletes, or location and address fields. Snowflake recommends zero-copy integration with Salesforce Data Cloud if you already use Data Cloud and need near real-time bidirectional integration.
Which ETL tools are best for Salesforce data integration?
The best Salesforce ETL tool is the one that matches where your warehouse already lives. Informatica suits large enterprise data estates, and Salesforce completed its acquisition of Informatica on November 18, 2025. Matillion fits teams already on Snowflake or BigQuery, Talend (Qlik) covers enterprise data quality, Fivetran and Airbyte run managed pipelines, and Coefficient syncs Salesforce with Sheets or Excel.
iPaaS, ETL and a native managed package do different jobs, and the table below separates them.
| iPaaS | ETL | Native managed package | |
|---|---|---|---|
| The job it does | Orchestrates workflows across systems | Moves and reshapes data into a warehouse | Ships your product inside the customer's org |
| Timing | Real time or near real time | Batch, on a schedule | In-transaction, inside the org |
| Runs where | Outside Salesforce | Outside Salesforce | Inside the customer's Salesforce org |
| Salesforce API allocation | Used on every inbound call | Used in bulk on every run | In-org Apex logic makes no inbound API calls; calls from the package still count |
| Typical examples | MuleSoft, Workato, Boomi, Zapier | Informatica, Matillion, Fivetran, Coefficient | A managed package you own |
Two mistakes account for most wasted spend: using iPaaS to distribute your product to customers, when iPaaS connects systems you control and cannot put your app inside a customer's Salesforce with its own UI; and using ETL for live operational workflows, when ETL is batch-oriented and built for analytics.
Which tools connect Salesforce to an ERP such as NetSuite or SAP?
ERP integration needs enterprise iPaaS or a prebuilt connector, because it is bidirectional, transactional and order-sensitive: a quote becomes an order becomes an invoice, and a half-applied sync corrupts a financial record. The Salesforce ERP integration guide covers the build patterns.
| Approach | How it works | Best when |
|---|---|---|
| Enterprise iPaaS (MuleSoft, Boomi, Jitterbit) | Full transformation, error handling, retry and audit logging | Real transactional volume and a finance team that audits it, including SAP |
| Prebuilt ERP connector (Celigo and vendor-supplied connectors) | Templated flows for a specific Salesforce and ERP pair, such as NetSuite | Your pair is common and the template fits |
| Native managed package | The integration ships inside Salesforce as a packaged app | You are the vendor and your customers need it installed in their org |
Task-based automation tools are a poor fit for ERP work: they lack transactional guarantees, and a failure can leave a partially written financial record with no clean retry. For contract management, buy the CLM vendor's own AppExchange package, and check that it is native rather than an iframe, because an iframe leaves no queryable data in your org.
How do HubSpot and Salesforce stay in sync?
HubSpot and Salesforce usually stay in sync through HubSpot's own Salesforce connector. HubSpot's documentation says it requires a HubSpot Professional or Enterprise subscription and a Salesforce edition with API access or Professional Edition (not Group Edition), and the installing user needs the "Download AppExchange Packages" permission. A single contact sync can take up to four API calls per record. When a custom database joins the flow, an iPaaS such as Workato or Boomi is the common layer. The HubSpot Salesforce integration setup guide walks through the connector.
What are the six Salesforce integration patterns?
Salesforce's Integration Patterns and Practices guide, Version 68.0 (Winter '27, last updated July 22, 2026), documents six patterns. The last column maps each pattern to the tool category that usually implements it.
| Pattern | What it is | Usually implemented by |
|---|---|---|
| Remote Process Invocation, Request and Reply | Salesforce calls an external system and waits for the response | Native managed package (Apex callout) |
| Remote Process Invocation, Fire and Forget | Salesforce invokes an external process and does not wait | Native package publishing Platform Events or outbound messages |
| Batch Data Synchronization | Bulk updates on a schedule, in either direction | ETL, unified APIs, embedded iPaaS |
| Remote Call-In | An external system calls into Salesforce through its APIs | iPaaS, unified APIs, embedded iPaaS, code-first platforms |
| UI Update Based on Data Changes | The Salesforce UI updates when data changes | Change Data Capture or Platform Event subscribers |
| Data Virtualization | External data accessed in real time without copying it in | Salesforce Connect external objects |
Who are the top Salesforce integration partners?
If you would rather hire a consulting firm to build a custom integration, these are the leading Salesforce integration partners in 2026. Before shortlisting, check each firm's listing and reviews in the AppExchange consulting directory, and read what "Salesforce integration partner" can mean so you hire the right kind.
| Partner | HQ | Size | Specialization |
|---|---|---|---|
| Accenture | Dublin, Ireland | 750,000+ firm-wide; 56,000+ Salesforce-skilled | Enterprise Salesforce plus AI and Agentforce programs |
| Coastal (formerly Coastal Cloud) | Palm Coast, FL | More than 600 North American professionals; joined TCS (announced December 2025, completed January 14, 2026) | Multi-cloud Salesforce, public sector, RevOps |
| Grazitti Interactive | Panchkula, India | About 1,400 across 4 continents | Marketo and Salesforce integrations, communities and portals |
| Cloudity (Hardis Group) | Warsaw, Poland | 350 (293 Salesforce-certified) | EU Salesforce Platinum partner, MuleSoft |
| Merkle (dentsu) | Columbia, MD | 14,000+ at Merkle | Marketing Cloud, Data Cloud, customer experience |
| 360 Degree Cloud | Walnut, CA and India | 600+ certified | Mid-market Salesforce implementations |
| Enterprise SI tier | Global | Deloitte Digital 16,200+ Salesforce-certified; Capgemini 10,100+ | Deloitte Digital (16,200+ Salesforce-certified), Capgemini (10,100+), HCLTech, Cognizant, TCS |
How much does Salesforce integration cost in 2026?
Salesforce integration costs range from a few hundred dollars a year for simple automation to six figures for enterprise iPaaS or a custom build. The table groups annual costs by category.
| Category | Typical cost | Best for |
|---|---|---|
| iPaaS entry tier (Zapier Professional) | From $240 per year at $19.99 per month | SMB, simple workflows |
| iPaaS mid-market (Integrate.io Core) | $23,988 per year at $1,999 per month | Mid-volume Salesforce ETL and ELT |
| Warehouse ELT (Hevo Starter, Skyvia Basic) | $948 to $3,588 per year at list price | Single-warehouse pipelines |
| iPaaS enterprise (Workato) | Vendr median $64,544 per year, range $20,000 to $183,999 | Multi-system orchestration |
| MuleSoft Anypoint | Vendr median $68,695 per year, up to $281,462 | Enterprise governance and compliance |
| Product integration platforms (Merge, Ampersand, Nango, Paragon) | Free tiers to custom quotes; about $3,250 per month for 50 orgs on Merge Launch | SaaS vendors serving many customer orgs |
| Custom managed-package build (SI firm) | $75,000 to $400,000 one-time, plus maintenance | Custom native integrations |
Frequently Asked Questions
What is iPaaS in Salesforce?
iPaaS (Integration Platform as a Service) is a hosted platform that connects Salesforce to other systems over the Salesforce APIs, supplying connectors, scheduling, retries and monitoring. MuleSoft, Workato, Boomi, Celigo and Jitterbit are the platforms most often used with Salesforce. You handle the mapping and the license cost.
Does iPaaS consume Salesforce API calls?
Yes. Every REST, SOAP or Bulk API call an iPaaS makes into Salesforce counts against the org's 24-hour API allocation, which starts at 100,000 plus 1,000 per license on Enterprise Edition. At high volume, teams plan for purchased API Call Add-Ons.
Do managed packages count against Salesforce API limits?
API calls made from installed managed packages count against the org's limit, according to Salesforce's Developer Limits Quick Reference. Logic that runs as Apex inside the org, such as a trigger updating a related record, does not need an inbound API call.
Which embedded iPaaS offers deep Salesforce coverage?
Paragon, Prismatic and Workato's Embedded Platform are the embedded iPaaS options most often compared for Salesforce. Paragon documents sync up to every minute and gates Dynamic Field Mapping to Enterprise. For unlimited custom objects on every tier, Ampersand, a code-first platform, is the most explicit on its pricing page.
What is the best alternative to coding dozens of one-off Salesforce connectors?
Use a unified API (Merge, Apideck) if you need the same objects across many CRMs, a code-first platform (Ampersand, Nango) or embedded iPaaS (Paragon, Prismatic) for per-customer custom objects, or one native managed package that every customer installs in their own org.
What is the difference between ETL and iPaaS for Salesforce?
ETL moves data on a schedule into a warehouse for analysis, while iPaaS orchestrates live workflows between applications. Using ETL for an operational workflow leaves users looking at stale records.
What does it cost to set up a Salesforce data integration tool?
Entry tools cost from $19.99 per month (Zapier Professional) and warehouse pipelines from $299 per month (Hevo Starter), while enterprise iPaaS contracts have Vendr medians of $64,544 (Workato) and $68,695 (MuleSoft) per year. Custom managed-package builds by an SI firm run $75,000 to $400,000 one-time.
Related Articles
- Salesforce ISV Partner Program: tiers, costs and how to join
- How to list your app on the Salesforce AppExchange (2026)
- Salesforce app development costs in 2026
- What is the Salesforce AppExchange and Partner Console?
Sources
- Salesforce, Integration Patterns and Practices, Version 68.0, Winter '27
- Salesforce, Developer Limits and Allocations Quick Reference
- Salesforce, Spring '26 release architect highlights
- Vendr, MuleSoft pricing and Workato pricing
- Vendor pricing pages: Ampersand, Merge, Paragon, Nango, Prismatic, Integrate.io
- Merge docs, supplemental data
- Ampersand, 8 Best Tools to Build a Salesforce Integration (2026)
