The right Salesforce integration tool depends on whose Salesforce org the integration lives in. Connecting your own company's org to an ERP or warehouse means buying an iPaaS (integration platform as a service) such as MuleSoft, Workato or Boomi. A SaaS company whose customers want its product inside their Salesforce faces a product decision instead. The same integration has to run in hundreds of customer orgs, and each org has its own custom objects, admins and API allocation.
That product decision has four routes. A unified API (Merge, Apideck) gives you one normalized model across many CRMs. An embedded iPaaS (Paragon, Prismatic, Workato's embedded platform) runs per-customer workflows in the vendor's cloud. A code-first platform (Nango, Ampersand) lets your engineers define integrations in code on hosted infrastructure. A native managed package installs inside each customer's org. Appnigma is an option on the services side of that choice. Its done-for-you integration delivery promises "Build your product. We'll build the integrations." A named integration engineer handles implementation and ongoing maintenance. Its native Salesforce app development covers "a native app, marketplace listing preparation, and review support." If you want a consulting firm to integrate your own org, our guide to choosing a Salesforce integration partner is the better starting point.
Updated October 2026. Every vendor price was rechecked on the vendor's own pricing page on October 27, 2026, and every limit against Salesforce's API Request Limits and Allocations page. Ampersand has moved to consumption pricing with no public list price, so the earlier tier prices and customer caps are gone, and Vendr's Workato figures were updated. This version adds the call arithmetic that decides what an integration costs each customer org, and it drops the consulting-firm headcount table, whose figures could not be traced to current sources.
Four jobs, four different shortlists
Salesforce integration tools sort cleanly by the job they were built for, and a tool built for one job rarely fits another. Most bad tool choices start with picking from the wrong row.
| Your job | Shortlist | Where the logic runs |
|---|---|---|
| Connect Salesforce to systems your company runs (ERP, HRIS, billing) | MuleSoft, Workato, Boomi, Celigo, Jitterbit, Zapier | The iPaaS vendor's cloud or your runtime |
| Ship your product's integration into each customer's Salesforce org | Merge, Apideck, Paragon, Prismatic, Nango, Ampersand, or a native managed package | The vendor's cloud, your cloud, or inside each customer org |
| Move Salesforce data into a warehouse for analytics | BigQuery Data Transfer Service, Snowflake Openflow, Fivetran, Airbyte, Hevo, Skyvia | A pipeline outside Salesforce |
| Show external data inside Salesforce without copying it | Salesforce Connect external objects | Queried live from the source |
Salesforce's own Integration Patterns and Practices guide (Version 68.0, last updated July 22, 2026) describes the same split in its six patterns. Remote Call-In, where an outside system calls Salesforce's APIs, is what an iPaaS, unified API or embedded iPaaS does. Remote Process Invocation, where Salesforce calls out to your service, is what Apex code in a managed package does.
How do SaaS companies ship a Salesforce integration to each customer's org?
A SaaS company shipping a Salesforce integration to its customers faces three problems an internal IT team does not. The integration runs in many orgs at once. Each customer customizes Salesforce differently. Every API call the product makes is charged to the customer's allocation rather than the vendor's. The four routes for shipping one trade those problems off differently. The table uses only what each vendor publishes on its own pricing page, checked October 27, 2026.
| Route | Example vendors | Where the logic runs | Custom fields and mappings (vendor's own page) | Billing unit (list price) |
|---|---|---|---|---|
| Unified API | Merge, Apideck | Vendor's cloud, one normalized CRM model | Merge lists "Access custom fields" on its contract-priced Professional plan. Launch has "Basic functionality included" and a "Daily" sync | Merge Launch has 3 free production Linked Accounts, then $650 a month for up to 10 and $65 per Linked Account after |
| Embedded iPaaS | Paragon, Prismatic, Workato's embedded platform | Vendor's cloud, workflows configured per customer | Paragon puts Dynamic Field Mapping in its Enterprise column and syncs "up to every minute" | Paragon usage "scale[s] based on the number of tenants". Prismatic is "never billed on API calls or executions" |
| Code-first platform | Nango, Ampersand | Vendor infrastructure, integration defined in your code | Defined by your own code per customer | Nango Pay-as-you-go is $50 a month in credits, then $0.29 per connection, $0.72 per compute hour and $0.50 per GB. Ampersand is "Priced by infrastructure consumption" with no public list price |
| Native managed package | Built in-house or by a partner | Inside each customer's org as Apex, Lightning components and metadata | Reads and writes the org's standard and custom objects directly, subject to the user's object and field permissions | Your build and maintenance cost, with no per-connection fee to a third party |
Sources for the table are each vendor's pricing page, listed under Sources below. Workato does not publish a price for its embedded product. Our embedded iPaaS vs Appnigma comparison covers when a platform subscription or a delivered integration fits better.
What each route costs at 50 customer orgs
At 50 connected customer orgs, list prices already separate the routes. This is our arithmetic from published list prices only, before usage charges and negotiated discounts.
Merge Launch comes to $650 plus 40 more Linked Accounts at $65, or $3,250 a month. Nango's connection fees for 50 connections are $14.50, which sits inside the plan's $50 monthly credit, so the bill depends on compute hours and data volume rather than customer count. Paragon, Ampersand and Workato's embedded platform require a quote. A native managed package has no per-org platform fee, and its cost is the build plus every release you maintain after it.
The per-org fee is not the number that usually decides the route. What decides it is whether your customers' custom objects fit the vendor's model, and whether the integration needs to act inside a Salesforce transaction, such as blocking a save or updating a related record the moment an opportunity closes. Only code running in the org can do the second.
Merge vs Paragon vs Ampersand for Salesforce custom objects
These three are the names SaaS teams most often compare when customers have their own custom objects and field mappings. Merge's pricing page lists "Access custom fields" on its contract-priced Professional plan. Its Launch plan has "Basic functionality included." Paragon puts Dynamic Field Mapping, the feature that lets your customers configure their own mappings, in its Enterprise column. Ampersand bills by actions such as Read, Write and Subscribe, and its pricing page does not mention custom objects. None of the three pages tells you whether a customer's custom quote object with its own validation rules will work, so run a proof of concept against a real customer org before signing.
Which route fits your integration
Answer three questions in order. If you need the same few objects across many CRMs and customers rarely customize them, a unified API is the shortest path. If each customer needs its own field mappings and write-back but you want the logic in your own cloud, compare a code-first platform with an embedded iPaaS on how customer-specific mappings are stored and versioned. If the integration needs an interface inside Salesforce, in-transaction logic or an AgentExchange (formerly AppExchange) listing, build a native managed package.
The routes also mix. A common shape is a managed package for the in-org pieces, such as a Lightning component and a trigger, with your backend handling the heavy sync. Appnigma's integration infrastructure for your engineers is built for teams that want to keep that work in-house, with "default mappings" plus "custom objects, field transformations, and workflow rules for individual customers."
Do managed packages and iPaaS count against Salesforce API limits?
Yes, both do. Salesforce's API limits page says "API calls made from installed managed packages, count against your org limit," and every REST, SOAP or Bulk call an iPaaS or unified API makes is charged to the same org. The difference is that Apex running inside the org, such as a trigger that updates a related record, makes no inbound API call at all. Event delivery works the same way. Salesforce's Change Data Capture allocations cover external subscribers such as Pub/Sub API clients. The delivery allocation "doesn't apply to Apex triggers, flows, or Process Builder processes."
The daily allocation for Enterprise Edition and Professional Edition with API access is 100,000 requests plus 1,000 per Salesforce license, plus any purchased add-ons. Unlimited and Performance editions get 5,000 per license. Salesforce's own example is an Enterprise org with 15 licenses at 115,000 requests. The limit is pooled across the whole org, which Salesforce states as "Limits and allocations are not on a per-user basis," so your product shares it with every other tool the customer runs.
What one sync costs a customer org
Call design, not record count, sets the bill. Take a product that pushes 10,000 changed records a day into a customer's Enterprise org. The arithmetic below uses Salesforce's documented request rules.
| Call pattern | Calls per day for 10,000 records | Share of a 10-license org (110,000) | Share of a 50-license org (150,000) |
|---|---|---|---|
| One REST call per record | 10,000 | 9.1% | 6.7% |
| HubSpot's documented connector rate of up to 4 calls per record | Up to 40,000 | Up to 36.4% | Up to 26.7% |
| sObject Collections, 200 records per call | 50 | 0.05% | 0.03% |
| Composite Batch, 25 subrequests per call | 10,000 | 9.1% | 6.7% |
The figures come from the following documents. sObject Collections adds "up to 200 records" per request. Salesforce adds that "The entire request counts as a single call toward your API limits." Composite Batch bundles 25 subrequests, but "Each subrequest counts against rate limits," so it saves round trips, not allocation. HubSpot's own Salesforce connector documentation says "a single contact sync can take up to four API calls per record, but this number can vary." For loads above a few thousand records, Salesforce's Bulk API limits page says "Any data operation that includes more than 2,000 records is a good candidate for Bulk API 2.0."
Size the design for the smallest org you sell to, not your test org. The same sync that looks harmless in a large customer can use a third of a small customer's day. When an org runs over, Salesforce "still lets the operations proceed by a certain amount" until it reaches a hard cap. Its advice on that overage is "Don't rely on it on an ongoing basis." The customer's admin sees that as your product breaking their other integrations, which is how an API design choice becomes a renewal conversation. When you evaluate a unified API or embedded iPaaS, ask the vendor which of these call patterns it uses against Salesforce.
Salesforce auth changes that push product integrations toward packaging
Two recent Salesforce changes shape how any product integration authenticates into a customer's org. In early September 2025, Salesforce restricted the use of uninstalled connected apps. Users who had already authorized an app keep access, and admins can install the app or grant the "Approve Uninstalled Connected Apps" permission. Then came the Spring '26 release. Salesforce's architect highlights say it "restricts Connected App creation by default across both the UI and Metadata API, except through package installation." The same post says "New inbound integrations should use ECAs," meaning External Client Apps.
For a SaaS vendor, this makes packaging part of the integration plan from the start. An app delivered through a package your customers install is the supported route, and asking each customer's admin to create a connected app by hand is no longer the default. Our Connected App vs External Client App comparison covers what changes for your OAuth setup.
Best iPaaS for connecting Salesforce to your own systems
For integrating your own company's Salesforce org, MuleSoft suits enterprise API governance and Workato suits business-led automation across many SaaS apps. Boomi offers a pay-as-you-go entry point. Celigo fits prebuilt NetSuite flows, and Zapier handles simple record-level triggers. Prices come from each vendor's pricing page, or from Vendr's purchase data where no list price exists, checked October 27, 2026.
| Platform | Strongest at | Price anchor |
|---|---|---|
| MuleSoft Anypoint (Salesforce) | API management and governance at enterprise scale | Vendr median $68,695 a year across 72 purchases, range $7,977 to $281,462 |
| Workato | Business-led automation across many SaaS apps | No list price. Vendr median $64,772 a year across 344 purchases, range $20,278 to $182,987 (how Workato pricing works) |
| Boomi | Connector breadth with a usage-based entry | Pay-As-You-Go "$99 per month plus usage" |
| Celigo | Prebuilt flows for common SaaS pairings, including NetSuite | "Pay for endpoints and flows, not per task or transaction" |
| Jitterbit | ERP and on-premise connectivity | Custom quote |
| Zapier | Simple record-level triggers | Professional "Starting from $19.99 /month," task based |
| Integrate.io | Salesforce ETL with a fixed monthly price | Core $1,999 a month with a 60-second pipeline frequency |
Salesforce also ships integration tools that run from inside the platform. Salesforce Connect shows external data as Salesforce objects without copying it in. Heroku Connect keeps a two-way Postgres mirror of Salesforce data, and per Heroku's documentation it polls every ten minutes by default, with a range of two to 60 minutes on paid plans. MuleSoft Composer lets admins build flows across a few connected systems from Salesforce. If the shortlist is down to two enterprise platforms, our Boomi vs MuleSoft comparison goes deeper.
An iPaaS is the right buy when you control both ends. It is the wrong tool for distributing your product to customers, because it connects systems you own and cannot put your app, its interface or its in-transaction logic inside a customer's org.
Salesforce data into BigQuery or Snowflake
For analytics, start with the warehouse vendor's own Salesforce connector, check its documented limits, and move to managed ELT only when those limits bite. Our guide to getting Salesforce data into BigQuery or Snowflake walks through both.
Google's BigQuery Data Transfer Service connector "only supports transfers from Salesforce Sales Cloud" and supports fields in Bulk API V1 version 64.0. It skips objects with binary fields such as Attachment and ContentVersion. Transfers run no more often than every 15 minutes, and incremental transfers cannot sync deletes. The Snowflake Openflow Connector for Salesforce Bulk API is generally available, uses Bulk API 2.0 and authenticates only through the OAuth 2.0 JWT Bearer Flow with an external client app. It does not support custom Salesforce domains, hard deletes or consolidating several Salesforce instances into one database.
When those limits rule out the native connector, managed ELT is the usual next step. Fivetran excludes formula fields from synced tables and recommends "a transformation-based approach" for them, and its free plan covers 500,000 monthly active rows. Hevo Starter is $299 a month billed monthly, and Skyvia Data Integration Basic is $99 a month with scheduling once a day. ETL and ELT tools are built for batch analytics, so using one for a live operational workflow leaves users looking at stale records.
ERP and HubSpot sync with Salesforce
ERP integration needs an enterprise iPaaS or a prebuilt connector because it is two-way, transactional and order-sensitive. A quote becomes an order and then an invoice, and a half-applied sync leaves a broken financial record. MuleSoft, Boomi and Jitterbit handle the transformation, retry and audit logging that real transactional volume needs, including SAP. Celigo's templated flows suit a common pair such as Salesforce and NetSuite. Task-based tools are a poor fit, because a failure mid-sequence can leave a partly written record with no clean retry. Our Salesforce ERP integration guide covers the build patterns.
HubSpot and Salesforce usually stay in sync through HubSpot's own connector. Per HubSpot's documentation, it needs a HubSpot Professional or Enterprise subscription and a "Salesforce edition with API access, or Salesforce Professional." Group Edition is not supported, and the installing user needs the "Download AppExchange Packages" permission. Our HubSpot Salesforce integration setup guide walks through the connector.
Mistakes that make a Salesforce integration expensive later
These are the failure modes that show up after launch, when changing the design is hardest.
- Choosing by connector count. A long connector list says nothing about whether a customer's custom quote object and its validation rules will work. Test the vendor against your messiest customer's org before signing.
- Sizing API use on your own test org. A developer org gets 15,000 calls a day and a large customer far more. Model your sync against a 10-license Enterprise org, the smallest you are likely to sell to.
- One call per record. Writing records one at a time costs the customer up to 200 times more allocation than sObject Collections for the same data.
- Asking customer admins to create connected apps. Since Spring '26, connected app creation outside package installation is off by default, so plan an installable package or External Client App route.
- Treating the build as the finish line. Salesforce ships three releases a year, and every customer org gets each one. Budget for maintenance and per-customer monitoring, or the integration that closed the deal becomes the reason for a churn conversation.
When a consulting firm is the better choice
A Salesforce consulting partner is the right hire when you are a Salesforce customer integrating your own org, for example connecting Sales Cloud to SAP with heavy data migration and change management. Check each firm's listing and reviews in the AgentExchange consulting directory. Salesforce reorganized its consulting partner tiers in March 2026, so older "Platinum" or "Crest" labels on third-party lists no longer match the program. Our guide to what a Salesforce integration partner actually does explains the difference between consultants, product development firms and building as an ISV.
For a SaaS company, a consultant's one-org project rarely covers what comes next, such as packaging, security review and keeping the integration working across hundreds of customer orgs. That is where a product-focused build, in-house or with a partner that maintains it, fits better.
Frequently Asked Questions
What is the best iPaaS for Salesforce?
For your own company's systems, MuleSoft fits enterprise governance and Workato fits business-led automation. Boomi offers a usage-based start and Celigo suits NetSuite flows. For shipping your product into customers' orgs, compare unified APIs, embedded iPaaS, code-first platforms and a native managed package instead.
Which embedded iPaaS offers deep Salesforce coverage?
Paragon, Prismatic and Workato's embedded platform are the embedded iPaaS options most often compared. Paragon documents sync "up to every minute" and puts Dynamic Field Mapping on Enterprise, and Prismatic bills per instance rather than per API call.
Does a native managed package avoid Salesforce API limits?
No. Calls made from installed managed packages count against the customer org's limit. Apex logic that runs inside the org, such as a trigger, makes no inbound API call, and Apex trigger subscribers do not use the event delivery allocation.
What is the difference between ETL and iPaaS for Salesforce?
ETL moves data on a schedule into a warehouse for analysis. iPaaS orchestrates live workflows between applications, so it suits operational processes such as order-to-invoice.
Can Appnigma build our Salesforce integration?
Yes. Appnigma builds and maintains customer-facing Salesforce and HubSpot integrations for SaaS companies, with a named integration engineer, and builds native managed packages with listing preparation and security review support. Review timing stays with Salesforce.
About the author
Sunny Chauhan is the co-founder and CEO of Appnigma AI, which builds and maintains customer integrations and native Salesforce and HubSpot apps for B2B SaaS teams. Before Appnigma, he was on Salesforce's AppExchange team, where he worked with more than 300 SaaS partners. He has spent close to a decade on the Salesforce platform, including work at Zennify, and holds Salesforce certifications including Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate.
Related Articles
- Choosing a Salesforce integration partner as a SaaS company
- Salesforce managed package guide
- Platform Events vs Change Data Capture
- Connected App vs External Client App
- Salesforce security review guide
Sources
- API Request Limits and Allocations, Salesforce Developer Limits and Allocations Quick Reference
- Bulk API and Bulk API 2.0 Limits and Allocations, Salesforce
- Create Records Using sObject Collections and Composite Batch, REST API Developer Guide
- Change Data Capture Allocations, Salesforce
- Integration Patterns and Practices, Version 68.0, Salesforce
- Spring '26 release architect highlights, Salesforce Architects
- Restriction on uninstalled connected apps, Salesforce Help
- Merge pricing and Paragon pricing. All vendor pages were checked October 27, 2026
- Prismatic pricing and Nango pricing
- Ampersand pricing and Boomi pricing
- Celigo pricing and Zapier pricing
- Integrate.io pricing and Hevo pricing
- Skyvia pricing and Fivetran pricing
- Vendr purchase data for MuleSoft and Workato
- BigQuery Data Transfer Service for Salesforce, Google Cloud, and Openflow Connector for Salesforce Bulk API, Snowflake
- Fivetran Salesforce connector, Fivetran docs
- Heroku Connect mapping configuration options, Heroku Dev Center
- Install the HubSpot Salesforce integration, HubSpot Knowledge Base
