Fivetran's Internal Database Replication

This matters because Fivetran is not just a SaaS connector company, it is also a core database replication vendor, and that broader footprint makes the business more durable than any thesis focused only on Salesforce, Stripe, or HubSpot connectors. In practice, many customers use Fivetran to copy data from operational databases like Oracle or Postgres into Snowflake or Databricks for internal reporting, migration, backup, and analytics workflows.

• Fivetran explicitly sells two different jobs. One is app connectors for SaaS tools. The other is CDC database replication, which automates high volume movement from systems like Oracle into Snowflake or between warehouses. That second job has nothing to do with external SaaS vendors.
  1 sacra 2 sacra
• The economics are different for database replication. Transactional databases generate large, constantly changing tables, so the customer pays for dependable high frequency syncing of internal records, not just for cleaning up brittle third party APIs. That helps explain why Fivetran could grow to about $325M in ARR by 2024 while expanding beyond the original SaaS connector wedge.
  1 sacra 4 sacra
• The competitive threat from native warehouse exports is concentrated in a narrower slice of Fivetran's business, mainly the highest volume SaaS connectors where vendors like Stripe or Salesforce can take the revenue back in house. Internal database replication is harder for those SaaS vendors to displace because the source system is the customer's own stack.
  2 sacra 3 sacra 5 sacra

Going forward, the market likely splits in two. Native exports will keep eating some SaaS connector revenue, while internal database replication stays a foundational workload for warehouse migration and analytics. That pushes Fivetran toward being judged less as a connector catalog and more as critical data movement infrastructure inside the enterprise.