We started Sequin to give developers a better way to integrate with their data. We’re deeply grateful for the trust you’ve placed in us over the years. That’s what makes this a hard message to write: Sequin has been acquired, and as a result, our services will be shut down on October 23, 2025. We know this is a disruptive change. Here’s what’s ahead:
  • Today, August 21, 2025, we are announcing the shutdown. All subscriptions will be automatically canceled and we will issue refunds for unused months if you are on an annual plan.
  • Between now and October 23, 2025, even though your subscription has been canceled, Sequin services will continue as normal.
  • On October 23, 2025, Sequin as a service and a company will dissolve. Sequin’s servers will be turned off, syncs will stop, and Sequin-hosted databases will be shutdown. For your security, all data will be permanently deleted.
We know this is unexpected and a tight timeline, so we’ve partnered with Stacksync to provide a seamless path to migrate your syncs. Stacksync provides the same real-time, two-way syncs you’ve come to expect from Sequin with additional features you’ll find valuable such as more connectors (NetSuite, Shopify, etc.), sync triggers, and an integrated workflow automation suite. We are also here to help and are committed to supporting you during the migration process. Send us an email at support@sequin.io and we’ll work with you to migrate.

Migrate to Stacksync

We’ve partnered closely with the team at Stacksync to provide a seamless migration of your syncs. Stacksync is generously honoring existing Sequin pricing for comparable syncs and providing white-glove migration support. Stacksync provides the same real-time, two-way syncs you’ve come to expect from Sequin. We’ve personally reviewed their technology and believe it’s the best alternative for you. To make the migration as seamless as possible, we’ve built an integration that allows Stacksync to import your Sequin sync configuration and create new syncs that match your existing schema.

Migration checklist

  1. Visit the Stacksync migration page: https://stacksync.com/sequin.
  2. Create an account and a Stacksync engineer will contact you directly.
  3. You’ll connect your sources and Postgres database to Stacksync and then provide them with your Sequin API key (which you’ll find in the console) so the Stacksync team can access your Sequin configuration.
  4. Stacksync will import your sync configuration. Validate your new syncs with Stacksync’s team to ensure they match your existing schema.
  5. Decommission your Sequin syncs before October 23, 2025.
Typical migration timeline: Most customers can complete migration in 3–5 business days with Stacksync’s white-glove support.

Getting your Sequin API key (to give to Stacksync)

We’ve built an integration to export your sync configurations to Stacksync. For security, Stacksync needs you to provide them with a Sequin API key to access these configurations. You can get your API key by:
  1. Log into the Sequin console.
  2. Clicking on your user profile in the top right corner and select App key.
  3. Generate an API key and share it with the team at Stacksync.

Migration tips

We suggest running both Sequin and Stacksync concurrently to validate everything is working before you turn off your Sequin syncs. Here is how:
  • New Schema: You can configure Stacksync to sync your data to a new schema in your existing Postgres db.
  • Rate limits: While you run both Sequin and Stacksync, turn down your rate limits to ensure you don’t hit your limits.
  • Data validation: Check that all the data from your source is in the new Stacksync schema. A SELECT count(*) is an easy way to do this.
  • Code validation: Finally, verify that any code or workflows now point to the Stacksync schema and work properly.

Support During Migration

We’re here to help through this transition.
  • Support window: until October 23, 2025.
  • Response time: expect replies within 1 business day.
  • Contact us: support@sequin.io
Stacksync’s team will also provide white-glove migration support alongside ours: ruben@stacksync.com

FAQ