migrate-functions-connector

What problem does it solve?

Manually porting a Fivetran Functions connector (hosted on AWS Lambda, Azure Functions, Google Cloud Functions, or other serverless platforms) to a native Fivetran Connector SDK (CSDK) project is time-consuming, error-prone, and requires deep expertise in both the Functions connector framework and CSDK rules, leading to lost sync logic, broken state handling, and invalid schema definitions if done incorrectly.

Core Features & Use Cases

• Automated Concept Mapping: Provides an explicit mapping of all Functions connector concepts (request.secrets, request.state, insert/delete/softDelete outputs, hasMore pagination) to their CSDK equivalents, eliminating guesswork during translation.
• Guided End-to-End Workflow: Walks users through inventorying the source Functions connector, porting implementation code to Python, updating configuration and dependency files, and validating the migrated CSDK project against SDK constraints.
• Use Case: If you have an existing AWS Lambda Fivetran Functions connector that syncs customer data with incremental state and soft-delete support, this skill will automatically convert it to a valid CSDK connector while preserving all original sync behavior and state semantics.

Quick Start

Use the migrate-functions-connector skill to port your existing Fivetran Functions connector to a Connector SDK project, following the guided workflow to preserve all sync logic, state handling, and operation mappings.