To migrate your pipeline to another Airbyte instance while keeping the already synced data, you can follow these steps: 1. Export the configuration from your current Airbyte instance (Instance A). 2. Disable Instance A. 3. Import the configuration to the new Airbyte instance (Instance B) pointing to the same database. Here's the recommended process from a [forum discussion](https://discuss.airbyte.io/t/1768):

1. export configuration from Instance A 2. Disable instance A 3. import configuration to Instance B pointing to the database

Since your source connector is Hubspot and your destination is BigQuery, the data in BigQuery will remain intact during this process. After migrating the pipeline, you can continue syncing data from Hubspot to BigQuery using the new Airbyte instance.

To export the configuration of your Airbyte instance, you can use the Octavia CLI tool. Follow these steps: 1. Install Octavia CLI by following the instructions in the [GitHub repository](https://github.com/airbytehq/airbyte/tree/master/octavia-cli). 2. Configure Octavia CLI to target your Airbyte instance by setting the

AIRBYTE_SERVER_URL

and

AIRBYTE_API_KEY

environment variables. 3. Use the

octavia export

command to export your Airbyte configuration to a local directory:

bash octavia export --output-dir <path_to_output_directory>

This will create a directory structure containing your Airbyte configuration files in YAML format. For more information on using Octavia CLI, refer to the [Version control Airbyte configurations with Octavia CLI tutorial](https://airbyte.com/tutorials/version-control-airbyte-configurations).

@kapa.ai how do i generate an airbyte api key?

Hmm, I don't know enough to give you a confident answer yet. However, you can refer to the [Airbyte documentation](https://docs.airbyte.com) for more information on various topics related to Airbyte.

Yes, there is another way to migrate the configuration using the Airbyte UI or API. Here are the steps to export and import the configuration using the Airbyte UI: 1. Navigate to the Admin page in the UI. 2. Go to the Configuration Tab. 3. Click "Export" to download a compressed backup archive (gzipped tarball) of all your Airbyte configuration data and sync history locally. Note that any secrets you have entered into Airbyte will be in this archive, so treat it as a secret. 4. To import the configuration to another Airbyte instance, navigate to the Admin page in the UI of the new instance. 5. Go to the Configuration Tab and click on "Import". 6. Upload your exported archive. If you prefer to use the API instead of the UI, follow these instructions: 1. Export the archive using the following curl command:

bash curl -H "Content-Type: application/json" -X POST localhost:8000/api/v1/deployment/export --output /tmp/airbyte_archive.tar.gz

2. Import the archive to the new instance using the following curl command:

bash curl -H "Content-Type: application/octet-stream" -X POST --data-binary "@/tmp/airbyte_archive.tar.gz" localhost:8000/api/v1/deployment/import

Replace

localhost:8000

with the appropriate URL for your Airbyte instances. For more information on exporting and importing configurations, refer to the [Upgrading Airbyte documentation](https://docs.airbyte.com/operator-guides/upgrading-airbyte).

The Admin page should be available for both Airbyte Cloud and open-source users. If you're not seeing the Admin page in the UI, it's possible that your Airbyte instance is not running correctly or there might be an issue with the UI. To troubleshoot, you can try restarting the Airbyte server. If you're using a local

airbyte-platform

repository, run the following commands:

bash VERSION=dev docker compose down -v   VERSION=dev docker compose up

If you're still having issues, consider reaching out to the Airbyte community on [Slack](https://airbytehq.slack.com) or the [Airbyte forum](https://discuss.airbyte.io) for further assistance.

Please ignore me, I was not mounting the current directory into docker properly, it works fine now 🙂