Notion Migration Guide
Upgrading to 4.0.0
Version 4.0.0 migrates the connector from Notion API version 2022-06-28 to 2025-09-03. This is a major update driven by Notion's introduction of multi-source databases, where the concept of a "database" has been split into "databases" (containers) and "data sources" (individual schemas/property sets). A "data source" now represents what was previously called a "database" — the table containing pages and properties.
Breaking Changes
-
databasesstream replaced bydata_sources: Thedatabasesstream has been removed and replaced with a newdata_sourcesstream. The new stream returns objects with"object": "data_source"instead of"object": "database", along with a different parent structure (database_idparent anddatabase_parentgrandparent fields). -
pagesstream parent field updated: Pages that belong to a database now reportparent.type: "data_source_id"with aparent.data_source_idfield instead ofparent.type: "database_id"with aparent.database_idfield. -
blocksstream schema additions: Newin_trashboolean field added anddata_source_idparent type added.
Migration Steps
A full schema refresh and data reset are required for the Data Sources (formerly Databases), Pages, and Blocks streams.
- Select Connections in the main nav bar.
- Select the connection(s) affected by the update.
- Select the Schema tab.
- Click Refresh source schema to pick up the new
data_sourcesstream and updatedpagesschema. - Enable the new Data Sources stream if you were previously syncing the Databases stream.
- Click Refresh source schema to pick up the new
- Select the Status tab.
- In the Enabled streams list, click the three dots on the right side of the Pages stream and select Clear data.
- Do the same for the Blocks stream if you are syncing it.
- Trigger a new sync by clicking Sync Now.
For more information on clearing your data in Airbyte, see this page.
Upgrading to 3.0.0
Version 3.0.0 migrates the connector from the Python CDK to the low-code CDK. This migration changes how state is managed for incremental streams nested within a parent stream, which is a breaking change for users syncing the Comments stream.
If you are not syncing the Comments stream, no action is required.
Migration Steps
Clear the data for the Comments stream:
- Select Connections in the main nav bar.
- Select the connection(s) affected by the update.
- Select the Status tab.
- In the Enabled streams list, click the three dots on the right side of the Comments stream and select Clear data.
- After the clear succeeds, click Sync Now.
For more information on clearing your data in Airbyte, see this page.
Upgrading to 2.0.0
Version 2.0.0 updates the JSON schemas of the Blocks, Databases, and Pages streams to reflect changes in the Notion API:
- The
rich_textproperty in Pages changed from an object to an array ofrich_textobjects. - The
phone_numberproperty in Pages changed from a string to an object. - The deprecated
textproperty in content blocks was renamed torich_textacross the Blocks, Databases, and Pages streams.
Migration Steps
A full schema refresh and data reset are required.
- Select Connections in the main nav bar.
- Select the connection(s) affected by the update.
- Select the Schema tab.
- Click Refresh source schema to pick up the updated schemas.
- Select the Status tab.
- In the Enabled streams list, click the three dots on the right side of each affected stream (Blocks, Databases, Pages) and select Clear data.
- Click Sync Now.
For more information on clearing 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.
-
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.