migrating toBrowse playbooks
← All playbooks
ELT and data integration migration

Airbyte → Fivetran

Move sources, connectors, and authentication, destinations, schemas, and namespaces, streams, tables, fields, and selections, incremental cursors and replication state, historical backfill and reset behavior, transformations and normalization, schedules, concurrency, and rate limits, custom connectors and connector code from Airbyte to Fivetran with a reversible cutover, explicit exception ledger, and evidence-backed verification.

Typical timeline15–45 business days70–180 hours active work
Statusneeds review
Source profileAirbyte documentation reviewed 2026-07-20
Destination profileFivetran documentation reviewed 2026-07-20
Documentation date
Review window
Evidence2 sources
This route needs review.Use it as a planning baseline, then verify the dated sources and test with representative data before production.
Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Airbyte

Reasons to stay
  • A broad open-source connector catalog offers deployment and customization flexibility
  • Managed analytical storage and compute support large-scale SQL, governance, and reporting
Reasons to leave
  • Connector quality, upgrades, normalization, and self-hosted operations require active ownership
  • SQL dialects, security models, pipelines, workload tuning, and historical evidence create deep lock-in
New platform

Fivetran

What gets better
  • Highly managed connectors and schema evolution minimize day-to-day pipeline maintenance
  • Managed analytical storage and compute support large-scale SQL, governance, and reporting
What gets worse
  • Consumption pricing, connector behavior, and limited low-level control can constrain large or unusual workloads
  • SQL dialects, security models, pipelines, workload tuning, and historical evidence create deep lock-in
Best of the move

Fivetran: Highly managed connectors and schema evolution minimize day-to-day pipeline maintenance. This removes a major source-side concern: Connector quality, upgrades, normalization, and self-hosted operations require active ownership.

Worst of the move

What you lose: A broad open-source connector catalog offers deployment and customization flexibility. What you inherit: Consumption pricing, connector behavior, and limited low-level control can constrain large or unusual workloads.

Connected catalog

2 destinations are documented from Airbyte. Compare nearby routes before committing.

Also from Airbyte
Also moving to Fivetran
Jump to a section
01At a glance

Know the shape of the move.

Transfer outcome10 features audited
Transfer outcome distributionClean transfer: 0, Partial transfer: 2, Manual rebuild: 6, Not transferred: 2.
Clean0
Partial2
Manual6
Lost2
Mapping route7 of 9 fields have a destination path

This timeline assumes

  • Up to 500 connectors, 10,000 streams, 100 destinations, and 10 TB of daily replicated change
  • Administrators control both Airbyte and Fivetran, including billing, identity, APIs, integrations, and export permissions.
  • Airbyte remains intact and recoverable until Fivetran completes one representative operating cycle.
  • A production-shaped pilot includes every object type, access class, edge case, and failure path.
  • The migration team preserves stable source identifiers and records durable evidence for every blocking check.
02What transfers

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

ItemOutcomeImpactWhat happensMitigation
Sources, connectors, and authenticationmanualcriticalConnector availability, auth methods, network paths, versions, and supported objects differ. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Inventory and rebuild sources, connectors, and authentication, then test normal, edge, failure, and rollback behavior.
Destinations, schemas, and namespacesmanualcriticalDestination support, naming, dataset layout, normalization, and ownership require redesign. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Inventory and rebuild destinations, schemas, and namespaces, then test normal, edge, failure, and rollback behavior.
Streams, tables, fields, and selectionspartialcriticalDiscovery catalogs, inclusion rules, field selection, and unsupported types do not map one-to-one. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Map streams, tables, fields, and selections explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Incremental cursors and replication statelostcriticalProvider-specific cursors, offsets, logs, and checkpoints cannot safely become destination state. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Archive incremental cursors and replication state as dated source evidence and define the new destination baseline.
Historical backfill and reset behaviormanualcriticalResets, re-syncs, deduplication, history modes, and source load require controlled planning. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Inventory and rebuild historical backfill and reset behavior, then test normal, edge, failure, and rollback behavior.
Transformations and normalizationmanualcriticalGenerated schemas, SQL transformations, dbt integration, typing, and deduplication models differ. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Inventory and rebuild transformations and normalization, then test normal, edge, failure, and rollback behavior.
Schedules, concurrency, and rate limitsmanualhighSync frequency, parallelism, API quotas, retries, and maintenance windows change. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Inventory and rebuild schedules, concurrency, and rate limits, then test normal, edge, failure, and rollback behavior.
Custom connectors and connector codepartialcriticalSDKs, manifests, packaging, secrets, tests, and deployment environments are not portable. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Map custom connectors and connector code explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Logs, alerts, failures, and sync historylosthighHistorical run logs, rejected rows, alert state, and operational baselines remain source-native. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Archive logs, alerts, failures, and sync history as dated source evidence and define the new destination baseline.
Users, workspaces, permissions, and billingmanualhighWorkspace structure, role controls, usage metering, and pricing units use different models. A successful bulk job therefore does not prove semantic parity between Airbyte and Fivetran.Inventory and rebuild users, workspaces, permissions, and billing, then test normal, edge, failure, and rollback behavior.
03Field and feature mapping

Where each thing goes.

SourceDestinationMethodNotes
Airbyte: Sources, connectors, and authenticationFivetran: approved sources, connectors, and authentication representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for sources, connectors, and authentication.
Airbyte: Destinations, schemas, and namespacesFivetran: approved destinations, schemas, and namespaces representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for destinations, schemas, and namespaces.
Airbyte: Streams, tables, fields, and selectionsFivetran: approved streams, tables, fields, and selections representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for streams, tables, fields, and selections.
Airbyte: Incremental cursors and replication stateNo destinationunsupportedRetain immutable source evidence; do not manufacture destination-native history.
Airbyte: Historical backfill and reset behaviorFivetran: approved historical backfill and reset behavior representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for historical backfill and reset behavior.
Airbyte: Transformations and normalizationFivetran: approved transformations and normalization representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for transformations and normalization.
Airbyte: Schedules, concurrency, and rate limitsFivetran: approved schedules, concurrency, and rate limits representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for schedules, concurrency, and rate limits.
Airbyte: Custom connectors and connector codeFivetran: approved custom connectors and connector code representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for custom connectors and connector code.
Airbyte: Logs, alerts, failures, and sync historyNo destinationunsupportedRetain immutable source evidence; do not manufacture destination-native history.
04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Preserve Airbyte data, configuration, access, and operating evidence before any destination write.

  1. Export every available Airbyte object and binary in scope, including sources, connectors, and authentication, destinations, schemas, and namespaces, streams, tables, fields, and selections, incremental cursors and replication state.
  2. Capture configuration and runtime dependencies for historical backfill and reset behavior, transformations and normalization, schedules, concurrency, and rate limits, custom connectors and connector code.
  3. Record counts, sizes, owners, timestamps, access classes, financial totals where applicable, and known exceptions.
  4. Hash immutable exports, record tool versions and commands, and transform working copies only.

Proof to capture: A signed manifest accounts for every scoped record class, configuration object, binary, count, total, exception, and hash.

Transformation · Version-controlled migration workbook, SQL, or typed transformation code

Identity, schema, and disposition registry

Preserve stable identity and make every mapping or exclusion reviewable.

  1. Inventory source types, identifiers, owners, states, and access.
  2. Define one approved destination representation or explicit archive decision.
  3. Reject unmapped critical items and produce an exception ledger.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Official APIs, provider importers, checksums, and reconciliation scripts

Dependency-ordered migration package

Load prerequisite identities and configuration before dependent records and runtime actions.

  1. Normalize encoding, timestamps, identifiers, nulls, and destination limits.
  2. Run a representative pilot and retain request, response, and rejection evidence.
  3. Reconcile the final delta before enabling destination production writers.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Import

A completed migration hides missing or altered sources, connectors, and authentication

criticalpossible likelihood

Headline counts look plausible while semantic, access, or relationship checks fail.

Consequence
The destination becomes authoritative with incomplete or misleading business data.
Mitigation
Reconcile by type, state, owner, access class, and representative record rather than total count alone.

Stop if: Any critical item lacks a verified destination, approved transformation, explicit exclusion, or recoverable archive.

Cutover

Airbyte and Fivetran both perform production actions

criticalpossible likelihood

Users, schedules, webhooks, integrations, or traffic continue changing both systems.

Consequence
State diverges or customers receive duplicate, contradictory, or unsafe actions.
Mitigation
Freeze source writers and transfer one production owner at a time with an approved rollback.

Stop if: An unapproved source writer or destination duplicate action appears after the freeze.

Verification

Destination access or security is broader than approved

criticalpossible likelihood

A representative restricted user can read, change, export, or trigger an unauthorized item.

Consequence
Confidential, regulated, financial, or security-sensitive data is exposed or changed.
Mitigation
Apply least privilege before bulk loading and test every access class using ordinary identities.

Stop if: Any unauthorized read, write, export, administrative action, or secret access succeeds.

06Precise timeline

Do the work in this order.

Estimate forUp to 500 connectors, 10,000 streams, 100 destinations, and 10 TB of daily replicated change
Total elapsed15–45 business days
Active work70–180 hours
BufferAdd time for large Airbyte exports, destination rate limits, unsupported features, identity exceptions, regulated data, or a strict downtime objective.
01
Days 1–4Inventory and decisions2–4 days
02
Days 3–8Backup and reconcile2–5 days
03
Days 6–20Map, transform, and pilot5–12 days
04
Days 18–35Bulk load, final delta, and switch2–8 days
05
Days 25–45Observe and close7–14 days
  1. Days 1–4 · inventory

    Inventory and decisions

    8–16 hours active2–4 days elapsedOwner, legal, security, and finance review waiting
    • Inventory Airbyte data, configuration, identities, integrations, limits, and billing.
    • Approve scope, owners, mappings, exclusions, acceptance thresholds, and rollback authority.

    Depends on: Airbyte and Fivetran administrator access

    Stop / go checkpoint

    Export?

    Go when: Every critical item and production action has an owner and disposition.

    Stop when: Authority, retention, billing, access, or system ownership is unclear.

  2. Days 3–8 · backup

    Backup and reconcile

    8–20 hours active2–5 days elapsedProvider export processing waiting
    • Create immutable data, configuration, binary, and audit exports.
    • Reconcile source counts, totals, sizes, access classes, and hashes.

    Depends on: Approved inventory and retention location

    Stop / go checkpoint

    Transform?

    Go when: The signed source manifest and exports agree.

    Stop when: Any critical dataset, binary, configuration, or recovery path is absent.

  3. Days 6–20 · pilot

    Map, transform, and pilot

    25–70 hours active5–12 days elapsedDestination processing and owner review waiting
    • Configure Fivetran and transform a production-shaped pilot.
    • Test normal records, every feature class, edge cases, permissions, failures, and rollback.

    Depends on: Verified source backup and approved mapping registry

    Stop / go checkpoint

    Scale?

    Go when: Every pilot mapping and blocking verification check passes.

    Stop when: Any critical invariant, access boundary, or production action lacks a safe destination.

  4. Days 18–35 · cutover

    Bulk load, final delta, and switch

    20–55 hours active2–8 days elapsedImports, propagation, indexing, or synchronization waiting
    • Freeze production writes and automated actions in Airbyte.
    • Apply and reconcile the final delta, switch ownership to Fivetran, and run all blocking checks.

    Depends on: Passed pilot, stakeholder go decision, and rehearsed rollback

    Stop / go checkpoint

    Open production?

    Go when: Fivetran is the sole production owner and every critical exception is resolved.

    Stop when: A source writer remains active, a blocking check fails, or rollback is unavailable.

  5. Days 25–45 · observe

    Observe and close

    9–19 hours active7–14 days elapsedRepresentative operating-cycle evidence waiting
    • Monitor correctness, access, failures, latency, delivery, cost, and user outcomes.
    • Sign the verification report and close rollback only after stable evidence.

    Depends on: Verified cutover

    Stop / go checkpoint

    Close rollback?

    Go when: No trigger occurs during the approved observation period.

    Stop when: Data, access, delivery, routing, cost, or business results regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Fivetran the only production system without losing the final Airbyte delta.

Recommended window: A low-volume weekday morning with platform, data, security, networking, finance, and business owners available.

  1. Freeze user, integration, schedule, and API writes in Airbyte.
  2. Capture and reconcile the final source delta against the last verified checkpoint.
  3. Apply the approved delta and configuration changes to Fivetran.
  4. Switch traffic, domains, integrations, credentials, automation, and user entry points in dependency order.
  5. Run every blocking verification check and keep the source intact.

Proof to capture: Fivetran alone owns production, totals reconcile, exceptions are signed, and every blocking check has durable evidence.

Return to safety

Rollback

Return production ownership to Airbyte without losing destination-era changes.

Deadline: Within seven days and before source data, plans, credentials, domains, keys, or retention settings are changed.

  1. Stop new user, integration, schedule, and API writes in Fivetran.
  2. Restore prior Airbyte traffic, domains, credentials, automation, and integration ownership.
  3. Export and classify the Fivetran post-cutover delta.
  4. Apply safe destination-era changes back to Airbyte without duplicating actions.
  5. Run the same blocking checks against the restored source.

Proof to capture: Airbyte again owns production with current data and no duplicate destination action.

Rollback immediately when
  • Unexplained critical count, value, relationship, or checksum variance
  • Missing, corrupted, or exposed critical data
  • Duplicate production action or unresolved split-brain state
  • Failed access, security, delivery, routing, performance, or integration check
  • A critical feature has no safe destination replacement or rollback path
08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

0%
Interactive report preview0 / 8 checks passed
PassIDCheckMethodExpected resultEvidence
V-01BlockingSources, connectors, and authentication reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for sources, connectors, and authentication.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Sources, connectors, and authentication ledger with counts, exceptions, sample IDs, and owner sign-off.
V-02BlockingDestinations, schemas, and namespaces reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for destinations, schemas, and namespaces.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Destinations, schemas, and namespaces ledger with counts, exceptions, sample IDs, and owner sign-off.
V-03BlockingStreams, tables, fields, and selections reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for streams, tables, fields, and selections.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Streams, tables, fields, and selections ledger with counts, exceptions, sample IDs, and owner sign-off.
V-04BlockingIncremental cursors and replication state reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for incremental cursors and replication state.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Incremental cursors and replication state ledger with counts, exceptions, sample IDs, and owner sign-off.
V-05BlockingHistorical backfill and reset behavior reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for historical backfill and reset behavior.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Historical backfill and reset behavior ledger with counts, exceptions, sample IDs, and owner sign-off.
V-06BlockingTransformations and normalization reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for transformations and normalization.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Transformations and normalization ledger with counts, exceptions, sample IDs, and owner sign-off.
V-07Schedules, concurrency, and rate limits reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for schedules, concurrency, and rate limits.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Schedules, concurrency, and rate limits ledger with counts, exceptions, sample IDs, and owner sign-off.
V-08BlockingCustom connectors and connector code reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for custom connectors and connector code.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Custom connectors and connector code ledger with counts, exceptions, sample IDs, and owner sign-off.
09Post-migration cleanup

Remove the scaffolding safely.

Safe after: One complete operating cycle, at least seven stable days, and owner sign-off on every blocking check and exception.

  1. Create final Airbyte exports and archive verification, access, financial, and rollback evidence.
  2. Revoke temporary credentials, API keys, webhooks, elevated roles, and migration network access.
  3. Remove obsolete jobs, embeds, domains, integrations, collectors, routes, and DNS records.
  4. Keep the source intact and read-only through the approved legal and operational retention window.
  5. Cancel paid plans only after billing, legal, security, evidence, and recovery review.
  6. Schedule the next Fivetran backup, restore test, access review, and migration-playbook review.
Sources and evidence

Verify against the primary material.

Platform behavior changes. Check these sources and the review dates above before executing a production migration.

  1. Airbyte: official portability and migration documentationAccessed 2026-07-20
  2. Fivetran: official portability and migration documentationAccessed 2026-07-20