Skip to main content

Marketo Migration Guide

Availability
Available CoreAvailable StandardAvailable PlusAvailable ProAvailable Enterprise FlexAvailable Self-Managed EnterpriseAvailable PyAirbyte
Support Level
Marketplace
Connector Version
2.0.0 (last updated 8 days ago)
CDK Version
2.3.0
Definition ID
9e0556f4-69df-4522-a3fb-03264d36b348

Upgrading to 2.0.0​

note

This change is only breaking if you are syncing the leads stream in Incremental mode. Full refresh syncs of leads are not affected, since they re-fetch the entire stream on every sync and never relied on the cursor/filter relationship.

This update changes the leads stream to filter Marketo's Bulk Lead Extract API on updatedAt instead of createdAt. The cursor field is unchanged (updatedAt).

Marketo's Bulk Lead Extract only supports a single date-range filter per export job. In previous versions, Airbyte filtered records using createdAt while tracking incremental progress with updatedAt. This caused a gap where leads created before the cursor window were excluded from future syncs, even if they were later updated. As a result, updates to existing leads were never replicated to the destination.

With this change, the export filter now uses the same field as the incremental cursor (updatedAt), ensuring updates to existing leads are correctly captured in every incremental sync.

Full refresh users​

If you sync the leads stream in Full Refresh mode, you can simply upgrade to 2.0.0 — no migration steps are required. Full refresh syncs re-fetch the entire stream on every run, so they were never affected by the cursor/filter mismatch.

Incremental users: refresh affected schemas and reset data​

Users syncing the leads stream in Incremental mode should refresh the source schema and clear data for the leads stream after upgrading. Without a clear and resync, historical updates that were silently dropped by earlier versions will not appear in the destination — the fix only prevents future silent drops.

  1. Select Connections in the main nav bar.
    • Select the connection affected by the update.
  2. Select the Schema tab.
    • Select Refresh source schema.
    • Select OK.
note

Any detected schema changes will be listed for your review.

  1. Select Save changes at the top right of the page.
    • Ensure the Reset affected streams option is checked.
note

Depending on destination type you may not be prompted to reset your data.

  1. Select Save connection.
note

This will reset the data in your destination and initiate a fresh sync.

For more information on resetting your data in Airbyte, see this page.

Connector upgrade guide​

Review the following information to prepare for and execute your upgrade.

Review the changelog​

Before updating a connector, review the changelog to understand the changes and their potential impact on your existing connections. Find the changelog for any connector by navigating to the bottom of the documentation for that connector. Major version releases also include a migration guide.

Plan for major updates​

Major updates may require you to adjust connection settings or even make changes to your data pipelines. Allocate enough time and resources for this. Use the migration guide to ensure your transition process goes smoothly.

Airbyte provides tooling that guarantees safe connector version bumps and enforces automated version bumps for minor and patch updates. You always need to manually update for major version bumps.

Self-managed plans: pin a specific version if you can't update​

If you're unable to upgrade to the new version of a connector, you can pin that connector to a specific version.

  1. In the navigation bar:

    • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

    • If you're on any other plan, click Workspace settings > Sources/Destinations.

  2. Edit the entry for the connector you want to pin.

  3. Set the Default Version to the version you want to use.

Self-managed plans: update the local connector image​

If you self-manage Airbyte, you must manually update the connector image in your local registry before proceeding with the migration. Follow the steps below.

  1. In the navigation bar:

    • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

    • If you're on any other plan, click Workspace settings > Sources/Destinations.

  2. Find the connector you want to update in the list of connectors.

    note

    Airbyte lists two versions, the current in-use version and the latest version available.

  3. Click Change to update your OSS version to the latest available version.

Update the connector version​

Update each instance of the connector separately. If you have multiple instances of a connector, updating one doesn't affect the others.

  1. In the navigation bar:

    • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

    • If you're on any other plan, click Workspace settings > Sources/Destinations.

  2. Select the instance of the connector you wish to upgrade.

  3. Select Upgrade.

  4. Follow the prompt to confirm you are ready to upgrade to the new version.

Clear data from affected streams​

After upgrading a connector with a breaking change, you must refresh affected schemas and clear your data.

  1. In the nav bar, click Connections.

  2. Find the connection affected by the upgrade.

  3. Click the Schema tab.

  4. Click Refresh source schema (looks like ). When Airbyte finishes, it shows you any detected schema changes.

  5. Click OK.

  6. Click Save changes

  7. Clear the data for the streams affected by this upgrade.

Once the clear is complete, you can begin syncing your data again as usual.

Was this page helpful?