Definition

iPaaS (Integration Platform as a Service)

iPaaS (Integration Platform as a Service) is the category of cloud middleware products like Boomi, MuleSoft, Workato, and Celigo that move data between SaaS systems on a schedule. It is the standard "CRM + ERP" architecture and the one Factory Labs's ERP-native model replaces.

Last updated

Definition

iPaaS stands for Integration Platform as a Service. It is the category of cloud middleware products that move data between SaaS systems on a schedule. The reference products are Boomi, MuleSoft, Workato, Celigo, and Tray.io, with vendor-specific connectors for each SaaS endpoint (Salesforce, NetSuite, Dynamics, etc.).

iPaaS is what most B2B teams use today to bridge a CRM (Salesforce, HubSpot, Dynamics) to an ERP (SAP, NetSuite, Dynamics BC, SX.e, Prophet 21). The pattern is: the CRM holds a copy of the ERP's data, iPaaS keeps the copy roughly in sync.

How iPaaS works

A typical iPaaS deployment for a CRM-ERP bridge:

  1. Connectors. Pre-built connectors to the source ERP and the destination CRM. Each connector knows the wire format and auth model of its system.
  2. Process definitions. Diagram or code that says "every 15 minutes, pull updated customers from NetSuite, transform them to Salesforce shape, write them to the Salesforce Customer object." A real distributor might have 30-80 of these processes.
  3. Scheduler. Runs each process on the cadence configured (every 15 min, hourly, daily).
  4. Error handling. A queue of failed records that someone (usually a partner or an internal admin) reviews and resolves.
  5. Monitoring. Dashboards showing process success rates, record counts, latencies.

iPaaS works. It is the proven pattern. The question is whether it is the right pattern for the CRM-ERP problem specifically.

What iPaaS costs

For a typical mid-market distributor (32 seats, single ERP, single CRM):

  • iPaaS platform license. Boomi: $24,000-36,000/year. MuleSoft: $30,000-80,000/year. Workato: $20,000-50,000/year. Celigo (lighter, NetSuite-focused): $15,000-30,000/year.
  • Initial integration build. Partner-led: $80,000-150,000 for a Salesforce-to-SAP or Salesforce-to-NetSuite build. More for SX.e or Prophet 21.
  • Annual maintenance retainer. 20-30% of the initial build, so $24,000-48,000/year for ongoing process maintenance, error queue management, and breaking-change adaptation.
  • Internal admin time. A part-time iPaaS admin (often shared with another role) at $40,000-80,000/year in loaded cost.

Five-year all-in for a 32-seat distributor: $250,000-500,000 just for the iPaaS layer.

The detailed walkthrough is in The Real Cost of Salesforce + Boomi vs ERP-Native CRM.

What iPaaS gets wrong (structurally) for CRM-ERP

The pattern is built for the general case of "any system to any system." For the specific case of CRM-to-ERP, three things go wrong:

  1. Staleness by design. The CRM data is always 15+ minutes behind the ERP. For sales reps who need to answer "is this in stock" or "what is this customer's credit," that is wrong.
  2. Reconciliation overhead. Sales-ops spends real time reconciling CRM totals against ERP totals. This is busywork.
  3. Doubled security surface. Customer data exists in two systems with two access models, two audit logs, two breach surfaces.

The trade-off iPaaS makes (generality at the cost of staleness) is the wrong trade-off when the source and destination both speak modern APIs and both are reachable from the same cloud.

When iPaaS is still the right answer

iPaaS earns its keep for:

  • Heterogeneous integrations. Connecting many systems to many systems, where no single pair justifies a purpose-built integration.
  • Batch ETL into a warehouse. Moving data from operational systems into a warehouse for analytics. iPaaS handles this fine.
  • Workflow automation across SaaS apps. "When deal closes in Salesforce, create project in Asana, notify Slack" type flows. Zapier / Workato / Make are the right tool.
  • Long-tail integrations. Niche systems with no purpose-built integration.

The CRM-ERP bridge is none of these; it is the most-traveled integration in the B2B SaaS stack and benefits from purpose-built tooling.

How Factory Labs eliminates the iPaaS layer

Factory Labs ships first-party ERP gateways for SAP, NetSuite, Dynamics 365 BC, Infor SX.e, and Epicor Prophet 21. The gateway reads live; there is no iPaaS layer because there is no sync.

The customer keeps any iPaaS investment for genuinely heterogeneous integrations (the long-tail flows iPaaS is good at). What gets decommissioned is the CRM-ERP bridge specifically: the Boomi processes that moved customers and orders back and forth, with their license cost, partner build, and maintenance retainer.

  • ERP Gateway. The CRM-internal alternative.
  • ERP-Native CRM. The architectural pattern that replaces iPaaS for CRM-ERP.
  • ETL / ELT. The data engineering subset of iPaaS, focused on warehouse loads.

Further reading