@kapa.ai I want to move some tables that are already replicated (to the destination) on an existing connection to a new connection for the same destination. Is there a way to do this in a way that the new connection does not result in the tables being rebuilt?

Yes, this is possible for incremental sync mode streams by transferring the connection state from the existing connection to the new one. Here's how: Steps to Move Tables Without Rebuilding 1. Create the new connection pointing to the same destination, using the same source. To avoid table collisions, use a different

Default Schema

(namespace) initially — you can adjust this later. 2. Copy the connection state from the existing connection: ◦ Go to the existing connection → Settings tab → Advanced settings. ◦ Find the connection state and copy it to your clipboard. 1. Apply the state to the new connection: ◦ Go to the newly created connection → Settings → Advanced. ◦ Replace the state with the copied contents and click Update State. ◦ This tells Airbyte where the sync left off, so historical data is not re-replicated. [Incremental Dual-Write Steps] 1. Enable the new connection. It will resume from where the old connection left off. 2. Disable or remove the streams from the old connection once you've confirmed the new connection is working correctly. Important Caveats • This approach works for incremental sync modes. For full refresh streams, there is no state to transfer — the new connection will simply do a full sync on first run, which means the tables will be rebuilt. [Dual-Write Overview] • Handle state updates with extreme care. Incorrect state values can break syncs and may require a full reset to fix. Only make changes as directed. • States are managed at the connection level, not the destination level, so two connections pointing to the same destination will have independent states. [Forum Discussion] image 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.