Migrate Fivetran connectors to Bruin ingestr

What

Migrate one Fivetran connector into a new Bruin project without treating the migration as an automatic cutover. You will scaffold the migration workspace, keep source and destination credentials local, give a coding agent the installed migration prompt, and review the ingestr assets it drafts before any destination write.

The template imports one Fivetran connector configuration with read-only API requests. It records the migration decisions in plan.md and keeps the redacted capture under .artifacts/.

How

Install or update Bruin, then enable the built-in Bruin MCP server in your coding agent. Create the migration template with bruin init migration-fivetran my-migration-project, add the named source and destination connections plus the Fivetran API credentials in .bruin.yml, and start a fresh agent chat from the project root.

The agent imports the selected Fivetran configuration, asks for the connection names and target tables it cannot infer, then drafts a Bruin ingestr pipeline. It pauses before connection testing and before any destination write. You approve the isolated v0 run only after reviewing the plan and generated assets.

The migration project

The template starts with the prompt, plan, and importer skill. The agent adds the final ingestion assets after it has imported the selected connector and you have answered the mapping questions.

my-migration-project/
├── .agents/
│   └── skills/
│       └── bruin-fivetran-migrator/
│           ├── SKILL.md                         # template: migration rules
│           └── import_fivetran.py               # template: read-only Fivetran importer
├── .artifacts/                                  # generated, Git-ignored redacted captures
├── .bruin.yml                                   # local source, destination, and Fivetran secrets
├── .gitignore
├── fivetran-bruin-prompt.md                     # template: instructions for the coding agent
├── plan.md                                      # template: decisions, TODOs, and run evidence
└── bruin/
    ├── pipeline.yml                             # template: empty Bruin pipeline
    └── assets/
        ├── placeholder                          # template marker
        └── bruin_ingestr/                       # drafted after review, example output
            ├── customers_bruin.asset.yml
            ├── order_items_bruin.asset.yml
            ├── orders_bruin.asset.yml
            └── products_bruin.asset.yml

The names under bruin_ingestr/ are an example from a completed migration. Your agent should create assets for the tables, target schema, and destination names you approve.