migrate-airbyte-connector

Convert Airbyte source connectors to Fivetran Connector SDK projects.

70|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/fivetran/connector_sdk_tools --skill migrate-airbyte-connector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-airbyte-connector
Source: https://github.com/fivetran/connector_sdk_tools/tree/main/claude-code/skills/migrate-airbyte-connector
Command: npx skills add https://github.com/fivetran/connector_sdk_tools --skill migrate-airbyte-connector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of rewriting Airbyte source connector logic to be compatible with Fivetran's Connector SDK, cutting migration time from days to minutes and reducing the risk of missing critical sync behavior like incremental cursors or stream-level error handling.

Core Features & Use Cases

  • Full Concept Mapping: Automatically translates Airbyte configuration schemas, stream definitions, state shapes, incremental cursors, and error handling logic to their CSDK equivalents.
  • Multi-Source Support: Handles Python CDK sources, low-code YAML manifests, and standalone Airbyte protocol artifacts (spec, catalog, state files) as migration inputs.
  • Use Case: If you have an existing Airbyte source-github connector with nested auth, stream slices, and incremental sync that you want to port to Fivetran, this skill generates a fully functional CSDK project that preserves all original behavior.

Quick Start

Use the migrate-airbyte-connector skill to port your existing Airbyte Python CDK source connector to a Fivetran Connector SDK project while preserving all stream schemas, sync modes, and authentication logic.

Frequently Asked Questions about migrate-airbyte-connector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert an Airbyte Python CDK source connector to Fivetran Connector SDK?

Migrating an Airbyte Python CDK source connector to Fivetran CSDK involves translating configuration schemas, stream definitions, and sync modes into valid CSDK project files. This skill automates that conversion while preserving original authentication and error handling logic.

Can I migrate Airbyte low-code YAML manifests to Fivetran CSDK?

Migrating Airbyte low-code YAML manifests to Fivetran CSDK is supported. The skill processes YAML manifests alongside Python CDK sources and standalone protocol artifacts to translate stream schemas and incremental cursors into valid CSDK code.

Does the migration preserve incremental sync logic and state files from Airbyte?

Migration preserves incremental sync logic and state files by porting Airbyte cursor definitions and state shapes directly to their Fivetran CSDK equivalents. This ensures continued incremental data extraction without losing sync progress or stream-level error handling.

What is the best way to port Airbyte stream schemas and authentication to Fivetran?

Porting Airbyte stream schemas and authentication to Fivetran is best handled by automatically translating stream definitions, nested auth configurations, and stream slices into CSDK-compatible code. This approach generates a fully functional project that maintains original connector behavior.

Do I need Airbyte protocol artifacts like spec and catalog files to use a connector migration tool?

You do not strictly need Airbyte protocol artifacts like spec and catalog files to use a connector migration tool, but providing them as inputs alongside Python CDK sources or YAML manifests improves configuration mapping and schema translation accuracy for the generated CSDK project.