November 2025

Schema changes

ADP Workforce Now

We have added two new child tables, WORKER_PAY_DISTRIBUTION and WORKER_PAY_DISTRIBUTION_INSTRUCTIONS, to the WORKER table. Be sure to re-sync the WORKER table to backfill historical data for these new child tables, or reach out to Fivetran Support to re-sync for you. MAR will be free for WORKER_PAY_DISTRIBUTION and WORKER_PAY_DISTRIBUTION_INSTRUCTIONS tables only.

We are gradually rolling out these changes to all connections.

Datadog

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

We are updating the connector schema to prevent or resolve data integrity issues.

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.

6 total changes • 6 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`SERVICE_LEVEL_OBJECTIVE_HISTORY_DENOMINATOR_VALUE`
column	Primary Key Change	`denominator_value`	`denominator_value` 🔑	Added to primary key.
column	Discontinued Column	`index` 🔑		No longer primary key.
`SERVICE_LEVEL_OBJECTIVE_HISTORY_NUMERATOR_VALUE`
column	Discontinued Column	`index` 🔑		No longer primary key.
column	Primary Key Change	`numerator_value`	`numerator_value` 🔑	Added to primary key.
`SERVICE_LEVEL_OBJECTIVE_HISTORY_SERIES_TIME`
column	Discontinued Column	`index` 🔑		No longer primary key.
column	Primary Key Change	`time`	`time` 🔑	Added to primary key.

GitHub

We have added the following new tables:

PROJECT_V2
PROJECT_V2_CUSTOM_FIELD
PROJECT_V2_ITEM

We are gradually rolling out this change to all existing connections.

incident.io

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

We are updating the connector schema to adhere to standard naming conventions.

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.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`WORKFLOW_ONCE_FOR`
column	Rename Column		`array`	`is_array`

Ironclad

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

We are updating the connector schema to support a feature enhancement.

6 total changes • 0 possible breaking changes

Table/column	Change type	New name
`APPROVAL_REQUEST`
table	New Table	`APPROVAL_REQUEST`
`ENTITY`
table	New Table	`ENTITY`
`ENTITY_NAMED_TYPE_ID`
table	New Table	`ENTITY_NAMED_TYPE_ID`
`ENTITY_RELATIONSHIP_TYPE`
table	New Table	`ENTITY_RELATIONSHIP_TYPE`
`TURN_HISTORY`
table	New Table	`TURN_HISTORY`
`TYPE_HASH_DATA`
table	New Table	`TYPE_HASH_DATA`

Jira

We have added a new column activatedDate to the SPRINT table.

Khoros Care

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

We are updating the connector schema to support a feature enhancement.

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.

16 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`TEAM_PERFORMANCE_INTERVAL`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	New Column		`agent_activities_total_review_closed_time`
column	New Column		`agent_activities_v_2_active_time_in_focus`
column	New Column		`agent_activities_v_2_active_time_out_of_focus`
column	New Column		`agent_activities_v_2_idle_time_in_focus`
column	New Column		`agent_activities_v_2_idle_time_out_of_focus`
column	New Column		`agent_activities_v_2_in_app_time_in_focus`
column	New Column		`agent_activities_v_2_in_app_time_out_of_focus`
column	New Column		`agent_activities_v_2_inactive_time_in_focus`
column	New Column		`agent_activities_v_2_inactive_time_out_of_focus`
column	New Column		`agent_activities_v_2_non_agent_time_in_focus`
column	New Column		`agent_activities_v_2_non_agent_time_out_of_focus`
column	New Column		`agent_utilization`
`TEAM_PERFORMANCE_REPORT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	New Column		`agent_activities_total_review_closed_time`
column	New Column		`agent_utilization`

ShipHero

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

We are updating the connector schema to prevent or resolve data integrity issues.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`ORDER_LINE_ITEM`
column	New Column	`price`
`SHIPMENT_SHIPPING_LABEL`
column	New Column	`status`

Stripe

We have added the following new tables:

CASH_BALANCE
CASH_BALANCE_TRANSACTION
CHARGE_PAYMENT_METHOD_DETAILS
PRICE_CURRENCY_OPTION

We are gradually rolling out this change to all existing connections.

Improvements

360Learning

We have added a new authentication method for our 360Learning connector. You can now use OAuth authentication method to connect your 360Learning with Fivetran. To support these features, we have made the following changes to the connection setup form:

Added Authentication type field, that allows you to select between API key and OAuth authentication methods.
Added Client ID, Client secret, and Base URL fields, allowing you to provide your own app credentials.

For more information, see our setup instructions.

Bitly

You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.

Drata

We have made the following improvements to the connector:

Added table re-sync support. Previously, we only supported connection-level re-syncs.
Event-based tables and tables with a retention period at the source don't support this feature.
You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.

Managed Data Lake Service

We now support the AWS PrivateLink and Azure Private Link connection methods for AWS and Azure data lakes on the Business Critical plan, respectively. We are gradually rolling out this enhancement to all existing destinations.

For more information, see our Managed Data Lake Service setup guide.

NICE

We no longer support priority-first sync for the CONTACT table.

Redshift destination

We now support IAM role authentication for authorizing S3 buckets associated with Redshift destinations configured for Hybrid Deployment.

Row Filtering - list of supported connectors extended

Row filtering is now supported for the following connectors:

To learn how to use row filtering and see the list of supported connectors, see our row filtering documentation.

Sage HR

We have made the following improvements to the connector:

Added table re-sync support. Previously, we only supported connection-level re-syncs.
Event-based tables and tables with a retention period at the source don't support this feature.
You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.

Simplecast

We have made the following improvements to the connector:

Added table re-sync support. Previously, we only supported connection-level re-syncs.
Event-based tables and tables with a retention period at the source don't support this feature.
You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.

Webhooks

We now capture and store HTTP request headers from webhook events in a new headers column. This enhancement provides better observability and debugging capabilities by allowing you to access request metadata such as User-Agent, Content-Type, and custom headers sent with webhook events. For security, authentication headers and other sensitive headers containing keywords like auth, token, secret, password, and cookie are automatically filtered before storage. For more information, see the schema information in our Webhooks documentation.