Airbyte Migration Questions

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

Summary

User inquires about the latest stable version of Airbyte for migration, documentation for the migration process, and common challenges faced during migration.


Question

Hello everyone! We use Airbyte to extract data from multiple sources for our clients, with over 5,000 connections running daily on an Airbyte cluster deployed on Kubernetes.

Our sources include
• Amazon Ads
• Google Ads
• Facebook Ads
• Shopify
• WooCommerce
• Amazon SP.
Currently, we’re on version : 0.39.42-alpha.

Could anyone help with the following questions?

  1. What is the latest stable Airbyte version recommended for migration?
  2. Is there any standard documentation to guide the migration process?
  3. What are common challenges during migration, and is there documentation on resolutions for these?
    Thanks!

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

['airbyte', 'migration', 'version', 'documentation', 'challenges']
2
  1. I’d recommend upgrading to 1.0.0
  2. I haven’t seen one
  3. Most of the time tweaking configuration to make it work. I’d recommend incremental upgrades and separate environment for testing changes.
    You can check threads in this answer
    https://airbytehq.slack.com/archives/C021JANJ6TY/p1730283137872169?thread_ts=1730279376.079549&cid=C021JANJ6TY

Sidenote: storing configuration of sources/destinations/connections as terraform code might be useful.

3

As I checked this was a path of upgrades in my team 0.50.30 - 0.50.38 - 0.50.45 - 0.50.51 - 0.60.1 - 0.63.3 - 0.63.4 - 0.64.3 - 1.0.0

4
  1. I’d recommend upgrading to 1.0.0
  2. I haven’t seen one
  3. Most of the time tweaking configuration to make it work. I’d recommend incremental upgrades and separate environment for testing changes.
    You can check threads in this answer
    https://airbytehq.slack.com/archives/C021JANJ6TY/p1730283137872169?thread_ts=1730279376.079549&cid=C021JANJ6TY

Sidenote: storing configuration of sources/destinations/connections as terraform code might be useful.

5

As I checked this was a path of upgrades in my team 0.50.30 - 0.50.38 - 0.50.45 - 0.50.51 - 0.60.1 - 0.63.3 - 0.63.4 - 0.64.3 - 1.0.0