--- title: "Heroku Exit Checklist: Apps, Postgres, Add-ons, Heroku Connect" description: "A complete Heroku exit checklist covering apps and dynos, Postgres, add-ons, pipelines and Heroku Connect, with who handles each item: Build.io or Stacksync." canonical: https://www.stacksync.com/blog/heroku-exit-checklist-apps-postgres-addons-heroku-connect last_modified: 2026-10-23 --- # Heroku Exit Checklist: Apps, Postgres, Add-ons, Heroku Connect > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md A complete Heroku exit checklist covering apps and dynos, Postgres, add-ons, pipelines and Heroku Connect, with who handles each item: Build.io or Stacksync. Author Stacksync · App tips writer Published October 23, 2026 Read time 4 min read APP TIPS ## What belongs on a Heroku exit checklist? A Heroku exit checklist should cover five areas: apps and dynos, Heroku Postgres, add-ons, pipelines and configuration, and Heroku Connect. [Build.io](https://www.build.io/) moves the first four off Heroku. Stacksync replaces Heroku Connect with real-time, two-way Salesforce to Postgres sync, which keeps the data your app depends on flowing after the move. Use the lists below as a working document. Each item should have an owner and a verification step before cutover. ## What do you need to check for apps and dynos? - List every app, including staging and review apps. - Record web, worker and scheduled process types and their scaling. - Capture config vars and secrets, and decide where they will live. - Note custom domains and TLS certificates. - Document buildpacks or build settings each app uses. This is the core of the platform move and sits with Build.io. Capture the current state in writing even if the plan is to replicate it exactly, because the inventory becomes the acceptance test for the new environment. Teams that skip this step tend to discover a missing worker or config var after traffic has moved. ![Moving from Heroku Connect to Stacksync during a Heroku migration](https://www.stacksync.com/images/blog-diagrams/heroku-connect-migration-concept.webp) *Moving from Heroku Connect to Stacksync during a Heroku migration* ## What do you need to check for Heroku Postgres? - Identify every Postgres database and which apps attach to it. - Flag which tables are written by Heroku Connect. - Note extensions, connection pooling and follower databases. - Plan the data move and a final sync point for cutover. - Confirm backup and restore on the target platform. Watch for Tables managed by Heroku Connect look like ordinary tables. If you do not flag them, they will move as static data and stop updating. ## What do you need to check for add-ons and pipelines? - List each add-on and what it provides: logging, caching, queues, monitoring, email and similar services. - Decide on a replacement or a direct vendor account for each. - Document pipeline stages and promotion steps. - Record deploy hooks and CI integrations. Add-ons and pipelines are part of the platform move with Build.io. ![Decision flow for replacing Heroku Connect](https://www.stacksync.com/images/blog-diagrams-mermaid/heroku-connect-showdown-decision.webp) *Decision flow for replacing Heroku Connect* ## What do you need to check for Heroku Connect? - Export every mapping: object, fields, direction and table name. - Identify services outside the app that read those tables. - Choose the Salesforce sandbox for testing. - Recreate mappings in Stacksync against the new database. - Plan how existing rows will be matched by Salesforce ID. This is the part of the checklist Stacksync owns. Review supported objects on the [Salesforce connector](https://www.stacksync.com/connectors/salesforce) page and our overview of [Stacksync as a Heroku Connect alternative](https://www.stacksync.com/heroku-connect-alternative). ## Who owns each part of the checklist? | Area | Owner | Verify before cutover | | --- | --- | --- | | Apps and dynos | Build.io | App runs on the new platform with production config | | Heroku Postgres | Build.io | Data moved, extensions present, backups configured | | Add-ons | Build.io and your team | Each service replaced or re-provisioned | | Pipelines and deploys | Build.io | A build can be promoted to production | | Heroku Connect | Stacksync | Counts match, inserts and write-backs work in staging | | Other CRM and ERP integrations | Stacksync | HubSpot, NetSuite or other syncs tested | ## What about integrations beyond Salesforce? Heroku Connect only covers Salesforce, but many Heroku apps also pull data from other systems through custom scripts, scheduled jobs or add-ons. A Heroku exit is a good moment to list those too, because scripts that ran on Heroku Scheduler or worker dynos move with the platform and may need to be rebuilt anyway. - CRM data from HubSpot synced into Postgres for the app or reporting. - ERP data from NetSuite such as customers, orders or invoices. - One-off scripts that copy data on a schedule and fail silently. - Webhooks that update tables when records change in another system. Stacksync syncs Postgres with HubSpot, NetSuite and other business systems in real time and in both directions, so these integrations can move to the same place as the Salesforce sync instead of being rewritten one by one. ## In what order should you cut over? 1. 01 Freeze writes to synced tables Stop the app from writing to tables Heroku Connect manages. 2. 02 Stop Heroku Connect Prevent a second sync from writing during the switch. 3. 03 Finish the database move Take the final data move to the new Postgres. 4. 04 Enable Stacksync Start the sync and confirm existing rows are matched, not duplicated. 5. 05 Switch traffic Point domains to the app on the new platform. 6. 06 Reopen writes and verify Test a create and an update in each direction. Then, after a stable period, decommission Heroku resources. If you are building this checklist now, [book a demo](https://www.stacksync.com/book-a-demo) to go through the Heroku Connect section with our team. FAQ ## Frequently asked questions | | | | --- | --- | | What should a Heroku exit checklist include? | Apps and dynos, Heroku Postgres, add-ons, pipelines and deploy workflows, config vars, domains, and any Heroku Connect mappings to Salesforce. | | Who handles Heroku Connect in a Heroku exit? | Stacksync replaces Heroku Connect with real-time, two-way sync between Salesforce and Postgres. Build.io handles the app and platform move. | | Is Heroku Connect easy to forget during a migration? | It is often overlooked because it runs in the background. If it is missed, the new database stops receiving Salesforce changes after cutover. | | Can I migrate HubSpot or NetSuite data the same way? | Yes. Stacksync syncs Postgres with HubSpot, NetSuite and other systems, so those integrations can move to the same platform. | | When should I turn off Heroku Connect? | Only after the replacement sync is live in production and record counts and write-backs have been verified. | ## Explore these integrations and topics - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Build.io + Stacksync FAQ: Planning a Heroku Exit 5 min read read](https://www.stacksync.com/blog/build-io-stacksync-heroku-exit-faq) [App tips Build.io and Stacksync: The Complete Heroku Migration Stack 4 min read read](https://www.stacksync.com/blog/build-io-stacksync-heroku-migration-stack) [App tips Heroku Alternatives for Salesforce-Connected Apps 5 min read read](https://www.stacksync.com/blog/heroku-alternatives-for-salesforce-connected-apps) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)