Migrating from Stitch to Airbyte for Stripe data integration

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

The user is looking for a way to avoid creating a new dataset in BigQuery for Stripe data when migrating from Stitch to Airbyte.


Question

Hi everyone, has anyone shifted from Stitch to Airbyte here? I have a couple of questions.
• We were fetching stripe data using stitch into BQ. Turns out Airbyte table schema of stripe is different from what we had in stitch. We wanted to resume our EL process from the point we stopped using stitch. Is there any way we can avoid creating a new dataset in BQ for Stripe and just use our old dataset (created using stitch)?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["stitch", "airbyte", "stripe", "data-integration", "bigquery", "schema", "migration"]
2

Not a data engineer.

From what I’ve seen folks do, you’d want a dbt layer on top of airbyte final tables in BQ to cast data into the same shape you’ve had before, so your downstream models stay stable.

That would mean that you eat the cost of new full sync of data in BQ.