Dan Cook
12/02/2025, 7:31 PMkapa.ai
12/02/2025, 7:31 PMget_source(...). [[PyAirbyte custom source](https://airbyte.com/tutorials/how-to-add-custom-source-to-pyairbyte-using-the-no-code-builder)] - Use the public API / Terraform on a self‑hosted instance to create a “declarative source” from that same YAML (POST /workspaces/{workspaceId}/definitions/declarative_sources). [[1.6 release notes](https://docs.airbyte.com/release_notes/v-1.6#create-custom-connectors-from-yaml-or-docker-images-using-the-api-and-terraform)] So in practice, a migration path looks like: 1. In Airbyte Cloud, open each custom Builder connector and export/download the YAML manifest. 2. On your self‑hosted Airbyte: - Use the appropriate API endpoint or Terraform resource to create a new YAML (declarative) source definition in the target workspace, providing the exported YAML. [[1.6 release notes](https://docs.airbyte.com/release_notes/v-1.6#create-custom-connectors-from-yaml-or-docker-images-using-the-api-and-terraform)] 3. Recreate your sources, destinations, and connections that use this definition (including credentials and sync settings). Caveats based on the sources: - There is no general config export/import from Cloud to self‑hosted; even for OSS → Cloud the guidance is to recreate connections manually. [[Migrate OSS to Cloud](https://discuss.airbyte.io/t/130)] - If you used Connector Builder’s test interface, note it always runs through the Cloud control plane in the US, but that doesn’t affect the self‑hosted runtime once you deploy the YAML there. [[Data residency](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-data-residency)] If you need exact API payload examples for creating the declarative source on self‑hosted, I don’t have them in these docs and would point you to the API reference linked from the release notes.