April 2025

Connector SDK

`fivetran-connector-sdk` PyPI package

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

A bug fix around error logging when using exit().
Improvements to the data type inference for unknown types.
Updated tester.
Minor improvements and bug fixes.

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

A bug fix for reading the correct state value when using the fivetran debug command.
Improved error logging when using exit() in connector.py.
Improved data type inference for unknown types.
Updated tester.
Minor improvements and bug fixes.

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

Optimized performance by eliminating redundant method calls.
Updated tester.
Minor improvements and bug fixes.

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

Improved logging messages.
Updated tester.
Minor improvements and bug fixes.

Improved Schema Tab

We've improved the schema tab for all connections.

You can now view key details at a glance, without hovering on the table or column line. If these features are available for the connector, you can now immediately:

Re-sync your tables
Switch between history and soft delete mode
Filtering data
See the column data type
Hash or unhash a column

Learn more in our Schema tab documentation.

NOTE: This update does not yet apply to SAP connectors.

Schema tab view

Lite Connectors

Lite connectors are now available for the following sources:

Managed Data Lakes Service

We have added support for a new storage provider, Google Cloud Storage (GCS), to Managed Data Lakes Service. The new storage provider is currently in beta.

Read our Managed Data Lakes Service documentation.

New connectors

Amazon DSP

Amazon DSP is a demand-side platform for advertisers. Read our Amazon DSP connector documentation.

Schema changes

AccuLynx

Effective April 1, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to enhance its usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`LEAD_HISTORY`
table	New Table	`LEAD_HISTORY`
`MILESTONE_HISTORY`
table	New Table	`MILESTONE_HISTORY`

Ada

Effective April 11, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to align with source changes.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`MESSAGE`
column	New Column	`in_response_to`
column	New Column	`record_last_updated`

Amazon Selling Partner

We have added the following new reports to provide details about sales and payment:

CUSTOMER_SHIPMENT_SALES_REPORT
FEE_PREVIEW_REPORT
FULFILLED_SHIPMENTS_DATA_GENERAL_REPORT
FULFILLMENT_CUSTOMER_SHIPMENT_PROMOTION_REPORT
LONG_TERM_STORAGE_FEE_CHARGES_REPORT
ORDERS_REPORT
REIMBURSEMENTS_REPORT

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

Appcues

Effective April 17, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

7 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`EVENT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	New Column		`attributes`
`EVENT_ATTRIBUTE`
table	Discontinued Table	`EVENT_ATTRIBUTE`
`MOBILE`
column	New Column		`tags`
`MOBILE_TAG`
table	Discontinued Table	`MOBILE_TAG`
`PIN`
column	New Column		`tags`
`PIN_TAG`
table	Discontinued Table	`PIN_TAG`

Appfigures

Effective April 16, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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
`PRODUCT_DEVICE`
table	Discontinued Table		`PRODUCT_DEVICE`		Data is now available in the `devices` column of the `PRODUCT` table.

Autodesk BIM 360

Effective April 10, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`PROJECT_ACC`
table	New Table	`PROJECT_ACC`
`PROJECT_ACC_PRODUCT`
table	New Table	`PROJECT_ACC_PRODUCT`

Bizzabo

Effective April 21, 2025 we use a new April 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`SESSIONS_CHECKIN`
column	Primary Key Change	`created`	`created` 🔑	Added to primary key.
column	Primary Key Change	`ticket_id`	`ticket_id` 🔑	Added to primary key.

Brightcove

Effective April 9, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

12 total changes • 12 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`LIVE_ANALYTICS_TIME_SERIES_CCU_DATA_POINT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	Rename Column	`_timestamp` 🔑	`time_stamp` 🔑
`LIVE_ANALYTICS_TIME_SERIES_FINGERPRINT_COUNT_DATA_POINT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	Rename Column	`_timestamp` 🔑	`time_stamp` 🔑
`LIVE_ANALYTICS_TIME_SERIES_SECOND_VIEWED_DATA_POINT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	Rename Column	`_timestamp` 🔑	`time_stamp` 🔑
`LIVE_ANALYTICS_TIME_SERIES_VIDEO_IMPRESSION_DATA_POINT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	Rename Column	`_timestamp` 🔑	`time_stamp` 🔑
`LIVE_ANALYTICS_TIME_SERIES_VIDEO_VIEW_DATA_POINT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	Rename Column	`_timestamp` 🔑	`time_stamp` 🔑
`VIDEO_TEXT_TRACK`
column	Rename Column	`default_`	`is_default`
`VIDEO_VARIANT`
column	Rename Column	`language_`	`languages`

Checkout.com

Effective April 3, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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
`FINANCIAL_ACTION_BY_PAYOUT_REPORT`
table	New Table			`FINANCIAL_ACTION_BY_PAYOUT_REPORT`

Coupa

We now support SUPPLIER_INFORMATION table and its child table.

For information, see supplier information API doc.

Crossbeam

Effective April 28, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to align with source changes.

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.

64 total changes • 55 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ACCOUNT_FILTER_EXPRESSION`
table	Discontinued Table	`ACCOUNT_FILTER_EXPRESSION`
`ACCOUNT_FILTER_PART`
table	Discontinued Table	`ACCOUNT_FILTER_PART`
`ACCOUNT_FILTER_PART_OPERAND`
table	Discontinued Table	`ACCOUNT_FILTER_PART_OPERAND`
`ACCOUNT_RECORD`
table	New Table		`ACCOUNT_RECORD`
`ACCOUNT_RECORD_POPULATION`
table	New Table		`ACCOUNT_RECORD_POPULATION`
`LEAD_RECORD`
table	New Table		`LEAD_RECORD`
`LEAD_RECORD_POPULATION`
table	New Table		`LEAD_RECORD_POPULATION`
`NOTIFICATION_CONFIG_EMAIL`
table	Discontinued Table	`NOTIFICATION_CONFIG_EMAIL`
`OVERLAP_ACCOUNT`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`OVERLAP_ACCOUNT_PARTNER_POPULATION`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`OVERLAP_ACCOUNT_PARTNER_SOURCE_DATA`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`OVERLAP_ACCOUNT_POPULATION`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`OVERLAP_LEAD`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`OVERLAP_LEAD_PARTNER_POPULATION`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`OVERLAP_LEAD_PARTNER_SOURCE_DATA`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`OVERLAP_LEAD_POPULATION`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`PARTNER`
column	Discontinued Column	`clearbit_domain`
column	Discontinued Column	`logo_url`
column	Discontinued Column	`partnership_authorizer_email`
column	Discontinued Column	`partnership_authorizer_first_name`
column	Discontinued Column	`partnership_authorizer_gravatar_url`
column	Discontinued Column	`partnership_authorizer_id`
column	Discontinued Column	`partnership_authorizer_last_name`
column	Discontinued Column	`partnership_authorizer_picture_url`
column	Discontinued Column	`partnership_created_at`
column	Discontinued Column	`url`
column	Discontinued Column	`uuid`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`PARTNER_OVERLAP_COUNT`
table	Discontinued Table	`PARTNER_OVERLAP_COUNT`
`PARTNER_POPULATION`
column	Discontinued Column	`partner_organization_id`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`PARTNER_PROPOSAL`
table	Discontinued Table	`PARTNER_PROPOSAL`
`PARTNER_PROPOSAL_RECEIVED`
table	Discontinued Table	`PARTNER_PROPOSAL_RECEIVED`
`PARTNER_TAG`
column	Discontinued Column	`partner_organization_id`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
column	Primary Key Change		`partner_id` 🔑	Added to primary key.
`POPULATION`
column	Discontinued Column	`base_schema`
column	Discontinued Column	`base_table`
column	Discontinued Column	`current_version_first_processed_at`
column	Discontinued Column	`current_version_id`
column	Discontinued Column	`current_version_is_active`
column	Discontinued Column	`source_id`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`RECORD`
table	Discontinued Table	`RECORD`		Data is available in the `ACCOUNT_RECORD` and `LEAD_RECORD` tables.
`REPORT`
column	Discontinued Column	`created_at`
column	Discontinued Column	`created_by_user_id`
column	Discontinued Column	`partner_organization_id`
column	Discontinued Column	`sort`
column	Discontinued Column	`updated_at`
column	Discontinued Column	`updated_by_user_id`
column	New Column		`organization_id`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
column	New Column		`partner_impact_scores`
column	New Column		`partner_standard_population`
column	New Column		`tag_id`
`REPORT_COLUMN`
table	Discontinued Table	`REPORT_COLUMN`
`REPORT_FILTER`
table	Discontinued Table	`REPORT_FILTER`
`REPORT_FILTER_EXPRESSION`
table	Discontinued Table	`REPORT_FILTER_EXPRESSION`
`REPORT_FILTER_PART`
table	Discontinued Table	`REPORT_FILTER_PART`
`REPORT_FILTER_PART_OPERAND`
table	Discontinued Table	`REPORT_FILTER_PART_OPERAND`
`REPORT_NOTIFICATION_CONFIG`
table	Discontinued Table	`REPORT_NOTIFICATION_CONFIG`
`REPORT_PARTNER_POPULATION`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`REPORT_POPULATION`
column	Primary Key Change		`organization_uuid` 🔑	Added to primary key.
`USER_ORGANIZATION`
table	New Table		`USER_ORGANIZATION`

dbt Cloud

Effective April 16, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

15 total changes • 11 possible breaking changes

Table/column	Change type	Old name	New name
`CONNECTION`
column	Discontinued Column	`allow_sso`
column	Discontinued Column	`client_session_keep_alive`
column	Discontinued Column	`created_by_id`
column	Discontinued Column	`created_by_service_token_id`
column	Discontinued Column	`database`
column	Discontinued Column	`dbt_project_id`
column	Discontinued Column	`is_configured_for_oauth`
column	Discontinued Column	`role`
column	Discontinued Column	`state`
column	Discontinued Column	`type`
column	Discontinued Column	`warehouse`
column	New Column		`adapter_version`
column	New Column		`is_ssh_tunnel_enabled`
column	New Column		`oauth_configuration_id`
column	New Column		`platform_metadata_credentials_id`

Docebo

Effective April 1, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to align with source changes.

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 • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CATALOG_CONTENT`
table	New Table		`CATALOG_CONTENT`
`CATALOGUE_ITEM`
table	Discontinued Table	`CATALOGUE_ITEM`		Data is available in the `CATALOG_CONTENT` table.
`COURSE`
column	New Column		`category_name` 🔑

Exact Online

Effective April 10, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to enhance its usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`TRANSACTION_LINE`
column	New Column	`amount_fc`
column	New Column	`gl_account_description`

Flywheel Digital

Effective April 7, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

5 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ONLINE_STORE_SEARCH_RESULT`
column	Primary Key Change		`report_date` 🔑	New primary key.
`PRODUCT`
column	Primary Key Change	`report_date`	`report_date` 🔑	Added to primary key.
`PRODUCT_PROMOTION`
column	Primary Key Change	`report_date`	`report_date` 🔑	Added to primary key.
`SEARCH_TERM`
column	Primary Key Change	`report_date`	`report_date` 🔑	Added to primary key.
column	New Column		`type`

GitHub

We have added the following tables to support GitHub Copilot metrics:

COPILOT_METRIC
IDE_CODE_COMPLETIONS_TOTAL_LANGUAGE
IDE_CODE_COMPLETION_EDITOR
IDE_CODE_COMPLETION_EDITOR_MODEL
IDE_CODE_COMPLETION_EDITOR_MODEL_LANGUAGE
IDE_CHAT_EDITOR
IDE_CHAT_EDITOR_MODEL
DOTCOM_CHAT_MODEL
DOTCOM_PULL_REQUEST_REPOSITORY
DOTCOM_PULL_REQUEST_REPOSITORY_MODEL
COPILOT_METRIC_TEAM
IDE_CODE_COMPLETIONS_TOTAL_LANGUAGE_TEAM
IDE_CODE_COMPLETION_EDITOR_TEAM
IDE_CODE_COMPLETION_EDITOR_MODEL_TEAM
IDE_CODE_COMPLETION_EDITOR_MODEL_LANGUAGE_TEAM
IDE_CHAT_EDITOR_TEAM
IDE_CHAT_EDITOR_MODEL_TEAM
DOTCOM_CHAT_MODEL_TEAM
DOTCOM_PULL_REQUEST_REPOSITORY_TEAM
DOTCOM_PULL_REQUEST_REPOSITORY_MODEL_TEAM

Google Ads

We now support the following fields for the AD_GROUP_AD custom report:

ad_group_ad.ad.app_pre_registration_ad.descriptions,
ad_group_ad.ad.app_pre_registration_ad.headlines,
ad_group_ad.ad.app_pre_registration_ad.images,
ad_group_ad.ad.app_pre_registration_ad.youtube_videos,

We've added a new prebuilt report, SEARCH_TERM_KEYWORD_STATS. We are slowly rolling that report out to all existing connectors.

Healthie

Effective April 24, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to enhance its usability.

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`USER_POLICY`
table	New Table	`USER_POLICY`
`USER_POLICY_BENEFIT`
table	New Table	`USER_POLICY_BENEFIT`
`USER_POLICY_CLAIM_ELIGIBILITY`
table	New Table	`USER_POLICY_CLAIM_ELIGIBILITY`
`USER_POLICY_CPT_CODE`
table	New Table	`USER_POLICY_CPT_CODE`
`USER_POLICY_ICD_CODE`
table	New Table	`USER_POLICY_ICD_CODE`

HubSpot

We have changed the primary key for the PROPERTY table. We now use the combination of _fivetran_id and hubspot_object columns as its composite primary key. Previously, only _fivetran_id was its primary key.

Instagram Business

We've added the owner_id column to the MEDIA_HISTORY table.

We've also added the following columns to the USER_HISTORY table:

profile_picture_url
has_profile_pic
is_published

We've also added the following columns to the MEDIA_INSIGHTS table:

carousel_album_views
carousel_album_shares
reel_views
story_views
story_shares
video_photo_views
video_photo_shares

We have upgraded our Instagram Business connector to version 22.0 of the Graph API. We are gradually rolling out this improvement to all existing connectors. For more information about the changes, see Graph API's changelog.

Due to deprecations in Graph API version 22.0, we've removed the following columns from the MEDIA_INSIGHTS table:

reel_clips_replays_count
reel_aggregated_all_plays_count
reel_plays

Starting from Graph API version 22.0, all impression columns will only be supported for media created before July 2, 2024. All media created after this date will have impression columns set to null. We will continue to support the impression metric on media created before this date.

This change applies to the following columns:

carousel_album_impressions
story_impressions
video_photo_impressions

Integral Ad Science

Effective April 2, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

6 total changes • 6 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`REPORT`
column	Rename Column	`brand_safety_risk_%`	`brand_safety_risk_percentage`
column	Rename Column	`brand_suitability_fail_%`	`brand_suitability_fail_percentage`
column	Rename Column	`invisible_url_%`	`invisible_url_percentage`
column	Rename Column	`out_of_geo_%`	`out_of_geo_percentage`
column	Rename Column	`target_language_mismatch_%`	`target_language_mismatch_percentage`
column	Primary Key Change		`media_partner_id` 🔑	New primary key.

Jira Align

Effective April 28, 2025 we use a new April 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

74 total changes • 19 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CAPABILITY_COUNTRY`
table	New Table		`CAPABILITY_COUNTRY`
`CAPABILITY_CUSTOMER`
table	New Table		`CAPABILITY_CUSTOMER`
`CAPABILITY_LINK`
table	New Table		`CAPABILITY_LINK`
`CAPABILITY_POINT`
table	New Table		`CAPABILITY_POINT`
`CAPABILITY_PROGRAM`
table	New Table		`CAPABILITY_PROGRAM`
`CAPABILITY_RELEASE`
table	New Table		`CAPABILITY_RELEASE`
`DEFECT_RELEASE_VEHICLE`
table	New Table		`DEFECT_RELEASE_VEHICLE`
`EPIC_CUSTOMER`
table	New Table		`EPIC_CUSTOMER`
`EPIC_POINT`
table	New Table		`EPIC_POINT`
`FEATURE_ADDITIONAL_PROGRAM`
table	New Table		`FEATURE_ADDITIONAL_PROGRAM`
`FEATURE_AFFECTED_COUNTRY`
table	New Table		`FEATURE_AFFECTED_COUNTRY`
`FEATURE_CUSTOMER`
table	New Table		`FEATURE_CUSTOMER`
`FEATURE_LINK`
table	New Table		`FEATURE_LINK`
`FEATURE_OBJECTIVE`
table	New Table		`FEATURE_OBJECTIVE`
`FEATURE_RELEASE_VEHICLE`
table	New Table		`FEATURE_RELEASE_VEHICLE`
`GOAL_LINK`
table	New Table		`GOAL_LINK`
`GOAL_SNAP_SHOT`
table	New Table		`GOAL_SNAP_SHOT`
`LINK`
table	Discontinued Table	`LINK`		Data is available in the `CAPABILITY_LINK`, `FEATURE_LINK`, `GOAL_LINK`, `MILESTONE_LINK`, `OBJECTIVE_LINK`, `RISK_LINK`, `STORY_LINK`, and `THEME_LINK` tables.
`MILESTONE`
table	New Table		`MILESTONE`
`MILESTONE_CUSTOM_FIELD`
table	New Table		`MILESTONE_CUSTOM_FIELD`
`MILESTONE_DEPENDENCY`
table	New Table		`MILESTONE_DEPENDENCY`
`MILESTONE_EPIC`
table	New Table		`MILESTONE_EPIC`
`MILESTONE_FEATURE`
table	New Table		`MILESTONE_FEATURE`
`MILESTONE_IMPEDIMENT`
table	New Table		`MILESTONE_IMPEDIMENT`
`MILESTONE_LINK`
table	New Table		`MILESTONE_LINK`
`MILESTONE_PROGRAM`
table	New Table		`MILESTONE_PROGRAM`
`MILESTONE_RELEASE`
table	New Table		`MILESTONE_RELEASE`
`MILESTONE_RISK`
table	New Table		`MILESTONE_RISK`
`MILESTONE_TEAM`
table	New Table		`MILESTONE_TEAM`
`OBJECTIVE`
table	New Table		`OBJECTIVE`
`OBJECTIVE_CUSTOM_FIELD`
table	New Table		`OBJECTIVE_CUSTOM_FIELD`
`OBJECTIVE_DEPENDENCY`
table	New Table		`OBJECTIVE_DEPENDENCY`
`OBJECTIVE_EPIC`
table	New Table		`OBJECTIVE_EPIC`
`OBJECTIVE_FEATURE`
table	New Table		`OBJECTIVE_FEATURE`
`OBJECTIVE_IMPEDIMENT`
table	New Table		`OBJECTIVE_IMPEDIMENT`
`OBJECTIVE_LINK`
table	New Table		`OBJECTIVE_LINK`
`OBJECTIVE_PROGRAM`
table	New Table		`OBJECTIVE_PROGRAM`
`OBJECTIVE_RELEASE`
table	New Table		`OBJECTIVE_RELEASE`
`OBJECTIVE_RISK`
table	New Table		`OBJECTIVE_RISK`
`OBJECTIVE_TEAM`
table	New Table		`OBJECTIVE_TEAM`
`PRODUCT_SNAP_SHOT`
table	New Table		`PRODUCT_SNAP_SHOT`
`PRODUCT_TYPE`
table	Discontinued Table	`PRODUCT_TYPE`		Data is available in the `RELEASE_PRODUCT` and `SNAP_SHOT_PRODUCT` tables.
`RELEASE_PRODUCT`
table	New Table		`RELEASE_PRODUCT`
`RELEASE_PROGRAM`
table	New Table		`RELEASE_PROGRAM`
`RELEASE_VEHICLE_FEATURE`
table	New Table		`RELEASE_VEHICLE_FEATURE`
`RELEASE_VEHICLE_PROGRAM`
table	New Table		`RELEASE_VEHICLE_PROGRAM`
`RELEASE_VEHICLE_TEAM`
table	New Table		`RELEASE_VEHICLE_TEAM`
`RISK_LINK`
table	New Table		`RISK_LINK`
`SNAP_SHOT_DIVISION`
column	Discontinued Column	`fund`
`SNAP_SHOT_FUNDING_LEVEL`
table	New Table		`SNAP_SHOT_FUNDING_LEVEL`
`SNAP_SHOT_RELEASE`
table	New Table		`SNAP_SHOT_RELEASE`
`STORY_LINK`
table	New Table		`STORY_LINK`
`STORY_RELEASE_VEHICLE`
table	New Table		`STORY_RELEASE_VEHICLE`
`TARGET`
table	Discontinued Table	`TARGET`		Data is available in the `MILESTONE` and `OBJECTIVE` tables.
`TARGET_CUSTOM_FIELD`
table	Discontinued Table	`TARGET_CUSTOM_FIELD`		Data is available in the `MILESTONE_CUSTOM_FIELD` and `OBJECTIVE_CUSTOM_FIELD` tables.
`TARGET_DEPENDENCY`
table	Discontinued Table	`TARGET_DEPENDENCY`		Data is available in the `MILESTONE_DEPENDENCY` and `OBJECTIVE_DEPENDENCY` tables.
`TARGET_EPIC`
table	Discontinued Table	`TARGET_EPIC`		Data is available in the `MILESTONE_EPIC` and `OBJECTIVE_EPIC` tables.
`TARGET_IMPEDIMENT`
table	Discontinued Table	`TARGET_IMPEDIMENT`		Data is available in the `MILESTONE_IMPEDIMENT` and `OBJECTIVE_IMPEDIMENT` tables.
`TARGET_RISK`
table	Discontinued Table	`TARGET_RISK`		Data is available in the `MILESTONE_RISK` and `OBJECTIVE_RISK` tables.
`TEAM_COMMUNITY`
column	Primary Key Change	`team_id`	`team_id` 🔑	Added to primary key.
`THEME_LINK`
table	New Table		`THEME_LINK`
`THEME_PROGRAM`
table	New Table		`THEME_PROGRAM`
`THEME_RELEASE`
table	New Table		`THEME_RELEASE`
`TYPE_COUNTRY`
table	Discontinued Table	`TYPE_COUNTRY`		Data is available in the `CAPABILITY_COUNTRY` and `FEATURE_AFFECTED_COUNTRY` tables.
`TYPE_CUSTOMER`
table	Discontinued Table	`TYPE_CUSTOMER`		Data is available in the `CAPABILITY_CUSTOMER`, `EPIC_CUSTOMER`, `FEATURE_CUSTOMER`, and `VALUE_STREAM_CUSTOMER` tables.
`TYPE_FEATURE`
table	Discontinued Table	`TYPE_FEATURE`		Data is available in the `MILESTONE_FEATURE`, `OBJECTIVE_FEATURE`, and `RELEASE_VEHICLE_FEATURE` tables.
`TYPE_POINT`
table	Discontinued Table	`TYPE_POINT`		Data is available in the `CAPABILITY_POINT` and `EPIC_POINT` tables.
`TYPE_PROGRAM`
table	Discontinued Table	`TYPE_PROGRAM`		Data is available in the `CAPABILITY_PROGRAM`, `FEATURE_ADDITIONAL_PROGRAM`, `MILESTONE_PROGRAM`, `OBJECTIVE_PROGRAM`, `RELEASE_PROGRAM`, `RELEASE_VEHICLE_PROGRAM`, `THEME_PROGRAM`, and `VALUE_STREAM_PROGRAM` tables.
`TYPE_RELEASE`
table	Discontinued Table	`TYPE_RELEASE`		Data is available in the `CAPABILITY_RELEASE`, `MILESTONE_RELEASE`, `OBJECTIVE_RELEASE`, `SNAP_SHOT_RELEASE`, and `THEME_RELEASE` tables.
`TYPE_RELEASE_VEHICLE`
table	Discontinued Table	`TYPE_RELEASE_VEHICLE`		Data is available in the `DEFECT_RELEASE_VEHICLE`, `FEATURE_RELEASE_VEHICLE`, and `STORY_RELEASE_VEHICLE` tables.
`TYPE_SNAP_SHOT`
table	Discontinued Table	`TYPE_SNAP_SHOT`		Data is available in the `GOAL_SNAP_SHOT` and `PRODUCT_SNAP_SHOT` tables.
`TYPE_TEAM`
table	Discontinued Table	`TYPE_TEAM`		Data is available in the `MILESTONE_TEAM`, `OBJECTIVE_TEAM`, and `RELEASE_VEHICLE_TEAM` tables.
`VALUE_STREAM_CUSTOMER`
table	New Table		`VALUE_STREAM_CUSTOMER`
`VALUE_STREAM_PROGRAM`
table	New Table		`VALUE_STREAM_PROGRAM`

Linear

Effective April 16, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

9 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`INITIATIVE`
table	New Table		`INITIATIVE`
`INITIATIVE_HISTORY`
table	New Table		`INITIATIVE_HISTORY`
`INITIATIVE_TO_PROJECT`
table	New Table		`INITIATIVE_TO_PROJECT`
`PROJECT_STATUS`
table	New Table		`PROJECT_STATUS`
`PROJECT_TEAM`
table	New Table		`PROJECT_TEAM`
`PROJECT_UPDATE`
table	New Table		`PROJECT_UPDATE`
`PROJECT_UPDATE_COMMENT`
table	New Table		`PROJECT_UPDATE_COMMENT`
`PROJECT_UPDATE_REACTION`
table	New Table		`PROJECT_UPDATE_REACTION`
`TEAM_PROJECT`
table	Discontinued Table	`TEAM_PROJECT`		Data is available in the `PROJECT_TEAM` table.

Maxio Chargify

Effective April 16, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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
`INVOICE`
column	New Column			`public_url`

Maxio SaaSOptics

Effective April 4, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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
`INVOICE_LINE_ITEM`
column	New Column			`number`

Microsoft Advertising

We have extended the free sync period until May 1, 2025 for the following metadata and reporting tables:

ASSET_GROUP_ATTRIBUTE_HISTORY
ASSET_GROUP_HISTORY
PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_MAX_DAILY_REPORT
PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_MAX_HOURLY_REPORT
PRODUCT_DIMENSION_PERFORMANCE_MAX_DAILY_REPORT
PRODUCT_DIMENSION_PERFORMANCE_MAX_HOURLY_REPORT

Be sure to exclude the tables that you don't want to sync and count towards paid MAR before May 1, 2025.

Navan

Effective April 24, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

11 total changes • 0 possible breaking changes

Table/column	Change type	New name
`TRANSACTION`
column	New Column	`accrued_rebate_amount`
column	New Column	`card_nickname`
column	New Column	`direct_reimbursement_fee_amount`
column	New Column	`est_doc_date`
column	New Column	`est_doc_link`
column	New Column	`est_doc_number`
column	New Column	`navan_booking_uuid`
column	New Column	`rebate_type`
column	New Column	`reporting_transaction_id`
column	New Column	`statement_id`
column	New Column	`vcf_transaction_reference_number`

Okta

We have made the following changes to the PROFILE_MAPPING table:

Added a new child table, PROFILE_MAPPING_PROPERTY
Added two new columns, source_name and target_name

We have added a new column, credentials_recovery_question, to the USERS table.

Opsgenie

Effective April 7, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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 • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`INTEGRATION_ACTION_CONDITION`
table	Discontinued Table	`INTEGRATION_ACTION_CONDITION`		Data now available in the `INTEGRATION_ACTION_INFO_ACKNOWLEDGE_CONDITION`, and `INTEGRATION_ACTION_CREATE_CONDITION` tables.
`INTEGRATION_ACTION_CREATE`
column	Rename Column	`responders`	`responder`
`INTEGRATION_ACTION_CREATE_CONDITION`
table	New Table		`INTEGRATION_ACTION_CREATE_CONDITION`
`INTEGRATION_ACTION_INFO`
table	Discontinued Table	`INTEGRATION_ACTION_INFO`		Data now available in the `INTEGRATION_ACTION_INFO_ACKNOWLEDGE`, `INTEGRATION_ACTION_INFO_ADDNOTE`, and `INTEGRATION_ACTION_INFO_CLOSE tables.`
`INTEGRATION_ACTION_INFO_ACKNOWLEDGE`
table	New Table		`INTEGRATION_ACTION_INFO_ACKNOWLEDGE`
`INTEGRATION_ACTION_INFO_ACKNOWLEDGE_CONDITION`
table	New Table		`INTEGRATION_ACTION_INFO_ACKNOWLEDGE_CONDITION`
`INTEGRATION_ACTION_INFO_ADDNOTE`
table	New Table		`INTEGRATION_ACTION_INFO_ADDNOTE`
`INTEGRATION_ACTION_INFO_CLOSE`
table	New Table		`INTEGRATION_ACTION_INFO_CLOSE`

Ordway

Effective April 4, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

7 total changes • 0 possible breaking changes

Table/column	Change type	New name
`SUBSCRIPTION_PLAN`
column	New Column	`cmrr`
column	New Column	`default_from_plan`
column	New Column	`discounted_cmrr`
column	New Column	`last_charge_date`
column	New Column	`prepayment_period`
column	New Column	`recognition_end_date`
`SUBSCRIPTION_PLAN_TIER`
table	New Table	`SUBSCRIPTION_PLAN_TIER`

Effective April 8, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

62 total changes • 7 possible breaking changes

Table/column	Change type	Old name	New name
`CHARGE`
table	Discontinued Table	`CHARGE`
`CHARGE_CUSTOM_FIELD`
table	Discontinued Table	`CHARGE_CUSTOM_FIELD`
`CHARGE_TIER`
table	Discontinued Table	`CHARGE_TIER`
`CHARGE_TRANSACTION_POSTING_ENTRIES`
table	Discontinued Table	`CHARGE_TRANSACTION_POSTING_ENTRIES`
`CONTACT`
table	Discontinued Table	`CONTACT`
`CONTACT_CUSTOM_FIELD`
table	Discontinued Table	`CONTACT_CUSTOM_FIELD`
`CUSTOMER_CONTACT`
column	New Column		`address_1`
column	New Column		`address_2`
column	New Column		`city`
column	New Column		`country`
column	New Column		`county`
column	New Column		`created_by`
column	New Column		`created_date`
column	New Column		`department`
column	New Column		`display_name`
column	New Column		`email`
column	New Column		`first_name`
column	New Column		`is_unrelated_contact`
column	New Column		`job_title`
column	New Column		`last_name`
column	New Column		`mobile`
column	New Column		`notes`
column	New Column		`phone`
column	New Column		`salesforce_id`
column	New Column		`state`
column	New Column		`updated_by`
column	New Column		`updated_date`
column	New Column		`zip`
`PLAN_CHARGE`
column	Discontinued Column	`billing_date`
column	New Column		`auto_refill_prepayment_units`
column	New Column		`backcharge_current_period`
column	New Column		`billing_day`
column	New Column		`billing_period`
column	New Column		`charge_billing_date`
column	New Column		`charge_inherited_product`
column	New Column		`dealhub_name`
column	New Column		`defaults_from_product`
column	New Column		`description`
column	New Column		`effective_date`
column	New Column		`included_units`
column	New Column		`line_no`
column	New Column		`list_price`
column	New Column		`name`
column	New Column		`original_type`
column	New Column		`prepaid_units_enable`
column	New Column		`prepaid_units_expiry`
column	New Column		`prepayment_amount`
column	New Column		`pricing_model`
column	New Column		`product_id`
column	New Column		`recognition_start_date`
column	New Column		`refill_prepaid_units_for`
column	New Column		`refill_qty`
column	New Column		`refund_units_on_cancel`
column	New Column		`revenue_rule_id`
column	New Column		`salesforce_charge_id`
column	New Column		`salesforce_id`
column	New Column		`timing`
column	New Column		`transaction_price`
column	New Column		`type`
column	New Column		`unit_of_measure`
`PLAN_CHARGE_TIER`
table	New Table		`PLAN_CHARGE_TIER`
`PLAN_CHARGE_TRANSACTION_POSTING_ENTRIES`
table	New Table		`PLAN_CHARGE_TRANSACTION_POSTING_ENTRIES`

PagerDuty

Effective April 15, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

36 total changes • 0 possible breaking changes

Table/column	Change type	New name
`ANALYTICS_METRIC_SERVICE`
table	New Table	`ANALYTICS_METRIC_SERVICE`
`INCIDENT`
column	New Column	`alert_counts_all`
column	New Column	`alert_counts_resolved`
column	New Column	`alert_counts_triggered`
column	New Column	`alert_grouping_active`
column	New Column	`alert_grouping_ended_at`
column	New Column	`alert_grouping_started_at`
column	New Column	`alerts_grouping_type`
column	New Column	`basic_alert_grouping_expires_at`
column	New Column	`body_details`
column	New Column	`incident_type_name`
column	New Column	`is_basic_alert_grouping`
column	New Column	`priority_account_id`
column	New Column	`priority_color`
column	New Column	`priority_created_at`
column	New Column	`priority_description`
column	New Column	`priority_html_url`
column	New Column	`priority_name`
column	New Column	`priority_order`
column	New Column	`priority_schema_version`
column	New Column	`priority_self`
column	New Column	`priority_type`
column	New Column	`priority_updated_at`
`INCIDENT_CUSTOM_FIELD_VALUE`
table	New Table	`INCIDENT_CUSTOM_FIELD_VALUE`
`LOG_ENTRIES`
column	New Column	`channel_changeset_application_fields_id`
column	New Column	`channel_changeset_application_fields_name`
column	New Column	`channel_changeset_application_fields_namespace`
column	New Column	`channel_changeset_application_fields_old_value`
column	New Column	`channel_changeset_application_fields_value`
column	New Column	`channel_changeset_customer_fields_id`
column	New Column	`channel_changeset_customer_fields_name`
column	New Column	`channel_changeset_customer_fields_namespace`
column	New Column	`channel_changeset_customer_fields_old_value`
column	New Column	`channel_changeset_customer_fields_value`
column	New Column	`escalation_policy_id`
column	New Column	`responder_id`

Paychex

Effective April 17, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

7 total changes • 7 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COMPANY_PAY_FREQUENCY`
column	Primary Key Change	`company_id` 🔑	`company_id`	No longer a primary key.
column	Discontinued Column	`index` 🔑		No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`WORKER_PAY_STANDARD`
column	Discontinued Column	`index` 🔑		No longer a primary key.
column	Primary Key Change	`worker_id` 🔑	`worker_id`	No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`WORKER_STATUS`
table	Discontinued Table	`WORKER_STATUS`		Data is available in the `WORKER` table.

Persona

Effective April 21, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to resolve a data integrity issue. The data of the discontinued columns is available in the custom_* columns of the INQUIRY table.

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 • 23 possible breaking changes

Table/column	Change type	Old name
`INQUIRY`
column	Discontinued Column	`address_lookup_report_resolved_city`
column	Discontinued Column	`address_lookup_report_resolved_postal_code`
column	Discontinued Column	`address_lookup_report_resolved_street_1`
column	Discontinued Column	`address_lookup_report_resolved_street_2`
column	Discontinued Column	`address_lookup_report_resolved_subdivision`
column	Discontinued Column	`current_government_id`
column	Discontinued Column	`current_government_id_1`
column	Discontinued Column	`current_government_id_2`
column	Discontinued Column	`current_selfie`
column	Discontinued Column	`current_selfie-1`
column	Discontinued Column	`document_9_f_8_b_current_document`
column	Discontinued Column	`ekata_score`
column	Discontinued Column	`ipqs_score`
column	Discontinued Column	`ipqs_transaction_score`
column	Discontinued Column	`phone_carrier`
column	Discontinued Column	`placeholder_city`
column	Discontinued Column	`placeholder_country_code`
column	Discontinued Column	`placeholder_postal_code`
column	Discontinued Column	`placeholder_street_1`
column	Discontinued Column	`placeholder_street_2`
column	Discontinued Column	`placeholder_subdivision`
column	Discontinued Column	`selected_id_class_1`
column	Discontinued Column	`selected_id_class_2`

Personio

Effective April 21, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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
`EMPLOYEE_ABSENCE_BALANCE`
column	Primary Key Change		`employee_id`	`employee_id` 🔑	Added to primary key.

Procore

Effective April 21, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to fix a bug.

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
`BUDGET_VIEW_SNAPSHOT_DETAIL_SEGMENT_ITEM`
column	Primary Key Change	`id` 🔑	`id`	No longer a primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`BUDGET_VIEW_SNAPSHOT_DETAIL_SEGMENT_ITEM_PATH`
column	Discontinued Column	`budget_view_snapshot_detail_segment_item_id` 🔑		No longer a primary key.
column	Primary Key Change		`budget_view_snapshot_detail_segment_item_index` 🔑	New primary key.
`BUDGET_VIEW_SNAPSHOT_DETAIL_SEGMENT_ITEM_PATH_CODE`
column	Discontinued Column	`budget_view_snapshot_detail_segment_item_id` 🔑		No longer a primary key.
column	Primary Key Change		`budget_view_snapshot_detail_segment_item_index` 🔑	New primary key.

Proofpoint Security Awareness

Effective April 16, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`PHISHING_EXTENDED`
column	Primary Key Change		`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.

Sage Intacct

We have resolved a data integrity issue in the Sage Intacct connector that impacts the GLACCOUNTBALANCE table. We have updated the primary key RECORDNO calculation for this table.

Earlier, we calculated the primary key as a hash of the following columns:

accountno
bookid
classid
customerid
departmentid
employeeid
itemid
location_id
period
projectid
vendorid
warehouseid

Now, we calculate the primary key as a hash of the following columns:

accountno
accountrec
accounttitle
bookid
classdimkey
classid
classname
contractdimkey
contractid
contractname
createdby
currency
customerdimkey
customerid
customername
departmentid
employeedimkey
employeeid
employeename
endbal
forbal
gldimcompensation_type
gldimservice_line
itemdimkey
itemid
itemname
location_id
locationno
modifiedby
openbal
period
projectdimkey
projectid
projectname
recordno
record_url
taskdimkey
taskid
taskname
totadjcredit
totadjdebit
totcredit
totdebit
vendordimkey
vendorid
vendorname
whencreated

To correct historical data in your destination:

You can initiate a free resync for the GLACCOUNTBALANCE table until May 5, 2025, from Fivetran.
If you choose not to resync, only incremental data from April 17, 2025, will reflect the updated RECORDNO calculation.

NOTE:
Resyncs will result in a large number of API calls to Sage Intacct, which may lead to additional charges at the source as per the Sage Intacct API pricing model.
GLACCOUNTBALANCE is a high-volume table, so sync times may increase during the resync.
You might notice an increase in MAR as we synced previously missed rows.

Sentry

Effective April 7, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

20 total changes • 20 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ORGANIZATION_RELEASE`
column	Discontinued Column	`organization_slug` 🔑		No longer a primary key.
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ORGANIZATION_RELEASE_COMMIT`
column	Discontinued Column	`organization_release_organization_slug` 🔑		No longer a primary key.
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ORGANIZATION_RELEASE_LAST_DEPLOY`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ORGANIZATION_RELEASE_PROJECT`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ORGANIZATION_RELEASE_PROJECT_PLATFORM`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ORGANIZATION_REPOSITORY`
column	Discontinued Column	`organization_slug` 🔑		No longer a primary key.
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`PROJECT_SERVICE_HOOK`
column	Discontinued Column	`organization_slug` 🔑		No longer a primary key.
column	Discontinued Column	`project_slug` 🔑		No longer a primary key.
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
column	Primary Key Change		`project_id` 🔑	Added to primary key.
`PROJECT_USER`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
`REPOSITORY_COMMIT`
column	Discontinued Column	`organization_slug` 🔑		No longer a primary key.
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`REPOSITORY_COMMIT_AUTHOR_EMAIL`
column	Discontinued Column	`orgainzation_slug` 🔑		No longer a primary key.
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`REPOSITORY_COMMIT_RELEASE`
column	Discontinued Column	`orgainzation_slug` 🔑		No longer a primary key.
column	Primary Key Change		`organization_id` 🔑	Added to primary key.

ServiceTitan

Effective April 4, 2025 we use a new April 2025 Schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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
`TECHNICIAN`
column	New Column			`team`

Sigma Computing

Effective April 17, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`TEAM_MEMBER`
column	Primary Key Change		`team_id`	`team_id` 🔑	Added to primary key.

SkuVault

Effective April 10, 2025 we use a new April 2025 Schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to fix a bug.

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
`EXTERNAL_WAREHOUSE_QUANTITIY`
column	Discontinued Column		`external_warehouse_id`

SmartHR

Effective April 1, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`EMPLOYEE_CUSTOM_FIELD`
column	Discontinued Column	`value` 🔑		No longer a primary key.
column	Primary Key Change		`index` 🔑	Added to primary key.

Tableau

Effective April 14, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

6 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name
`DATA_SOURCE_REVISION`
column	Discontinued Column	`created_at`
column	New Column		`published_at`
column	New Column		`size_in_byte`
`WORKBOOK_REVISION`
column	Discontinued Column	`created_at`
column	New Column		`published_at`
column	New Column		`size_in_byte`

UKG Pro

Effective April 9, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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_CHANGE`
column	New Column			`employee_number`

Visma

Effective April 22, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to fix a bug.

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.

15 total changes • 13 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`SUPPLIER_INVOICE`
column	Primary Key Change	`id` 🔑	`supplier_reference`	No longer a primary key.
column	Rename Column	`id` 🔑	`supplier_reference`
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
column	New Column		`payment_ref_no`
column	New Column		`time_stamp`
`SUPPLIER_INVOICE_ATTACHMENT`
column	Discontinued Column	`supplier_invoice_id` 🔑		No longer a primary key.
column	Primary Key Change		`supplier_invoice_fivetran_id` 🔑	New primary key.
`SUPPLIER_INVOICE_LINE`
column	Discontinued Column	`supplier_invoice_id` 🔑		No longer a primary key.
column	Primary Key Change		`supplier_invoice_fivetran_id` 🔑	New primary key.
`SUPPLIER_INVOICE_LINE_ATTACHMENT`
column	Discontinued Column	`supplier_invoice_id` 🔑		No longer a primary key.
column	Primary Key Change		`supplier_invoice_fivetran_id` 🔑	New primary key.
`SUPPLIER_INVOICE_LINE_SUB_ACCOUNT_SEGMENT`
column	Discontinued Column	`supplier_invoice_id` 🔑		No longer a primary key.
column	Primary Key Change		`supplier_invoice_fivetran_id` 🔑	New primary key.
`SUPPLIER_INVOICE_TAX_DETAIL_LINE`
column	Discontinued Column	`supplier_invoice_id` 🔑		No longer a primary key.
column	Primary Key Change		`supplier_invoice_fivetran_id` 🔑	New primary key.

Walmart Marketplace

Effective April 19, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

36 total changes • 36 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ADD_ON_SERVICE`
column	Primary Key Change	`add_on_service` 🔑	`add_on_service`	No longer a primary key.
column	Primary Key Change		`product_id` 🔑	New primary key.
`FEED_ITEM_DETAIL`
column	Primary Key Change	`mart_id` 🔑	`mart_id`	No longer a primary key.
`FULFILLMENT_ORDER_SHIPMENT`
column	Primary Key Change	`tracking_no` 🔑	`tracking_no`	No longer a primary key.
`FULFILLMENT_ORDER_SHIPMENT_DATE`
column	Primary Key Change	`datetype_id` 🔑	`datetype_id`	No longer a primary key.
column	Primary Key Change		`seller_order_id` 🔑	New primary key.
`FULFILLMENT_ORDER_SHIPMENT_LINE`
column	Primary Key Change	`fulfiller_line_id` 🔑	`fulfiller_line_id`	No longer a primary key.
column	Primary Key Change	`shipment_line_no` 🔑	`shipment_line_no`	No longer a primary key.
column	Primary Key Change		`index` 🔑	New primary key.
column	Primary Key Change		`seller_order_id` 🔑	New primary key.
`FULFILLMENT_ORDER_STATUS`
column	Primary Key Change	`order_channel_id` 🔑	`order_channel_id`	No longer a primary key.
`ITEM_SEARCH`
table	Discontinued Table	`ITEM_SEARCH`
`ITEM_SEARCH_CATEGORY`
table	Discontinued Table	`ITEM_SEARCH_CATEGORY`
`ITEM_SEARCH_DATA_VARIANT_VALUE`
table	Discontinued Table	`ITEM_SEARCH_DATA_VARIANT_VALUE`
`ITEM_SEARCH_IMAGE`
table	Discontinued Table	`ITEM_SEARCH_IMAGE`
`ITEM_SEARCH_PROPERTY_VARIANT_DATA`
table	Discontinued Table	`ITEM_SEARCH_PROPERTY_VARIANT_DATA`
`ITEM_SEARCH_PROPERTY_VARIANT_META`
table	Discontinued Table	`ITEM_SEARCH_PROPERTY_VARIANT_META`
`ITEM_UNPUBLISHED_REASON`
column	Primary Key Change	`unpublished_reason` 🔑	`unpublished_reason`	No longer a primary key.
`RETURN_LINE`
column	Primary Key Change		`customer_order_id` 🔑	New primary key.
`RETURN_LINE_GROUP`
column	Primary Key Change		`customer_order_id` 🔑	New primary key.
`RETURN_LINE_GROUP_CARRIER_INFO_LIST`
column	Rename Column	`index` 🔑	`return_line_label_index` 🔑
column	Primary Key Change		`customer_order_id` 🔑	New primary key.
column	Primary Key Change		`return_line_group_index` 🔑	New primary key.
`RETURN_LINE_LABEL`
column	Primary Key Change		`customer_order_id` 🔑	New primary key.
`RETURN_ORDER_LINE`
column	Primary Key Change	`purchase_order_id` 🔑	`purchase_order_id`	No longer a primary key.
`RETURN_ORDER_LINE_CHARGE_REFERENCE`
column	Primary Key Change		`return_order_line_index` 🔑	New primary key.
`RETURN_ORDER_LINE_CHARGE_TAX`
column	Primary Key Change		`return_order_line_index` 🔑	New primary key.
`RETURN_ORDER_LINE_TRACKING_REFERENCE`
column	Rename Column	`return_order_tracking_index` 🔑	`return_order_line_tracking_detail_index` 🔑
column	Primary Key Change		`return_order_line_index` 🔑	New primary key.
`SHIPPING_CONFIGURATION`
column	Primary Key Change	`partner_id` 🔑	`partner_id`	No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`SHIPPING_CONFIGURATION_CATEGORY`
column	Discontinued Column	`partner_id` 🔑		No longer a primary key.
column	Primary Key Change		`shipping_configuration_fivetran_id` 🔑	New primary key.
`SHIPPING_CONFIGURATION_DETAIL`
column	Discontinued Column	`partner_id` 🔑		No longer a primary key.
column	Discontinued Column	`partner_name` 🔑		No longer a primary key.
column	Primary Key Change		`shipping_configuration_fivetran_id` 🔑	New primary key.

Workday Financial Management

We have added two new columns, customer_contract_line_id and receivable_contract_line_code, to the CUSTOMER_INVOICE_LINE table.

We have added a new column, worktag_code, to the CUSTOMER_CONTRACT_LINE_WORKTAG table.

WorkRamp

Effective April 21, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

9 total changes • 0 possible breaking changes

Table/column	Change type	New name
`EVENT_SESSION`
column	New Column	`end`
column	New Column	`start`
column	New Column	`training_class_id`
column	New Column	`zoom_meeting_id`
column	New Column	`zoom_meeting_join_url`
column	New Column	`zoom_meeting_start_url`
`EVENT_SESSION_TRAINING_CLASS_INSTRUCTOR`
table	New Table	`EVENT_SESSION_TRAINING_CLASS_INSTRUCTOR`
`SCORM`
table	New Table	`SCORM`
`SCORM_ASSIGNMENT`
table	New Table	`SCORM_ASSIGNMENT`

Xactly

Effective April 24, 2025 we use a new April 2025 Schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`QUOTA_SUMMARY`
column	Discontinued Column	`id` 🔑		No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Effective April 30, 2025 we use a new April 2025 Schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

3 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CREDIT_SUMMARY`
table	New Table	`CREDIT_SUMMARY`
`DRAW`
table	New Table	`DRAW`
`DRAW_ASSIGNMENT`
table	New Table	`DRAW_ASSIGNMENT`

Xandr

Effective April 21, 2025 we use a new April 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

5 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`DEAL_BUYER_BIDDER`
column	Primary Key Change	`bidder_id` 🔑	`bidder_id`	No longer a primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`PLACEMENT_MIME_TYPE`
column	Discontinued Column	`id`
column	Discontinued Column	`name`
column	New Column		`mime_type`

Improvements

Alchemer

We have introduced a 6-hour replay window for the SURVEY_RESPONSE table to capture any delayed updates from the source.

Amazon S3

We now support syncing files to multiple destination tables and handling file patterns. To support these features, we have made the following changes to the connector setup form:

Added the Files field and sub-fields Table name and File pattern, in the connector setup form that enables you to define destination tables and specify the file pattern names.
Renamed the Destination table field to Table group name to enable unique identification of connections that share the same destination schema name.

Also, we have discontinued the table and pattern configuration parameters for all Amazon S3 connections and will delete them by August 31, 2025.

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

Amazon Selling Partner

We have fixed a bug where we didn't accurately sync the ITEM_VENDOR_DETAIL table.

Apache Kafka destination

We can now sync data from all your source tables into a single Kafka topic. To support this feature, we have added a new toggle, Sync Data Into Single Topic, to the destination setup forms. You can enable the feature by setting this toggle to ON. For more information, see our Apache Kafka documentation.

We are gradually rolling out this feature to all existing destinations.

Azure Blob Storage

We now support syncing files to multiple destination tables and handling file patterns. To support these features, we have made the following changes to the connector setup form:

Added the Files field and sub-fields Table name and File pattern, in the connector setup form that enables you to define destination tables and specify the file pattern names.
Renamed the Destination table field to Table group name to enable unique identification of connections that share the same destination schema name.

Also, we have discontinued the table and pattern configuration parameters for all Azure Blob Storage connections and will delete them by August 31, 2025.

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

Chargebee Product Catalog 2.0

We have changed the sync strategy for the TRANSACTION table. We now re-import this table once a day to capture updates and deletes.

Eventbrite

We now sync data from the ATTENDEE and ORDERS tables from the year 2006 onward.

Factbird

We now re-import the LINE and CHANGEOVER_STOP tables and their child tables once a month to capture deletes.

Google Cloud Storage

We now support syncing files to multiple destination tables and handling file patterns. To support these features, we have made the following changes to the connector setup form:

Added the Files field and sub-fields Table name and File pattern, in the connector setup form that enables you to define destination tables and specify the file pattern names.
Renamed the Destination table field to Table group name to enable unique identification of connections that share the same destination schema name.

Also, we have discontinued the table and pattern configuration parameters for all Google Cloud Storage connections and will delete them by August 31, 2025.

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

Klarna

We have changed the sync strategy of the PAYOUT table and its child tables. We now incrementally sync these tables to capture updates. Previously, we re-imported these tables once a week to capture updates and deletes.

Liftoff

We now sync data from the REPORT table from 2020.

Managed Data Lakes Service

We have made the S3 Prefix Path (for AWS) and Prefix Path (for ADLS) fields mandatory in the destination setup form. Previously, they were optional fields.

Marketo

We have added a new field, Sync data from selected date, under the Historical Sync Time Frame dropdown in the setup form. This allows you to select the exact date up to which the backward sync will occur. The default value is Sync all historical data. You can edit the connection details and update the time frame for an existing connector.

This limit applies to the following tables:

ACTIVITY_*
DELETED_PROGRAM_MEMBERSHIP
LEAD_SEGMENT
LIST_MEMBERSHIP
MERGED_LEAD
OPPORTUNITY_MEMBERSHIP
SEGMENT

We are gradually rolling out this feature to all connections.

Monday.com

The Monday.com connector now uses API version 2025-01.

MongoDB

We no longer support the SYMBOL data type during historical syncs. When running an historical sync on a collection, we now don't attempt to sync documents where the _id field is of type SYMBOL. Learn more in our MongoDB documentation.

Ordway

The Ordway connector now supports only the SaaS Deployment model. Previously, it supported both the SaaS and Hybrid deployment models.

PostgreSQL

We have improved the handling of INET and CIDR data types.

Previously, when syncing columns with the INET data type, Fivetran preserved the original CIDR suffix even when it was the default mask (/32 for IPv4, /128 for IPv6) for some connections. This behavior caused inconsistencies compared to PostgreSQL’s internal representation.

Now, we automatically normalize INET values to align with PostgreSQL behavior:

CIDR mask is omitted when it is the default (/32 for IPv4, /128 for IPv6).
CIDR mask is preserved for non-default prefixes or when the column type is explicitly CIDR.

In addition, IPv6 addresses are now compressed according to PostgreSQL-standard formatting. For example:

'0:0:0:0:0:0:0:1/128'::inet is now stored as '::1'
'2001:0db8:0000:0000:0000:0000:0000:0001/64'::cidr becomes '2001:db8::1/64'

This change applies only to PostgreSQL connections created after April 15, 2024.

Ramp

We now sync data from the TRANSACTION table starting from the year 2019, and re-import the table once a week to capture any updates or deletes.

RetailNext

We have implemented pagination for the LOCATION table.

Retently

We now incrementally sync the following tables and their child tables:

COMPANY
CUSTOMER
OUTBOX
REPORT

To capture updates and deletes, we now re-import the CUSTOMER table and its child tables once a week.

The REPORT table now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use.

We no longer capture deletes for the following tables:

COMPANY
OUTBOX
REPORT

Row Filtering

Row filtering now supports the following operators to check column values for NULL:

Is NULL
Is not NULL

For more information, see our row filtering documentation.

Row filtering now supports the following String comparison operators:

Equal To
Not Equal To
Greater Than
Less Than
Greater Than Or Equal To
Less Than Or Equal To

For more information, see our row filtering documentation.

Salesforce

We no longer use the deleted endpoint for the CURRENCY_TYPE table. This is to avoid the issue where the endpoint incorrectly returns IDs of deactivated (but not deleted) currencies, causing them to be marked as deleted (_fivetran_deleted = true) in the destination. In Salesforce, currencies cannot be hard deleted. The is_active field in the CURRENCY_TYPE table indicates whether a currency is active or deactivated and can be used to filter out inactive currencies instead of relying on the _fivetran_deleted field. If this issue has impacted your data, we recommend a resync of the CURRENCY_TYPE table.

SAP ERP on HANA

A new version of the Fivetran NetWeaver API is now available for download: v1900263.

We optimized the process for fetching deletes by breaking it into smaller chunks, improving stability in scenarios with large volumes (20 million+) of deleted records between syncs.

ServiceNow

We have added a new field, Historical sync time frame, to the connector setup form. This allows you to select how many months' worth of historical data you want to sync. For an existing connector, you can edit the connection details and set the time frame value. For more information, see our Historical sync time frame documentation. We apply the historical sync limit to all tables. This feature has been rolled out to all connections.

ServiceTitan

We now sync all records for the following tables:

BUSINESS_UNIT
CALL
CAMPAIGN
CAMPAIGN_CATEGORY
CUSTOMER
CUSTOMER_CONTACT
EMPLOYEE
ESTIMATE
INVOICE_ITEM
JOB_HOLD_REASON
LOCATION
MEMBERSHIP
NON_JOB_APPOINTMENT
TECHNICIAN
ZONE

Previously, we synced only active records.

We also capture deletes for the above tables during every sync.

SFTP

We have made the following changes to the connector setup form to support syncing files to multiple destination tables and handling file patterns in Merge Mode:

Added Files section in the connector setup form to enable you to define tables and specify file name patterns. Sync each file pattern as a unique destination table.
Renamed the Destination table field to Table group name to enable unique identification of connections that share the same destination schema name.

Also, we have discontinued the table and pattern configuration parameters for all SFTP connections and will delete them by August 31, 2025.

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

SQL Server destination

We have improved the timestamp precision in SQL Server destinations. We now support a precision of 7 digits for seconds in timestamp values. Previously, we supported a precision of 6 digits. We are gradually rolling out this change to all existing destinations.

Tempo

To capture updates and deletes, we now re-import the WORKLOG table once a week.

The Tempo connector now supports the Hybrid Deployment model. For more information, see our setup guide.

Workday RaaS

Our connector now allows you to select between an API client and an API client for integrations on the setup page when configuring your connection. For more information, see our Workday RaaS connector documentation.

REST API Improvements

dbt Transformation and Quickstart Transformation resources removed

We have removed the dbt Transformation and Quickstart Transformation resources in our REST API. Use the Transformation Management resource instead.

April 2025

Connector SDK

fivetran-connector-sdk PyPI package

Improved Schema Tab

Lite Connectors

Managed Data Lakes Service

New connectors

Amazon DSP

Schema changes

AccuLynx

Ada

Amazon Selling Partner

Appcues

Appfigures

Autodesk BIM 360

Bizzabo

Brightcove

Checkout.com

Coupa

Crossbeam

dbt Cloud

Docebo

Exact Online

Flywheel Digital

GitHub

Google Ads

Healthie

HubSpot

Instagram Business

Integral Ad Science

Jira Align

Linear

Maxio Chargify

Maxio SaaSOptics

Microsoft Advertising

Navan

Okta

Opsgenie

Ordway

PagerDuty

Paychex

Persona

Personio

Procore

Proofpoint Security Awareness

Sage Intacct

Sentry

ServiceTitan

Sigma Computing

SkuVault

SmartHR

Tableau

UKG Pro

Visma

Walmart Marketplace

Workday Financial Management

WorkRamp

Xactly

Xandr

Improvements

Alchemer

Amazon S3

Amazon Selling Partner

Apache Kafka destination

Azure Blob Storage

Chargebee Product Catalog 2.0

Eventbrite

Factbird

Google Cloud Storage

Klarna

Liftoff

Managed Data Lakes Service

Marketo

Monday.com

MongoDB

Ordway

PostgreSQL

Ramp

RetailNext

Retently

`fivetran-connector-sdk` PyPI package