tarcisio.pacheco
10/20/2026, 2:34 PMkapa.ai
10/20/2026, 2:34 PMoctavia init.
2. Run octavia import all to retrieve all sources, destinations, and connection configurations as YAML files. [Octavia tutorial]
3. Edit the secrets in the imported files. Octavia replaces secrets with ********** on import, so you must fill them in again, along with any environment variables that differ between instances. [Octavia tutorial]
4. Apply the configuration to the new instance:
octavia apply –airbyte-url http://production.myairbyte.com –force –airbyte-username YOUR_USERNAME –airbyte-password YOUR_PASSWORD
[Octavia tutorial]
Option 2: Database backup/restore (Docker to Docker) A community forum post describes moving an entire instance by dumping and restoring the Airbyte database. It was only validated for Docker to Docker, and both instances should run the same Airbyte version. [Forum tutorial]
1. On the old instance, stop all services and start only the database: docker-compose down, then docker-compose up -d db.
2. Create the backup with docker exec airbyte-db pg_dump -U docker airbyte > airbyte_backup.sql.
3. Copy the file to the new server, start Airbyte once, then stop it and start only the database.
4. Drop and recreate the database, then restore the dump:
◦ docker exec airbyte-db psql -U docker -c 'drop database airbyte'
◦ docker exec airbyte-db psql -U docker -c 'create database airbyte with owner docker;'
◦ cat airbyte.sql | docker exec -i airbyte-db psql -U docker -d airbyte
1. Run docker-compose up -d, then trigger all connections again to recreate their Temporal workflows. You can use the Airbyte API for that. [Forum tutorial]
The knowledge sources do not cover exporting a single connection, or migrating on Kubernetes or with an external database. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.