Hi, I'm working on replacing Stitch with Airbyte (self-hosted) in a Postgres -> Replicator -> Snowflake setup. Some data from Postgres has previously been deleted and retained in Snowflake, to keep the Postgres instance size down. Because of this, it would be helpful if I could use Airbyte with the existing Snowflake target DB instead of starting with a clean slate with Airbyte. I've searched online and in Slack for notes about a Stitch -> Airbyte changeover but have not been able to find any notes on whether others have been successful with this. Has anyone been able to do this or have thoughts on why this would be a bad idea, as opposed to starting over with Airbyte (e.g., the metadata that Stitch and Airbyte store in tables may conflict)? Thanks!

Hi @Justin Cortex I'm not aware of Stitch's specifics, but I'd suggest the following flow: Option A to keep your existing table: 1. Try a sync from Postgres to a new Snowflake table with Airbyte's basic normalization and check how far this is from your existing Snowflake table in term of schema. 2. Write a custom transformation in DBT (tutorial here) to adjust the schema to the existing one in your destination 3. Add this transformation to a PG to your existing snowflake table connection Option B to migrate your existing table to a new "airbyte" one: 1. Create a connection from Postgres to a new Snowflake table using basic normalization 2. Migrate data from your "legacy" Snowflake table to the new one with SQL in Snowflake to adapt to Airbyte's normalization schema

Thank you for the suggestions! I will do some experimentation based on these.