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, you can move tables/streams to a new connection pointing to the same destination without rebuilding or re-syncing historical data by copying the connection state for incremental streams [Forum Post: Questions on Switching Connectors and Syncing YAML in Airbyte Cloud; Forum Post: Using State from Existing Connection for New Connection in API Extraction]. Here is how you can do this: 1. Ensure the destination configuration matches When creating the new connection, make sure the destination settings (such as Destination Namespace, Stream Prefix, sync modes, and table structure) match the original connection so that data is written to the exact same destination tables [Forum Post: Questions on Switching Connectors and Syncing YAML in Airbyte Cloud]. 2. Copy the Connection State from the original connection 1. In the Airbyte UI, open your existing connection [Documentation Platform > Cloud > Managing-airbyte-cloud>]. 2. Go to the Settings tab and expand the Advanced section [Documentation Release_notes > Self-managed > Upgrading to Destinations V2 > Advanced Upgrade Paths > Upgrading Connections One by One with Dual-Writing > Additional Steps for Incremental Sync Modes>]. 3. In the Connection State editor, locate and copy the JSON state object (cursor information) corresponding to the specific streams/tables you are moving [Documentation Release_notes > Self-managed > Upgrading to Destinations V2 > Advanced Upgrade Paths > Upgrading Connections One by One with Dual-Writing > Additional Steps for Incremental Sync Modes>]. 3. Apply the state to the new connection 1. Open the new connection in the Airbyte UI. 2. Go to the Settings tab > Advanced > Connection State [Documentation Platform > Cloud > Managing-airbyte-cloud>]. 3. Paste the copied stream state JSON into the state editor for the respective streams [Documentation Release_notes > Self-managed > Upgrading to Destinations V2 > Advanced Upgrade Paths > Upgrading Connections One by One with Dual-Writing > Additional Steps for Incremental Sync Modes>]. 4. Click Update State and confirm the changes [Documentation Platform > Cloud > Managing-airbyte-cloud>]. 4. Adjust the original connection and run the sync 1. Disable or deselect the moved tables in the original connection so they are no longer synced twice. 2. Run a sync on your new connection. It will pick up from the existing cursor state and only fetch new/incremental records rather than performing a full refresh [Documentation Platform > Cloud > Managing-airbyte-cloud>; Documentation Release_notes > Self-managed > Upgrading to Destinations V2 > Advanced Upgrade Paths > Upgrading Connections One by One with Dual-Writing > Additional Steps for Incremental Sync Modes>]. > Caution: Updates to connection state should be handled with extreme care, as invalid state entries can cause sync failures [Documentation Platform > Cloud > Managing-airbyte-cloud>]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

@kapa.ai can you make shorter

Here is a concise summary of the steps: 1. Match settings: In the new connection, ensure the destination namespace, table prefix, and sync modes match the original connection so data writes to the same tables [Forum Post: Questions on Switching Connectors and Syncing YAML in Airbyte Cloud]. 2. Copy state: Go to your original connection > Settings > Advanced, and copy the stream cursor data from the Connection State field [Manage Connection State; Upgrading to Destinations V2]. 3. Paste state: Open the new connection > Settings > Advanced, paste the state into Connection State, and click Update State [Manage Connection State; Upgrading to Destinations V2]. 4. Sync: Disable the moved streams in the original connection, then run the new connection—it will resume incrementally from the copied state without rebuilding [Manage Connection State; Upgrading to Destinations V2]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

@Finn Bauer use connection state copy from old connection and apply to the new connection before replication start this way only ready the logs