Skip to main content

Strava Migration Guide

Availability
Available CoreAvailable StandardAvailable PlusAvailable ProAvailable Enterprise FlexAvailable PyAirbyte
Connector type (beta)
Available Data replicationNot available Agent(learn more)
Support Level
Marketplace
Connector Version
0.3.52 (last updated 3 months ago)
Sync Success Rate
Low
Usage Rate
Low
Data workers used
0.2 per sync (Learn more)
Definition ID
7a4327c4-315a-11ec-8d3d-0242ac130003

Upgrading to 0.4.0​

What changed and why​

Airbyte now stores the latest OAuth refresh token, a secret access token, and its expiry in the source configuration. Previously, rotated refresh tokens were discarded and the absolute expires_at timestamp was interpreted as a duration. The new optional, hidden access_token and token_expiry_date fields are managed automatically; do not populate them manually.

The connection check now validates access to both athlete stats and activities. Previously, setup could succeed without the activity permission needed to sync activities.

Who is affected​

All Strava sources use the updated credential configuration. Sources whose tokens lack activity:read_all will now fail setup instead of failing later during a sync. Existing valid credentials remain usable. Stream schemas and incremental state are unchanged; no stream reset is required.

Upgrade by October 21, 2026. Remaining sources will be automatically upgraded after that deadline.

Upgrade steps​

  1. Upgrade the connector to version 0.4.0.
  2. Ensure the Strava developer application is active. If Strava reports Application / Status / Inactive, restore its access before retrying.
  3. If the athlete has not granted activity:read_all, reauthorize the application with that scope and update the source credentials. Refreshing a token cannot add permissions.
  4. Use the latest refresh token if tokens have been exchanged outside Airbyte. Older tokens may have been invalidated by rotation.
  5. Run the source connection check, then resume syncing. Airbyte manages subsequent token refreshes automatically.

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?