Productive Migration Guide
Upgrading to 0.1.0
What changed
- The
project_assignmentsstream is removed. Productive retired this endpoint in favor of memberships, which the connector already supports. - The
boardsstream now reads the folders endpoint. Its stream name, primary key, and schema remain unchanged, but the resourcetypevalue is nowfoldersrather thanboards. - Requests now send the configured organization ID in the
X-Organization-Idheader, as required by Productive.
Who is affected
Connections selecting project_assignments or boards must review this migration. The old endpoints return errors and prevent these streams from syncing.
Complete the migration by October 21, 2026. Affected connections that have not upgraded by the deadline will be disabled rather than automatically upgraded, so you can review the stream changes before resuming syncs.
Migration steps
- Before upgrading, preserve any historical
project_assignmentsdata needed by downstream consumers. Productive's memberships are a different resource; their IDs and attributes are not a drop-in replacement for project assignments. - Upgrade the source connector to version 0.1.0 or later and refresh the connection's source schema.
- Accept the removal of
project_assignments. Selectmembershipsif you need project access data, then save the updated connection. - Update downstream queries that used
project_assignmentsto use the project-related records inmemberships. Memberships also include access to other resources, so filter using the project relationship orattributes.target_typeas appropriate for your data. - If you sync
boards, keep the stream selected and update any downstream filters that expecttype = 'boards'to accepttype = 'folders'. - Run a sync and validate the replacement data before resuming downstream jobs. No configuration or state migration is required for other streams.
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.
-
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.
-
-
Edit the entry for the connector you want to pin.
-
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.
-
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.
-
-
Find the connector you want to update in the list of connectors.
noteAirbyte lists two versions, the current in-use version and the latest version available.
-
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.
-
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.
-
-
Select the instance of the connector you wish to upgrade.
-
Select Upgrade.
-
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.
-
In the nav bar, click Connections.
-
Find the connection affected by the upgrade.
-
Click the Schema tab.
-
Click Refresh source schema (looks like ). When Airbyte finishes, it shows you any detected schema changes.
-
Click OK.
-
Click Save changes
-
Clear the data for the streams affected by this upgrade.
Once the clear is complete, you can begin syncing your data again as usual.