February 2026

Activations

Activations, the integration of Census into Fivetran, is now available for all users. With Activations, you can configure managed, automated reverse ETL pipelines without writing code. It activates data from a centralized source of truth, such as a data warehouse, and delivers insights directly into the business tools where your teams make decisions. Pair Activations with Fivetran’s ELT capabilities to create bidirectional, end-to-end data pipelines within a single platform. Learn more in our Activations documentation.

Activations offers several key self-service features:

Reverse ETL pipelines: Sync data from a centralized source of truth, such as a data warehouse or data lake, back into business tools where your teams take action. These include CRMs, support platforms, marketing platforms, and other SaaS applications.
Data transformations and enrichment: Create and enrich datasets for your business teams without having to write SQL queries.
Audience Hub: Create, test, and analyze marketing audience segments directly on top of your data warehouse.

Get started in the Activations tab of the Fivetran dashboard. Activations follows the Fivetran usage-based pricing model.

Connector SDK

`fivetran-connector-sdk` PyPI package

We have released version 2.6.1 of the fivetran-connector-sdk PyPI package. This release adds the following:

Minor enhancements and improvements.

Lite Connectors

Lite connectors are now available for the following sources:

Alation

Row Filtering - added support for the Lite connectors

We now support row filtering for our Lite connectors.

Logs

Account-Level External Logging

We now support connecting an external logging service at the account level, in addition to the destination level. Account-level logging collects logs for all destinations in your account, and you can still connect one external log service per destination. This feature will be rolled out gradually to all customers over three next weeks.

To connect an account-level external logging service, go to Account Settings > General > External Logging in your Fivetran dashboard.

sql_query log events deprecated

We've deprecated the sql_query log event. Use the extract_summary log event instead.

Quickstart Transformations

Custom variable support for Quickstart Data Models

We have added support for custom variables in the Quickstart Data Models. You can now manage values of custom variables, which are provided in Fivetran packages, to customize the transformations according to your requirements. For more information, see the Edit Custom Variables for Quickstart Transformations section

Sunset destinations

Azure Data Lake Storage

We have sunset the Azure Data Lake Storage destination and migrated all existing Azure Data Lake Storage destinations to Fivetran Managed Data Lake Service. You can no longer create Azure Data Lake Storage destinations. If you want to create a data lake with Azure Data Lake Storage as the storage provider, use our Managed Data Lake Service.

S3 Data Lake

We have sunset the S3 Data Lake destination and migrated all existing S3 Data Lake destinations to Fivetran Managed Data Lake Service. You can no longer create S3 Data Lake destinations. If you want to create a data lake with AWS S3 as the storage provider, use our Managed Data Lake Service.

Transformations for dbt Core

Updated dbt Quickstart packages

We have updated the Quickstart packages for the following connectors:

Connectors supporting the Social Media Reporting data model to version 1.5.0. We are gradually rolling out this change. All Quickstart transformations will be updated by March 24, 2026.
HubSpot to version 1.7.0. We are gradually rolling out this change. All Quickstart transformations will be updated by March 16, 2026.
Jira to version 1.5.0. We are gradually rolling out this change. All Quickstart transformations will be updated by March 16, 2026.
Klaviyo to version 1.3.1. We are gradually rolling out this change. All Quickstart transformations will be updated by March 25, 2026.
LinkedIn Company Pages to version 1.3.0. We are gradually rolling out this change. All Quickstart transformations will be updated by March 24, 2026.
QuickBooks to version 1.4.1. We are gradually rolling out this change. All Quickstart transformations will be updated by March 22, 2026.
SAP ERP on HANA to version 0.6.1. We are gradually rolling out this change. All Quickstart transformations will be updated by March 23, 2026.
Shopify to version 1.5.2. We are gradually rolling out this change. All Quickstart transformations will be updated by March 24, 2026.
Stripe to version 1.5.0. We are gradually rolling out this change. All Quickstart transformations will be updated by March 25, 2026.

Upstream Transformations

You can now specify upstream transformations in addition to upstream connections for Transformations for dbt Core* and Quickstart transformations with Integrated and Run Frequency with Smart Syncing schedules.

*dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Schema changes

Aha!

Effective February 3, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`GOAL`
column	New Column	`time_frame_id`
column	New Column	`time_frame_name`

Algolia

Effective February 12, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

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.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`RULE_CONDITION`
column	Discontinued Column	`_fivetran_id` 🔑
column	Primary Key Change		`index` 🔑	Added to primary key.

Ashby

Effective February 20, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`INTERVIEW_STAGE`
table	New Table	`INTERVIEW_STAGE`
`INTERVIEW_STAGE_GROUP`
table	New Table	`INTERVIEW_STAGE_GROUP`

Canvas Data 2 by Instructure

Effective February 3, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

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

3 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CONTEXT_MODULE_PROGRESSION`
table	New Table	`CONTEXT_MODULE_PROGRESSION`
`USER_ACCOUNT_ASSOCIATION`
table	New Table	`USER_ACCOUNT_ASSOCIATION`
`WEB_CONFERENCE`
table	New Table	`WEB_CONFERENCE`

Ceridian Dayforce

Effective February 16, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to improve data management.

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.

8 total changes • 8 possible breaking changes

Table/column	Change type	Old name
`ORGANIZATION_UNIT_CHILD_LEGAL_ENTITY_ITEM`
column	Discontinued Column	`effective_end`
column	Discontinued Column	`last_modified_timestamp`
column	Discontinued Column	`long_name`
column	Discontinued Column	`short_name`
`ORGANIZATION_UNIT_LEGAL_ENTITY_ITEM`
column	Discontinued Column	`effective_end`
column	Discontinued Column	`last_modified_timestamp`
column	Discontinued Column	`long_name`
column	Discontinued Column	`short_name`

Coupa

We have added the following new tables:

PURCHASE_ORDER_REVISION
PURCHASE_ORDER_REVISION_CHANGE

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

Front

We have added a new table, TICKET_STATUS.

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

Gorgias

Effective February 17, 2026 we use a new February 2026 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.

32 total changes • 31 possible breaking changes

Table/column	Change type	Old name
`CUSTOM_FIELDS`
table	New Table	`CUSTOM_FIELDS`
`CUSTOMER_CUSTOM_FIELD`
column	Discontinued Column	`choice`
column	Discontinued Column	`created_datetime`
column	Discontinued Column	`data_type`
column	Discontinued Column	`deactivated_datetime`
column	Discontinued Column	`description`
column	Discontinued Column	`external_id`
column	Discontinued Column	`input_type`
column	Discontinued Column	`label`
column	Discontinued Column	`managed_type`
column	Discontinued Column	`object_type`
column	Discontinued Column	`priority`
column	Discontinued Column	`required`
column	Discontinued Column	`updated_datetime`
`TICKET_CUSTOM_FIELD`
column	Discontinued Column	`choice`
column	Discontinued Column	`confidence`
column	Discontinued Column	`confirmed`
column	Discontinued Column	`created_datetime`
column	Discontinued Column	`data_type`
column	Discontinued Column	`deactivated_datetime`
column	Discontinued Column	`description`
column	Discontinued Column	`display`
column	Discontinued Column	`external_id`
column	Discontinued Column	`input_type`
column	Discontinued Column	`label`
column	Discontinued Column	`managed_type`
column	Discontinued Column	`modified`
column	Discontinued Column	`object_type`
column	Discontinued Column	`predicted`
column	Discontinued Column	`priority`
column	Discontinued Column	`required`
column	Discontinued Column	`updated_datetime`

GRIN

Effective February 16, 2026 we use a new February 2026 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.

2 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`MEDIA_LIBRARY_CONTENT`
column	New Column		`mentions`
`MEDIA_LIBRARY_CONTENT_MENTION`
table	Discontinued Table	`MEDIA_LIBRARY_CONTENT_MENTION`		Data is available in the `MEDIA_LIBRARY_CONTENT` table.

JustCall

Effective February 16, 2026 we use a new February 2026 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.

33 total changes • 16 possible breaking changes

Table/column	Change type	Old name	New name
`CALL`
column	Discontinued Column	`justcall_ai_call_score`
column	Discontinued Column	`justcall_ai_call_score_parameters_call_etiquette`
column	Discontinued Column	`justcall_ai_call_score_parameters_customer_sentiment_score`
column	Discontinued Column	`justcall_ai_call_score_parameters_de_escalation`
column	Discontinued Column	`justcall_ai_call_score_parameters_dead_air_time`
column	Discontinued Column	`justcall_ai_call_score_parameters_empathy`
column	Discontinued Column	`justcall_ai_call_score_parameters_filler_word`
column	Discontinued Column	`justcall_ai_call_score_parameters_greeting`
column	Discontinued Column	`justcall_ai_call_score_parameters_monologue_duration`
column	Discontinued Column	`justcall_ai_call_score_parameters_talk_listen_ratio`
column	Discontinued Column	`justcall_ai_call_score_parameters_words_per_minute`
column	Discontinued Column	`justcall_ai_call_summary`
column	Discontinued Column	`justcall_ai_customer_sentiment`
column	Discontinued Column	`justcall_ai_manual_call_score`
`CALL_AI_DATA_JUSTCALL`
table	New Table		`CALL_AI_DATA_JUSTCALL`
`CALL_AI_DATA_JUSTCALL_MOMENT`
table	New Table		`CALL_AI_DATA_JUSTCALL_MOMENT`
`CALL_AI_DATA_JUSTCALL_SMART_CHAPTER`
table	New Table		`CALL_AI_DATA_JUSTCALL_SMART_CHAPTER`
`CALL_AI_DATA_JUSTCALL_TAGS`
table	New Table		`CALL_AI_DATA_JUSTCALL_TAGS`
`CALL_AI_DATA_JUSTCALL_TRANSCRIPTION`
table	New Table		`CALL_AI_DATA_JUSTCALL_TRANSCRIPTION`
`CALL_AI_DATA_SALES_DIALER`
table	New Table		`CALL_AI_DATA_SALES_DIALER`
`CALL_AI_DATA_SALES_DIALER_MOMENT`
table	New Table		`CALL_AI_DATA_SALES_DIALER_MOMENT`
`CALL_AI_DATA_SALES_DIALER_SMART_CHAPTER`
table	New Table		`CALL_AI_DATA_SALES_DIALER_SMART_CHAPTER`
`CALL_AI_DATA_SALES_DIALER_TAGS`
table	New Table		`CALL_AI_DATA_SALES_DIALER_TAGS`
`CALL_AI_DATA_SALES_DIALER_TRANSCRIPTION`
table	New Table		`CALL_AI_DATA_SALES_DIALER_TRANSCRIPTION`
`CALL_AI_MOMENT`
table	Discontinued Table	`CALL_AI_MOMENT`
`CALL_AI_TAG`
table	Discontinued Table	`CALL_AI_TAG`
`MEETING_AI_DATA`
table	New Table		`MEETING_AI_DATA`
`MEETING_AI_DATA_INSTANCE_MOMENT`
table	New Table		`MEETING_AI_DATA_INSTANCE_MOMENT`
`MEETING_AI_DATA_INVITEE_EMAIL`
table	New Table		`MEETING_AI_DATA_INVITEE_EMAIL`
`MEETING_AI_DATA_SMART_CHAPTER`
table	New Table		`MEETING_AI_DATA_SMART_CHAPTER`
`MEETING_AI_DATA_SPEAKER`
table	New Table		`MEETING_AI_DATA_SPEAKER`
`MEETING_AI_DATA_TAGS`
table	New Table		`MEETING_AI_DATA_TAGS`
`MEETING_AI_DATA_TRANSCRIPTION`
table	New Table		`MEETING_AI_DATA_TRANSCRIPTION`

Klaviyo

We have added two new tables, FORM and FORM_VERSION, to capture form and form version history data for our Klaviyo connector. We are gradually rolling out these changes to all existing connections.

Lob

Effective February 26, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

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.

8 total changes • 8 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CHECK_THUMBNAIL`
column	Discontinued Column	`_fivetran_id` 🔑
column	Primary Key Change		`index` 🔑	Added to primary key.
`LETTER_THUMBNAIL`
column	Discontinued Column	`_fivetran_id` 🔑
column	Primary Key Change		`index` 🔑	Added to primary key.
`POSTCARD_THUMBNAIL`
column	Discontinued Column	`_fivetran_id` 🔑
column	Primary Key Change		`index` 🔑	Added to primary key.
`SELF_MAILER_THUMBNAIL`
column	Discontinued Column	`_fivetran_id` 🔑
column	Primary Key Change		`index` 🔑	Added to primary key.

MNTN

Effective February 12, 2026 we use a new February 2026 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.

3 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CAMPAIGN_GROUP_INFO (new table name: CAMPAIGN_INFO)`
table	Rename Table	`CAMPAIGN_GROUP_INFO`	`CAMPAIGN_INFO`	Entity has been renamed
`CREATIVE_GROUP_INFO (new table name: CREATIVE_INFO)`
table	Rename Table	`CREATIVE_GROUP_INFO`	`CREATIVE_INFO`	Entity has been renamed
`CREATIVE_INFO (new table name: AD_INFO)`
table	Rename Table	`CREATIVE_INFO`	`AD_INFO`	Entity has been renamed

PagerDuty

Effective February 20, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

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

8 total changes • 0 possible breaking changes

Table/column	Change type	New name
`RAW_INCIDENT`
table	New Table	`RAW_INCIDENT`
`RAW_INCIDENT_ACKNOWLEDGED_USER_ID`
table	New Table	`RAW_INCIDENT_ACKNOWLEDGED_USER_ID`
`RAW_INCIDENT_ACKNOWLEDGED_USER_NAME`
table	New Table	`RAW_INCIDENT_ACKNOWLEDGED_USER_NAME`
`RAW_INCIDENT_ASSIGNED_USER_ID`
table	New Table	`RAW_INCIDENT_ASSIGNED_USER_ID`
`RAW_INCIDENT_ASSIGNED_USER_NAME`
table	New Table	`RAW_INCIDENT_ASSIGNED_USER_NAME`
`RAW_INCIDENT_JOINED_USER_ID`
table	New Table	`RAW_INCIDENT_JOINED_USER_ID`
`RAW_INCIDENT_JOINED_USER_NAME`
table	New Table	`RAW_INCIDENT_JOINED_USER_NAME`
`RAW_INCIDENT_RESPONSE`
table	New Table	`RAW_INCIDENT_RESPONSE`

Pipedrive

We have added the following new tables:

ACTIVITY_ATTENDEES
ACTIVITY_FIELD
ACTIVITY_FIELD_OPTION
ACTIVITY_FIELD_SUBFIELD
PRODUCT_PRICE

Data synced into these new tables will not contribute toward your MAR until March 15, 2026.

We have removed the PRODUCT_PRICE_HISTORY table.

We have made the following changes to the ACTIVITY table:

Removed the following columns:

Column Name	Notes
`assigned_to_user_id`	Data is already available in the `owner_id` column.
`attendees`	Data is now available in the `ACTIVITY_ATTENDEES` table.
`deal_dropbox_bcc`
`last_notification_time`
`last_notification_user_id`
`person_dropbox_bcc`
`reference_id`
`reference_type`
`source_timezone`
`update_user_id`

Renamed the following columns:

Old Name	New Name	Notes
`active_flag`	`_fivetran_deleted`	`_fivetran_deleted = true` indicates the record is inactive.
`busy_flag`	`busy`
`created_date`	`add_time`
`custom_Priority`	`priority`	The renamed column (`priority`) now stores priority IDs instead of labels.
`custom_Project`	`project_id`
`user_id`	`owner_id`

We have made the following changes to the DEAL_HISTORY table:

Removed the following columns:
Column Name Notes
cc_email Pipedrive no longer provides any data for this column.
custom_Currency of ACV
custom_Currency of ARR
custom_Currency of MRR
pipeline_deal_probability
pipeline_name

Column Name	Notes
`cc_email`	Pipedrive no longer provides any data for this column.
`custom_Currency of ACV`
`custom_Currency of ARR`
`custom_Currency of MRR`
`pipeline_deal_probability`
`pipeline_name`

Renamed the following columns:

Old Name	New Name	Notes
`active_flag`	`_fivetran_deleted`	`_fivetran_deleted = true` indicates the record is inactive.
`created_date`	`add_time`
`custom_ACV`	`acv`
`custom_arr`	`arr`
`custom_Archive status`	`is_archived`	The renamed column (`is_archived`) now stores archive IDs instead of labels.
`custom_Archive time`	`archive_time`
`custom_Source channel`	`channel`	The renamed column (`channel`) now stores channel IDs instead of labels.
`custom_Source channel ID`	`channel_id`
`custom_Source origin`	`origin`	The renamed column (`origin`) now stores origin IDs instead of labels.
`custom_Source origin ID`	`origin_id`
`label`	`label_ids`
`user_id`	`user_id`

We have made the following changes to the ORGANIZATION table:

Added a new column, label_ids
Removed the label column

Renamed the following columns:

Old Name	New Name	Notes
`active_flag`	`_fivetran_deleted`	`_fivetran_deleted = true` indicates the record is inactive.
`cc_email`	`smart_bcc_email`
`created_date`	`add_time`
`custom_Annual revenue`	`annual_revenue`
`custom_Industry`	`industry`
`custom_LinkedIn profile`	`linkedin`
`custom_Number of employees`	`employee_count`
`custom_Website`	`website`

We have made the following changes to the PERSON table:

Added a new column, label_ids
Removed the label column

Renamed the following columns:

Old Name	New Name	Notes
`active_flag`	`_fivetran_deleted`	`_fivetran_deleted = true` indicates the record is inactive.
`created_date`	`add_time`
`custom_Birthday`	`birthday`
`custom_City/town/village/locality of Postal address`	`postal_address_locality`
`custom_Country of Postal address`	`postal_address_country`
`custom_District/sublocality of Postal address`	`postal_address_sublocality`
`custom_Full/combined address of Postal address`	`postal_address_formatted_address`
`custom_House number of Postal address`	`postal_address_street_number`
`custom_Instant messenger`	`im`
`custom_Job title`	`job_title`
`custom_Notes`	`notes`
`custom_Postal address`	`postal_address`
`custom_Region of Postal address`	`postal_address_admin_area_level_2`
`custom_State/county of Postal address`	`postal_address_admin_area_level_1`
`custom_Street/road name of Postal address`	`postal_address_route`
`custom_ZIP/Postal code of Postal address`	`postal_address_postal_code`

We have made the following changes to the PIPELINE table:

Removed the selected and url_title columns
Renamed the following columns:
Old Name New Name Notes
active_flag _fivetran_deleted _fivetran_deleted = true indicates the record is inactive.
created_date add_time

We have renamed the following columns of the PRODUCT table:

Old Name	New Name	Notes
`active_flag`	`_fivetran_deleted`	`_fivetran_deleted = true` indicates the record is inactive.
`created_date`	`add_time`

We have made the following changes to the STAGE table:

Removed the pipeline_deal_probability and pipeline_name columns
Renamed the following columns:
Old Name New Name Notes
active_flag _fivetran_deleted _fivetran_deleted = true indicates the record is inactive.
created_date add_time

We now sync only the user ID from the custom fields of the User type. Previously, we synced a JSON file containing user details from these fields. We have made this update to align with Pipedrive changes.

For all renamed columns, we will temporarily maintain two versions of each column, one with the old name and one with the new name, and sync data into both. This dual-column setup will remain in place until March 31, 2026. On March 31, 2026, we will permanently remove the columns with the old names and retain only the columns with the new names.

Pylon Support Platform

Effective February 20, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

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

11 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CONTACT`
column	New Column	`custom_*`
`ISSUE_FOLLOWER`
table	New Table	`ISSUE_FOLLOWER`
`KNOWLEDGE_BASE`
table	New Table	`KNOWLEDGE_BASE`
`KNOWLEDGE_BASE_SUPPORTED_LANGUAGE`
table	New Table	`KNOWLEDGE_BASE_SUPPORTED_LANGUAGE`
`MESSAGE`
table	New Table	`MESSAGE`
`TAGS`
table	New Table	`TAGS`
`TEAM`
table	New Table	`TEAM`
`TEAM_USER`
table	New Table	`TEAM_USER`
`TICKET_FORM`
table	New Table	`TICKET_FORM`
`TICKET_FORM_FIELD`
table	New Table	`TICKET_FORM_FIELD`
`USER_ROLE`
table	New Table	`USER_ROLE`

Ramp

Effective February 2, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

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

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`REIMBURSEMENT_ACCOUTING_FIELD_SELECTION`
column	New Column	`external_code`
`REIMBURSEMENT_LINE_ITEM_ACCOUNTING_FIELD_SELECTION`
column	New Column	`external_code`
`TRANSACTION`
column	New Column	`limit_id`
`TRANSACTION_ACCOUNTING_FIELD_SELECTION`
column	New Column	`external_code`
`TRANSACTION_LINE_ITEM_ACCOUNTING_FIELD_SELECTION`
column	New Column	`external_code`

SafetyCulture

Effective February 18, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`COURSE`
table	New Table	`COURSE`
`COURSE_PROGRESS`
table	New Table	`COURSE_PROGRESS`

Sprout Social

We have added three new tables:

CASES
CASE_MESSAGE
CASE_TAG

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

sticky.io

Effective February 10, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`ORDER_CUSTOM_FIELD`
table	New Table	`ORDER_CUSTOM_FIELD`
`ORDER_CUSTOM_FIELD_VALUE`
table	New Table	`ORDER_CUSTOM_FIELD_VALUE`

Talkdesk

We have added the following new tables:

CASES
CASE_CUSTOM_FIELD
CASE_DICT_FIELD
CASE_FIELD
CASE_NOTE

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

TikTok Ads

We've added support for the ad_id_v2 dimension for custom reports. This dimension is mutually exclusive with the ad_id dimension and only syncs data for upgraded smart plus ads.

Twilio

We have added the following new TaskRouter API tables:

WORKSPACE contains workspace data from Twilio TaskRouter, which are organizational containers for TaskRouter resources.
WORKER contains worker data representing TaskRouter agents who handle tasks, including their availability status and activity information.
TASK contains task data representing work items that need to be assigned to workers within TaskRouter workflows.
TASK_QUEUE contains task queue data that organize and prioritize tasks before they are assigned to workers.
TASK_RESERVATION contains reservation data that links tasks to workers, tracking the status of task assignments and worker acceptance.
ACTIVITY contains activity data representing worker states (e.g., Available, Offline, Break) within TaskRouter.
EVENT contains event data that logs all activities and state changes within TaskRouter workspaces.
TASK_CHANNEL contains task channel data that categorize tasks by communication type (e.g., voice, SMS, chat).
WORKFLOW contains workflow data that defines the routing logic for assigning tasks to workers based on business rules.

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

UKG Pro

Effective February 12, 2026 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes.

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

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`EMPLOYEE`
column	New Column			`address_longitude`

Workday Financial Management

We have added two new columns, use_for and use_for_tenanted, to the BUSINESS_ENTITY_COMMUNICATION_USAGE table.

Workday HCM

We have added two new columns, use_for and use_for_tenanted, to the COMMUNICATION_USAGE table.

Yahoo Display Ads on Yahoo Japan

Effective February 24, 2026 we use a new February 2026 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.

23 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`AD`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	New Column		`account_name`
column	New Column		`ad_group_labels`
column	New Column		`ad_group_name`
column	New Column		`ad_group_user_status`
column	New Column		`campaign_delivery_type`
column	New Column		`campaign_goals`
column	New Column		`campaign_labels`
column	New Column		`campaign_name`
column	New Column		`campaign_user_status`
`REACH`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	New Column		`account_name`
column	New Column		`ad_group_name`
column	New Column		`ad_group_user_status`
column	New Column		`ad_name`
column	New Column		`ad_user_status`
column	New Column		`campaign_buying_type`
column	New Column		`campaign_delivery_type`
column	New Column		`campaign_end_date`
column	New Column		`campaign_goals`
column	New Column		`campaign_name`
column	New Column		`campaign_start_date`
column	New Column		`campaign_user_status`

Younium

Effective February 19, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`USAGE`
table	New Table			`USAGE`

Zip

Effective February 10, 2026 we use a new February 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.

26 total changes • 9 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`APPROVAL`
column	New Column		`parent_queue_id`
column	New Column		`parent_queue_level`
column	New Column		`parent_queue_name`
column	New Column		`queue_id`
column	New Column		`queue_level`
column	New Column		`queue_name`
`INVOICE_APPROVAL`
column	Primary Key Change	`id` 🔑	`id`	No longer a primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`ITEM_ACCOUNT`
column	Discontinued Column	`key`
column	Discontinued Column	`lookup_active`
column	Discontinued Column	`lookup_external_id`
column	Discontinued Column	`lookup_name`
column	Discontinued Column	`purchase_order_line_item_id` 🔑		No longer a primary key.
column	Discontinued Column	`show_in_zip`
column	New Column		`active`
column	New Column		`external_id`
column	New Column		`type`
`ITEM_ACCOUNT_LOOKUP_SUBSIDIARY`
table	Discontinued Table	`ITEM_ACCOUNT_LOOKUP_SUBSIDIARY`
`ITEM_ACCOUNT_SUBSIDIARY`
table	New Table		`ITEM_ACCOUNT_SUBSIDIARY`
`QUEUE`
table	New Table		`QUEUE`
`QUEUE_BILL_APPROVALS_AND_INVOICE_ASSIGNMENT_CONDITION`
table	New Table		`QUEUE_BILL_APPROVALS_AND_INVOICE_ASSIGNMENT_CONDITION`
`QUEUE_MEMBER`
table	New Table		`QUEUE_MEMBER`
`QUEUE_OWNER`
table	New Table		`QUEUE_OWNER`
`QUEUE_PAYOUT_APPROVALS_CONDITION`
table	New Table		`QUEUE_PAYOUT_APPROVALS_CONDITION`
`QUEUE_PO_CHANGE_ORDER_WORKFLOWS_CONDITION`
table	New Table		`QUEUE_PO_CHANGE_ORDER_WORKFLOWS_CONDITION`
`QUEUE_PURCHASE_REQUEST_WORKFLOWS_CONDITION`
table	New Table		`QUEUE_PURCHASE_REQUEST_WORKFLOWS_CONDITION`

Zoom

Effective February 12, 2026 we use a new February 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

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
`WEBINAR_TRACKING_SOURCE`
column	Rename Column		`registrationr_count`	`registration_count`

Improvements

Amazon S3

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

Appcues

We have added a new drop-down menu, Region, to the connection setup form. You can now specify the Appcues region from which you want to sync the data. We have also added a new config parameter, region, to the Fivetran REST API.

Azure Blob Storage

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

Box

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

Collibra

We have fixed a bug that prevented all issue records from being synced into the ISSUE table. We will trigger a re-sync to ensure the data is fully up to date.

Dropbox

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

Email

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

Facebook Ads

We no longer support the status filter for Insights API requests. Previously, we filtered insights data by the following entity statuses:

ACTIVE
PAUSED
DELETED
PENDING_REVIEW
DISAPPROVED
PREAPPROVED
PENDING_BILLING_INFO
CAMPAIGN_PAUSED
ARCHIVED
ADSET_PAUSED
IN_PROCESS
WITH_ISSUES

Status filtering could cause data discrepancies in certain scenarios. With this change, we now retrieve insights for all entities regardless of their status, ensuring more complete and accurate reporting data.

We are gradually rolling out this change to all Facebook Ads connectors.

FTP

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

Google Ads

We've added support for the ai_max_search_term_ad_combination_view resource for custom reports.

For a full list of supported resources for custom reports, see our Custom Reports documentation.

Google Campaign Manager 360

We've updated the Google Campaign Manager 360 connector to use the latest API version (v5). This update includes the following schema changes:

We've added a new column, eu_political_ads_declaration, to the CAMPAIGN table.
We've added a new column, eu_political_ads_declaration, to the ADVERTISER table.
We've discontinued support for the dynamic_asset_selection and creative_asset_selection_default_asset_id columns in the CREATIVE table. The latest version of the API no longer supports these columns.

This update applies to all Google Campaign Manager 360 connections.

Google Cloud Storage

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

Google Drive

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

We have made the following enhancements to the Unstructured file replication feature in our Google Drive connector:

We now support syncing the Google Drive labels attached to your files to enable filtering and categorizing files in your downstream applications. By default, we sync these labels when you choose Replicate unstructured files in the setup form.
We now support the Group membership expansion permission to enable access to information about individual members within a group.

For more information, see our setup instructions.

HubSpot

We have simplified how the HubSpot connector handles merged records to prevent duplicate data. When you merge records in HubSpot, Fivetran now marks the merged records as deleted (_fivetran_deleted = true). This change enables you to filter out inactive records without using complex joins.

We now support HubSpot's Services API to sync service records from your HubSpot account. To support this enhancement, we have added the following new tables:

SERVICE
SERVICE_COMPANY
SERVICE_CONTACT
SERVICE_DEAL
SERVICE_ENGAGEMENT
SERVICE_PIPELINE
SERVICE_PIPELINE_STAGE
SERVICE_PROPERTY_HISTORY
SERVICE_TICKET

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

Impact Brand

We now sync the CONTRACT table for contracts with the following statuses:

Active
Declined
Expired
Pending
Upcoming

Previously, we synced this table only for Active contracts. We are gradually rolling out this change to all existing connections.

Impact Partner

We have updated our sync strategy, and we now sync one month of historical data for the CLICK table. Previously, we synced three months of historical data.

Katana

We have fixed an issue in the variant_config_attribute child table of the VARIANT table where data was not syncing due to an incorrectly defined path. The table now correctly includes this column.

Klaviyo

We now sync both active and archived flows for the FLOW table during full syncs. Previously, only active flows were included, which could result in missing data when flows were archived.

Lattice

You can now select a region-specific subdomain to sync your data. To support this enhancement, we’ve made the following updates:

Added a new drop-down menu, Subdomain, to the connection setup form.
Added a new parameter, sub_domain, to the Fivetran REST API.

LinkedIn Ad Analytics

The LinkedIn Ad Analytics connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Managed Data Lake Service

We have improved how we handle Delta Lake table metadata to prevent incompatible schema issues and maintain consistent schema definitions for your data lake tables. When we create a Delta Lake table, we now drop the existing table metadata before creating the new table. We also display a warning on your Fivetran dashboard whenever we perform this process for your data lake.

We now stage orphan files before permanent deletion. When we identify orphan files during our maintenance operations, we first move them to a separate orphans folder within your table directory. We move orphan data files to orphans/data and orphan metadata files to orphans/metadata.

Files moved to the orphans folder are permanently deleted in subsequent maintenance runs.

For more information about table maintenance operations, see our Managed Data Lake Service documentation.

Oracle Business Intelligence Publisher

The Oracle Business Intelligence Publisher connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Paylocity

We’ve added support for multiple Company IDs. You can now enter multiple comma-separated Company IDs when creating a new Paylocity connection.

PostgreSQL destination

When creating new decimal columns in your destination, we now create the column as:

decimal(precision, scale) when both precision and scale of the column are defined
decimal when precision and scale are not specified or are greater than or equal to 1000
text when precision or scale exceeds the PostgreSQL limits

We are gradually rolling out this change to all existing destinations. To apply the new mapping to existing decimal columns, drop and re-sync them.

Qualtrics

The Qualtrics connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Qualtrics's priority-first syncs fetch the most recent 7 days' worth of data from the DIRECTORY_CONTACT, DISTRIBUTION, SURVEY_RESPONSE and TICKET tables and their child tables.

To learn more, see our priority-first sync documentation.

Connections created after February 3, 2026 will have priority-first sync enabled by default. For existing connections, we are gradually rolling out this change.

S3-Compatible Storage

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

SFTP

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

SharePoint

We now support syncing XLS/XLSX/XLSM files to multiple destination tables and handling file patterns. To support this enhancement, we have made the following changes to the connection setup form:

Moved the Configure files section below the Format section to enable file type selection before configuration.
Moved the following sub-fields from the Format section to the Configure files section of the setup form:
- Manual cell reference
- Spreadsheet to find data to be synced
- Cell reference for syncs

For more information, see our setup instructions. We are gradually rolling out these enhancements to all existing connections.

UKG Pro

We have changed the sync strategy for the EMPLOYEE_JOB_HISTORY table. We now re-import the EMPLOYEE_JOB_HISTORY table every week to capture updates and deletes. Previously, we incrementally synced this table to capture updates. We are gradually rolling out this enhancement to all existing connections.

Workday RaaS

We’re migrating all Workday RaaS connections created before March 12, 2025, to support multiple reports in a single connection. This migration requires no action on your part. If you want to use this new capability, you can update your existing connections at any time to include additional reports.

Wrike

We now re-import the FOLDER_PROJECT table and its child tables during every sync to capture updates and deletes.

Xero

We now support a new authentication method, Custom connection, for the Xero connector. You can set up a custom connection only if the Xero organization you select is located in Australia, New Zealand, the UK, or the United States. New Xero connections created in these regions after February 18, 2026, support the Custom connection authentication. For more information, see our setup instruction.

We are updating the authentication methods for the Xero connector and discontinuing the legacy Fivetran-managed app. As part of this update, migrate the existing connections to a supported authentication method based on your Xero organization's region.

Effective March 2, 2026, we will no longer support the Fivetran-managed app. If your existing connection uses the Fivetran-managed app and your organization belongs to Australia, New Zealand, the United Kingdom, or the United States, you must migrate and re-authenticate using Custom Connections. However, migration is optional for the Web app connections in these supported regions.
Existing connections using the Fivetran-managed app with Xero organizations that belong to any region other than Australia, New Zealand, the United Kingdom, and the United States, must migrate to a Web app.
Existing connections using the Web app and belonging to regions outside those that support Custom connection do not need to migrate.

Connections that require migration display a warning message on the connection details page. You must migrate all affected Xero connections before March 2, 2026 to avoid interruptions to your data syncs.

For more information, see our Xero documentation.

Zoom

We now sync scheduled meetings up to 12 months in the future into the MEETING table.

REST API Improvements

Expose `supports_history_mode` for table configuration responses

We’ve extended the table response model for the Connection Schema resource endpoints by adding a new field, supports_history_mode.

This boolean field indicates whether a table supports history mode.

February 2026

Activations

Connector SDK

fivetran-connector-sdk PyPI package

Lite Connectors

Row Filtering - added support for the Lite connectors

Logs

Account-Level External Logging

sql_query log events deprecated

Quickstart Transformations

Custom variable support for Quickstart Data Models

Sunset destinations

Azure Data Lake Storage

S3 Data Lake

Transformations for dbt Core

Updated dbt Quickstart packages

Upstream Transformations

Schema changes

Aha!

Algolia

Ashby

Canvas Data 2 by Instructure

Ceridian Dayforce

Coupa

Front

Gorgias

GRIN

JustCall

Klaviyo

Lob

MNTN

PagerDuty

Pipedrive

Pylon Support Platform

Ramp

SafetyCulture

Sprout Social

sticky.io

Talkdesk

TikTok Ads

Twilio

UKG Pro

Workday Financial Management

Workday HCM

Yahoo Display Ads on Yahoo Japan

Younium

Zip

Zoom

Improvements

Amazon S3

Appcues

Azure Blob Storage

Box

Collibra

Dropbox

Email

Facebook Ads

FTP

Google Ads

Google Campaign Manager 360

Google Cloud Storage

Google Drive

HubSpot

Impact Brand

Impact Partner

Katana

Klaviyo

Lattice

LinkedIn Ad Analytics

Managed Data Lake Service

Oracle Business Intelligence Publisher

Paylocity

PostgreSQL destination

Qualtrics

S3-Compatible Storage

SFTP

SharePoint

UKG Pro

Workday RaaS

Wrike

`fivetran-connector-sdk` PyPI package

Expose `supports_history_mode` for table configuration responses