Downgrading Airbyte from 2.0.1 to 1.8.5 is very likely
not possible without data loss or connection issues. Here's why:
The knowledge sources explicitly mention that starting from Airbyte version 1.8.0,
Flyway database migrations are applied that update the internal schema. Once these migrations run, older binaries (i.e., a downgraded version) can no longer use the updated schema. As one user noted in a GitHub issue:
> "It is not possible to simply downgrade Airbyte to an older version. On my case it was required to deploy a new instance and migrate the connections manually." [
Refresh UI error issue]
This means that after running 2.0.1, the internal Postgres database schema has been migrated forward, and rolling back to 1.8.5 would likely break the application since 1.8.5 binaries cannot interpret the newer schema. What you can do instead 1.
Stay on 2.0.x: If there's a specific issue driving the downgrade, consider checking if a newer patch of 2.0.x resolves it.
2.
Restore from a database backup: If you have a backup of Airbyte's internal Postgres database taken
before the upgrade to 2.0.1, you could restore it and redeploy 1.8.5. The knowledge sources describe a database restoration process for Helm-based deployments [
chart-v2-community], but this would only work if you have a pre-upgrade backup.
3.
Deploy a fresh 1.8.5 instance and migrate manually: As mentioned in the community, you can deploy a new Airbyte instance at 1.8.5 and recreate your sources, destinations, and connections manually. In summary, a seamless in-place downgrade from 2.0.1 to 1.8.5 while preserving all data connections is
not supported due to irreversible database schema migrations. The knowledge sources do not describe any official downgrade path for this scenario. š 0 button š 0 button ā¹ļø
Tip: Mention
@kapa.ai in the thread for follow-ups or
DM the app for
1-to-1 help.