Release Notes

April 2026

We've implemented a new mechanism to fetch source schema quicker when creating a new connection. Now, instead of deriving the schema from source data, we use fixed schema models. This allows you to see the schema blocking and hashing screen almost immediately after creating a new connection.

As a result of this improvement, you may see empty tables and columns in the Schema tab of existing connections that have not yet synced to your destination.

After optimizing schema fetch for the connectors below, these connections no longer use the pre-initial-sync schema capture flow described in schema_status.

Affected connectors

REST API request changes (breaking)

For the connectors listed above, the schema_status request field is no longer supported in:

Update a Connection

If your automation still sends schema_status for these connectors, requests may fail.

REST API response changes

For the connectors listed above, schema_status is no longer returned for flows that previously exposed it, including:

If your downstream transformations or orchestration rely on this field, update them to handle its absence.

Dashboard flow change

In the Fivetran dashboard, these connectors no longer show the schema prefetch and review step before initial sync. After connection creation, you proceed directly to the initial sync flow.

March 2026

We've added support for schema, table, and column deletion events. These events are available in the SOURCE_SCHEMA_CHANGE_HISTORY, SOURCE_TABLE_CHANGE_HISTORY, and SOURCE_COLUMN_CHANGE_HISTORY tables of the Fivetran Platform connector and will be attributed the change type DELETE.

Additionally, these events will now be included in the schema change count value displayed in the Status tab on the Connection Details page.

February 2026

We have updated the Fivetran Platform Quickstart package to version 2.5.1

January 2026

We have updated the Fivetran Platform Quickstart package to version 2.5.0

December 2025

The Fivetran Platform Connector no longer captures internal system columns, such as _fivetran_updated_cols, _fivetran_op_type, _fivetran_rowid_old, and _fivetran_earliest, in the DESTINATION_COLUMN table.

See our System Columns and Tables documentation for more details.

October 2025

We unified each connector’s pre-built dbt Core–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.

September 2025

We now show a warning when the Google Cloud Storage bucket used for log events cannot be accessed from the Hybrid Deployment environment.

The warning includes the underlying error message to help troubleshooting.
Account- and destination-related metadata continues to sync; log event ingestion resumes automatically once access is restored.

If you see this warning, verify that connection from your Hybrid environment can reach the storage endpoint.

August 2025

Effective August 27, 2025 we use a new August 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability. For a period of time, existing connections will have both the old and new tables with the same data.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

7 total changes • 7 possible breaking changes

Table/column	Change type	Old name	New name
`DESTINATION_COLUMN_METADATA (new table name: DESTINATION_COLUMN)`
table	Rename Table	`DESTINATION_COLUMN_METADATA`	`DESTINATION_COLUMN`
`DESTINATION_SCHEMA_METADATA (new table name: DESTINATION_SCHEMA)`
table	Rename Table	`DESTINATION_SCHEMA_METADATA`	`DESTINATION_SCHEMA`
`DESTINATION_TABLE_METADATA (new table name: DESTINATION_TABLE)`
table	Rename Table	`DESTINATION_TABLE_METADATA`	`DESTINATION_TABLE`
`SOURCE_COLUMN_METADATA (new table name: SOURCE_COLUMN)`
table	Rename Table	`SOURCE_COLUMN_METADATA`	`SOURCE_COLUMN`
`SOURCE_FOREIGN_KEY_METADATA (new table name: SOURCE_FOREIGN_KEY)`
table	Rename Table	`SOURCE_FOREIGN_KEY_METADATA`	`SOURCE_FOREIGN_KEY`
`SOURCE_SCHEMA_METADATA (new table name: SOURCE_SCHEMA)`
table	Rename Table	`SOURCE_SCHEMA_METADATA`	`SOURCE_SCHEMA`
`SOURCE_TABLE_METADATA (new table name: SOURCE_TABLE)`
table	Rename Table	`SOURCE_TABLE_METADATA`	`SOURCE_TABLE`

July 2025

We have added a new column, deployment_type, to the CONNECTIONS table. This column captures the deployment model used with a given connection. Possible values are as follows: Fivetran, Hybrid.

May 2025

We've discontinued support and stopped syncing the following columns:

type from the DESTINATION metadata table
connector_id from the INCREMENTAL_MAR metadata table
integration_id from the RESOURCE_MEMBERSHIP metadata table

Metadata sharing tables in our Fivetran Platform Connector are now generally available for all accounts on the Enterprise and Business Critical plans:

These tables provide access to metadata for the data synced by Fivetran, which helps you understand the mapping between the source and the destination. The data retrieved can be easily consumed in BI tools, data catalogs, or through direct SQL queries.

We have added the new AUDIT_TRAIL table. It enables users to track important actions and changes across their Fivetran account, providing a comprehensive history of user interactions and data modifications.

March 2025

We've introduced the new CONNECTION table, which replaces the deprecated CONNECTOR table. Additionally, we have deprecated several columns and introduced new ones.

TABLE NAME	DEPRECATED COLUMNS	NEW COLUMN
INCREMENTAL_MAR	CONNECTOR_ID, CONNECTOR_NAME	CONNECTION_NAME
RESOURCE_MEMBERSHIP	INTEGRATION_ID, CONNECTOR_ID	CONNECTION_ID
LOG	CONNECTOR_ID	CONNECTION_ID
CONNECTOR_SDK_LOG	CONNECTOR_ID	CONNECTION_ID
SOURCE_SCHEMA_METADATA	CONNECTOR_ID	CONNECTION_ID
SOURCE_TABLE_METADATA	CONNECTOR_ID	CONNECTION_ID
SOURCE_COLUMN_METADATA	CONNECTOR_ID	CONNECTION_ID
DESTINATION_SCHEMA_METADATA	CONNECTOR_ID	CONNECTION_ID
DESTINATION_TABLE_METADATA	CONNECTOR_ID	CONNECTION_ID
DESTINATION_COLUMN_METADATA	CONNECTOR_ID	CONNECTION_ID
SOURCE_SCHEMA_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
SOURCE_TABLE_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
SOURCE_COLUMN_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
DESTINATION_SCHEMA_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
DESTINATION_TABLE_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
DESTINATION_COLUMN_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID

See the Fivetran Platform Connector documentation for details.

December 2024

We've added the TRANSFORMATION_RUNS table to sync Transformations usage data.

October 2024

The group-level Fivetran Platform Connector is now automatically paused when it is the only active connector in the group. This means that if there are other connectors in the group, but all of them are paused, we pause the group-level Fivetran Platform Connector.

We unpause the automatically-paused group-level Fivetran Platform Connector once there is at least one active connector present in the group.

We have added the new CONNECTOR_SDK_LOG table. The Fivetran Platform Connector now syncs Connector SDK logs to this table.

We have added a new nullable column, connector_id, to the DESTINATION_SCHEMA_METADATA, DESTINATION_TABLE_METADATA, and DESTINATION_COLUMN_METADATA tables in the Metadata Sharing section. This column, going forward, will be populated with the ID of the connection that each schema, table, or column belongs to.

August 2024

We have discontinued the broken column of the CONNECTOR_TYPE table. For more information, see our Fivetran Platform Connector ERD.

July 2024

The Fivetran Platform connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

We have made the following changes to the INCREMENTAL_MAR table:

Deprecated the connector_id column, which contains the connector name;
Added a new column, connector_name.

The ROLE table has the connector_types column, which creates a many-to-many relationship between the CONNECTOR_TYPE and ROLE tables. We added a new bridge/join table, role_connector_type that has the connector_type and role_id columns to make this relationship more intuitive.

We have added a new column, connector_id, to the RESOURCE MEMBERSHIP table. It contains the connector ID (like the existing integration_id column). Existing connectors now have both columns, connector_id and integration_id, while new connections created after July 10, 2024 only have the connector_id column.

The DESTINATION table has the type column, which contains the deployment type (Fivetran or HVR). For new connections created after July 10, 2024 this column is replaced with the deployment_type column.

See our Fivetran Platform Connector ERD for more information.

June 2024

We have added the destination_type column to the DESTINATION table. While the existing type column has two possible values, Fivetran and HVR, destination_type will contain the exact destination type (for example, Snowflake, Kafka, BigQuery, etc.).

May 2024

The Fivetran Platform connector now syncs 7 days' worth of historical data instead of 5 days.

You can now select tables to include or exclude from syncs on the Schema tab of the connector details page in your Fivetran dashboard.

We are gradually rolling out these changes to all existing connections.

March 2024

We have removed the free_type column from the deletion key of the INCREMENTAL_MAR table. Previously, the deletion key included this column, which caused data discrepancy.

February 2024

Automatic connector creation: We now add a destination-level Fivetran Platform Connector to every new destination that you create in your Fivetran dashboard. This way, you have full access to essential Fivetran technical information from the start, like logs and metadata.

We don't currently add the Fivetran Platform Connector to destinations created using our REST API.

Immediate data sync: Once created, the connector immediately begins syncing data to the destination, so that you have access to this technical information from the start.

Smart Trial Management: During trial periods, we add the Fivetran Platform Connector, but its initial sync does not trigger the start of the trial period.

January 2024

We have updated the Quickstart packages for the following connectors:

Fivetran Platform Connector to version 1.4.0
Google Ads to version 0.10.1

November 2023

We now sync metadata to the SOURCE_FOREIGN_KEY_METADATA table. For more information, see our Fivetran Platform documentation and sample queries.

October 2023

We now sync source and destination metadata to the following tables:

COLUMN_LINEAGE
DESTINATION_COLUMN_METADATA
DESTINATION_SCHEMA_METADATA
DESTINATION_TABLE_METADATA
SCHEMA_LINEAGE
SOURCE_COLUMN_METADATA
SOURCE_SCHEMA_METADATA
SOURCE_TABLE_METADATA
TABLE_LINEAGE

This functionality replaced the Metadata API. If you are using the Metadata API, you should have received an email with details regarding the deprecation timeline.

September 2023

We now populate the created_at column as null in the DESTINATION table if the is_active column is false.

We have added two new columns, is_active and type, to the DESTINATION table.

We now sync HVR 6 usage data to the DESTINATION and USAGE_COST tables.

We now sync all roles to the ROLE and ROLE_PERMISSION tables. Previously, we synced only the custom roles with an associated account.

August 2023

We have renamed our Fivetran Log Connector to Fivetran Platform Connector. This name change applies to the Fivetran dashboard and our documentation.

June 2023

We have removed the following obsolete tables that we previously used for our Role-Based Access Control:

ACCOUNT_MEMBERSHIPS
MEMBERSHIPS
MEMBERSHIPS_ROLES
MEMBERSHIPS_ROLES_SOURCES

November 2022

We now sync dbt transformations' user-facing logs into the LOG table.

October 2022

For the accounts that have the Role-Based Access Control (RBAC) feature enabled, we have added the following new tables:

RESOURCE_MEMBERSHIP
ROLE
ROLE_PERMISSION
TEAM
TEAM_MEMBERSHIP

We have added a new table, INCREMENTAL_MAR, which stores the incremental daily active rows for every destination, connector, and table within your account. This is helpful in tracking and managing consumption in our usage-based pricing. This table contains both paid and free MAR. We have deprecated the ACTIVE_VOLUME table, which stores the cumulative monthly active rows.

July 2022

We have added two new optional parameters, is_account_level_connector and group, to the Fivetran Platform Connector REST API Request. You can now opt to retrieve account-level logs.

January 2022

We have added a new table, USAGE_COST.

We have added a new column, sync_id, to the LOG table.

We have deprecated the CREDITS_USED table.

June 2021

From June 1, 2021 00:00 UTC, our Fivetran Platform Connector reports only paid Monthly Active Rows (MAR). This is a forward only change that will not be applied for the previous months. The Usage tab in the Dashboard will continue to display both free and paid MAR. We have increased visibility into free MAR in the Dashboard and made certain types of re-sync free. No action is required on your part. For more details, see the Expanded Free MAR Operations changelog.

May 2021

We have added a new column, sync_frequency, to the CONNECTOR table.

March 2021

We have added a new table, CONNECTOR_TYPE, to capture a connector's release phase status.

We have added a new column, _fivetran_deleted, to the USER table to track when a user is deleted.

We have added a new column, _fivetran_deleted, to the CONNECTOR table to track when a connector is deleted.

December 2020

The Fivetran Platform Connector now supports the creation of account-level connectors. A Fivetran Account Administrator can now sync the connector logs for all destinations in the account. See our setup instructions for more information.

August 2020

We have released a pre-built, dbt Core-compatible data model for the Fivetran Platform Connector. Find the model in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

July 2020

We have removed the service_version column from the CONNECTOR table.

June 2020

We have added a new table, CREDITS_USED. This table stores the monthly credit usage summary per destination.

April 2020

We have renamed the TRANSFORMATION_TABLE table to TRIGGER_TABLE.

We have renamed the group_id column to destination_id in the TRANSFORMATION, DESTINATION_MEMBERSHIP, and USER tables.

You can now configure the Fivetran Platform Connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.

March 2020

We have added a new table, ACTIVE_VOLUME, which stores the cumulative monthly active rows for every destination, connector, and table within your account. This will be helpful in tracking and managing consumption in our usage-based pricing.

July 2019

Fivetran Platform Connector syncs logs and metadata about your connectors.

Read our Fivetran Platform Connector documentation.