How do I move a connector between environments?

Contact us at [email protected] with the connectors you want moved and the target environment, and we'll move them for you. You can't move a connector from the dashboard yourself.

What stays the same

A moved connector keeps its authorization and every ID you've stored, so your customer doesn't need to reconnect.

What you need to change

1. Switch your API calls for that connector to the target environment's API key. The old environment's key returns a 401 for a moved connector.

2. If you moved a connector to Development, you’ll need to trigger syncs manually going forward. Development connectors don't sync on a schedule.

3. If you moved a connector to Production, it picks up the 24-hour sync schedule and counts toward your plan.

Moving many connectors at once

When most of your connectors should move, it's quicker to send us the short list of connectors that should stay where they are. We'll confirm the final list with you before making the switch.

If a connector still appears in the old environment

The Connectors tab can include connectors that never finished authorizing. Filter the list to active connectors to check what actually moved.

Setting up a new Production connector instead

If you'd rather start fresh, create a new connector in Production from the dashboard using the customer's credentials. A new connector runs a fresh initial sync and gets new Bindbee IDs for every record, so update any IDs you stored from the old one.