Bruin CLI Step 5 of 5
Migrate Fivetran connectors to Bruin ingestr
Answer connection and table questions
Give concrete answers when the agent asks. These are the usual decisions:
| The agent asks | Give it |
|---|---|
| Which Fivetran connector should I import? | The exact connector name, or preferably the connector ID. Migrate one connector at a time. |
| What are the Bruin connection names? | The source and destination names from .bruin.yml or bruin connections list. |
| Where should the first load land? | An isolated v0 schema and the destination table name for each source table. |
| Which tables should move now? | The selected Fivetran tables and any approved renames, omissions, or destination mappings. |
| How should changes be loaded? | The primary key, incremental key, materialization strategy, and how deletes or history should work. |
| What can the agent run? | The agreed date bounds, source watermark or snapshot boundary, validation checks, and explicit permission for an isolated write. |
When the agent pauses after reviewing the connections, reply with a direct confirmation such as:
AI Prompt
The source connection is source-postgres and the destination connection is analytics-bigquery. The connections are ready. You may test them, but do not write to a destination yet.
Replace those example names with yours. The agent then captures the Fivetran configuration, updates plan.md, and drafts the ingestr assets. Review each asset's source table, destination table, keys, incremental strategy, and any Fivetran behaviour it cannot reproduce before you permit a run.