Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP

Heroku Connect Pricing and Lock-In: Plan Your Heroku Exit

Heroku Connect pricing and its tie to Heroku Postgres create lock-in. What costs and work to plan for when leaving Heroku with Build.io and Stacksync.

Author
Stacksync · App tips writer
Published
Read time
5 min read
Heroku Connect Pricing and Lock-In: Plan Your Heroku Exit
APP TIPS

What should teams leaving Heroku plan for with Heroku Connect?

Plan for two things: the cost structure of Heroku Connect itself, and the lock-in that comes from it only working with Heroku Postgres. Leaving Heroku means replacing the sync, not only the hosting, so the budget needs a line for a new sync and for the time to validate it.

This guide does not list prices, because Heroku Connect terms vary by contract. It explains how the costs are structured and where they show up in a migration plan.

How is Heroku Connect pricing structured?

Heroku Connect is an add-on in the Heroku ecosystem. Its cost sits alongside the other Heroku line items: dynos, Heroku Postgres plans and other add-ons. Depending on the plan, the price can relate to how many rows you sync and the level of support, and some teams buy it as part of a wider Salesforce agreement.

Because of that, the real cost of Heroku Connect is rarely one line. It includes:

  • The Heroku Connect add-on or contract line itself.
  • The Heroku Postgres plan it requires, sized for synced data.
  • The dynos and add-ons that stay on Heroku because the database does.
  • Engineering time spent working around sync limits or errors.
Check your own numbers
Pull the last few Heroku invoices and your Salesforce contract before budgeting. Your actual terms are the only reliable baseline.
Heroku Connect compared with Stacksync
Heroku Connect compared with Stacksync

Where does the lock-in come from?

The lock-in is architectural, not contractual. Heroku Connect writes Salesforce data into Heroku Postgres and nowhere else. Once the app depends on that schema, moving the database means losing the sync, and moving the app without the database adds latency and complexity.

Heroku Connect also only covers Salesforce. Teams that add HubSpot, NetSuite or other systems end up running separate integrations next to it, which adds cost and more places for data to drift.

Cost driverStaying on Heroku ConnectMoving to Build.io + Stacksync
PlatformHeroku dynos, Postgres and add-onsBuild.io moves apps and platform off Heroku
Salesforce syncHeroku Connect add-onStacksync two-way sync with Postgres
Database locationMust stay on Heroku PostgresAny Postgres the platform provides
Other CRMs and ERPsSeparate tools or custom codeSame sync layer covers HubSpot, NetSuite and others
Migration effortNone now, deferredOne-time mapping, parallel run and cutover

A practical way to measure lock-in is to ask what it would take to move only the database next quarter. If the honest answer is that the Salesforce sync would stop, the sync is the constraint, and it should be planned before the platform.

What one-time costs come with a Heroku exit?

Leaving is not free, and it is better to plan for the one-time costs than to discover them mid-project.

  • Mapping work. Documenting Heroku Connect objects, fields and directions.
  • Platform migration. Moving apps, the database, add-ons and pipelines with Build.io.
  • Parallel run. A period where both Heroku Connect and Stacksync run, so you pay for both.
  • Salesforce API usage. Extra calls while two syncs read the same org.
  • Validation. Engineering time to compare data and test writes.

These are bounded costs. The ongoing cost of staying tied to one database and one CRM keeps running.

Heroku migration topology: app moves to a new platform while Stacksync keeps Salesforce and Postgres in sync
Heroku migration topology: app moves to a new platform while Stacksync keeps Salesforce and Postgres in sync

How should you build the budget?

  1. 01
    Collect current spend
    Gather Heroku invoices and the Salesforce contract terms covering Heroku Connect.
  2. 02
    Separate platform from sync
    Split current costs into platform (dynos, Postgres, add-ons, pipelines) and sync (Heroku Connect).
  3. 03
    Price the replacement platform
    Get a proposal from Build.io for moving the app and platform off Heroku.
  4. 04
    Price the replacement sync
    Get a Stacksync quote based on your Salesforce objects, other systems and record volumes.
  5. 05
    Add one-time migration costs
    Include mapping, the parallel run, API usage and validation time.
  6. 06
    Compare over a realistic period
    Weigh ongoing costs over the time you expect to run the app, not only the first month.
Book a Stacksync demo

What costs are easy to miss when staying on Heroku Connect?

Some of the cost of Heroku Connect never shows up on an invoice. It shows up as engineering time and as decisions the team avoids.

  • Workarounds. Custom jobs written to fill gaps, such as syncing systems Heroku Connect does not support.
  • Sizing for the sync. Database plans chosen for synced data volume rather than for the app's needs.
  • Delayed platform decisions. Projects that would move part of the stack elsewhere get postponed because the sync cannot move.
  • Troubleshooting. Time spent investigating sync errors and replaying failed records.

None of these have a fixed price, but they belong in the comparison. Ask the engineers who maintain the integration how much of their time it takes, and include that estimate alongside the invoice figures.

When is the right time to act?

Contract renewal is the natural decision point. Starting the mapping and a Stacksync test a few months before renewal gives you real data on effort and a working alternative before you have to commit to another term.

Compare the two approaches in detail on our Heroku Connect alternative page, review supported objects on the Salesforce connector page, or book a demo to get pricing for your setup.

Start syncing with Stacksync

FAQ

Frequently asked questions

How is Heroku Connect priced?
Heroku Connect is sold as a Heroku add-on, and pricing depends on your plan and contract with Heroku or Salesforce. Check your current invoice and contract terms rather than relying on list prices, which may not reflect what you pay.
Why does Heroku Connect create lock-in?
It only syncs Salesforce with Heroku Postgres. To keep using it, the database has to stay on Heroku, which in practice keeps much of the app there too.
What costs should we budget for when replacing Heroku Connect?
Budget for the new platform, the new sync tool, engineering time for mapping and validation, a parallel-run period where both syncs operate, and Salesforce API usage during testing.
Can we leave Heroku but keep Heroku Connect?
Only by keeping a Heroku Postgres database for the sync and copying data elsewhere. That keeps a Heroku bill and adds a second data hop, so most teams treat it as temporary.
Does Stacksync publish its pricing?
Talk to the Stacksync team for pricing based on your systems and record volumes. Book a demo to get a quote for your setup.

Explore these integrations and topics

Keep reading

Related articles

All articles
App tips Build.io + Stacksync FAQ: Planning a Heroku Exit 5 min read read
App tips Build.io and Stacksync: The Complete Heroku Migration Stack 4 min read read
App tips Heroku Alternatives for Salesforce-Connected Apps 5 min read read
Coworkers laughing in front of a laptop in a casual office setting

You just read how it should work.
See it run on your own data.

Book a demo Get started