Release Notes
July 2026
We have made the following schema changes to the Recurly connector.
We've added the following new tables:
EXTERNAL_ACCOUNT_HISTORYEXTERNAL_SUBSCRIPTIONEXTERNAL_SUBSCRIPTION_PAYMENT_PHASEGIFT_CARDINVOICE_LINE_ITEMINVOICE_TAX_DETAILINVOICE_TRANSACTION_HISTORYLINE_ITEM_TAX_DETAILPLAN_ADD_ON_CURRENCY_PERCENTAGE_TIERPLAN_ADD_ON_TIER_HISTORYPLAN_SETUP_FEESSUBSCRIPTION_CREDIT_INVOICESUBSCRIPTION_RAMP_INTERVALTRANSACTION_FRAUD_INFO_RISK_RULES_TRIGGEREDUSAGE_RECORDUSAGE_RECORD_PERCENTAGE_TIERSUSAGE_RECORD_TIERS
We have added the following new columns to the ACCOUNT_HISTORY table:
account_geo_codebill_datedunning_campaign_identity_use_codehas_active_subscriptionhas_canceled_subscriptionhas_future_subscriptionhas_live_subscriptionhas_past_due_invoicehas_paused_subscriptioninvoice_template_idoverride_business_entity_idpreferred_time_zone
We have added the following new columns to the BILLING_INFO_HISTORY table:
account_geo_codebackup_payment_methodbill_datebilling_geo_codeentity_use_codehas_past_due_invoicepayment_gateway_referencespayment_method_account_typepayment_method_billing_agreement_idpayment_method_card_network_preferencepayment_method_cc_bin_countrypayment_method_funding_sourcepayment_method_gateway_attributes_account_referencepayment_method_gateway_codepayment_method_last_twopayment_method_name_on_accountpayment_method_routing_numberpayment_method_routing_number_bankpayment_method_usernameprimary_payment_method
We have added the following new columns to the SHIPPING_ADDRESS_HISTORY table:
geo_codestreet_1street_2
We have added the available_credit_amount and processing_prepayment_amount column to the ACCOUNT_BALANCE_HISTORY table.
We have added a new column, acquired_at, to the ACCOUNT_ACQUISITION_HISTORY table.
We have added a new column, subscription_id, to the COUPON_REDEMPTION_HISTORY table.
We have added the following new columns to the INVOICE_HISTORY table:
address_geo_codeaddress_name_on_accountaddress_phoneaddress_street_1address_street_2billing_info_idbusiness_entity_idcredit_paymentscustomer_notesdunning_campaign_iddunning_events_sentfinal_dunning_eventgateway_codehas_more_line_itemsobjectoriginreference_only_currency_conversion_currencyreference_only_currency_conversion_datereference_only_currency_conversion_ratereference_only_currency_conversion_sourcereference_only_currency_conversion_subtotal_in_centsreference_only_currency_conversion_tax_in_centsrefundable_amountshipping_address_geo_codeshipping_address_idshipping_address_nicknameshipping_address_objectshipping_address_street_1shipping_address_street_2shipping_address_vat_numberterms_and_conditionsused_tax_serviceuuidvat_numbervat_reverse_charge_notes
We have added the following new columns to the LINE_ITEM_HISTORY table:
avalara_service_typeavalara_transaction_typebill_for_account_iddestination_tax_address_sourceexternal_skuharmonized_system_codeitem_codeitem_idliability_gl_account_codeorigin_tax_address_sourceperformance_obligation_idquantity_decimalrefunded_quantity_decimalrevenue_gl_account_codeshipping_address_idtax_inclusiveunit_amount_decimal
We have added the following new columns to the PLAN_ADD_ON_HISTORY table:
add_on_typeavalara_service_typeavalara_transaction_typeexternal_skuharmonized_system_codeitem_codeitem_descriptionitem_iditem_nameitem_objectitem_stateliability_gl_account_idmeasured_unit_idperformance_obligation_idrevenue_gl_account_idusage_calculation_typeusage_percentageusage_timeframeusage_type
We have added the tax_inclusive and unit_amount_decimal columns to the PLAN_ADD_ON_CURRENCY_HISTORY table.
We have added the following new columns to the PLAN_HISTORY table:
allow_any_item_on_subscriptionsavalara_service_typeavalara_transaction_typedunning_campaign_idharmonized_system_codehosted_page_bypass_confirmationhosted_page_cancel_urlhosted_page_display_quantityhosted_page_success_urlliability_gl_account_idperformance_obligation_idpricing_modelrevenue_gl_account_idrevenue_schedule_typesetup_fee_liability_gl_account_idsetup_fee_performance_obligation_idsetup_fee_revenue_gl_account_idsetup_fee_revenue_schedule_typetrial_requires_billing_infovertex_transaction_type
We have added the price_segment_id and tax_inclusive columns to the PLAN_CURRENCY_HISTORY table.
We have added the following new columns to the SUBSCRIPTION_HISTORY table:
action_resultactive_invoice_idbank_account_authorized_atbilling_info_idbusiness_entity_idcredit_application_policy_modegateway_codeinvoice_collection_charge_invoice_idnet_terms_typenext_actionprice_segment_idshipping_address_objectshipping_amountshipping_method_codeshipping_method_idshipping_method_nameshipping_method_objecttaxtax_inclusivetotal
We have added the add_on_source and unit_amount_decimal columns to the SUBSCRIPTION_ADD_ON_HISTORY table.
We have added the billing_info_three_d_secure_action_result_token_id and tax_inclusive columns to the SUBSCRIPTION_CHANGE_HISTORY table.
We have added the following new columns to the TRANSACTION table:
action_resultbackup_method_usedbilling_geo_codebilling_phonefraud_info_decisionfraud_info_objectfraud_info_referencefraud_info_scoreinitiatornext_action_typenext_action_valuepayment_method_account_typepayment_method_billing_agreement_idpayment_method_card_network_preferencepayment_method_cc_bin_countrypayment_method_funding_sourcepayment_method_gateway_attribute_account_referencepayment_method_gateway_codepayment_method_last_twopayment_method_name_on_accountpayment_method_routing_numberpayment_method_routing_number_bankpayment_method_username
We have added a new column, bulk_coupon_id, to the BULK_UNIQUE_CODE table.
October 2025
We unified each connector’s pre-built dbt Core–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.
December 2024
We have added table re-sync support. Previously, we only supported connection-level re-syncs.
Event-based tables and tables with a retention period at the source don't support this feature.
You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.
November 2024
The Recurly connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
August 2024
We have made the following changes to the Schema tab for connections created on or after August 13, 2024:
- We now display all table names in lowercase
- We now display all tables, including the empty tables
- We no longer support table-level selection and deselection for syncing
We have made the following schema changes for connections created on or after August 13, 2024:
- added a new table,
SUBSCRIPTION_GIFT_CARD_MAPPING - removed the
coupon_idcolumn from the primary key of theCOUPON_DISCOUNTtable - removed the
started_with_giftandconverted_atcolumns from theSUBSCRIPTION_HISTORYtable
July 2023
We have added a new table, BULK_UNIQUE_CODE, to map bulk coupon codes with their respective unique coupon codes.
October 2022
We have released pre-built, dbt Core-compatible data models for Recurly. Find the models in Fivetran's dbt hub. Learn more in our Fivetran Data Models documentation.
March 2021
We have added two new columns, started_with_gift and converted_at, to the SUBSCRIPTION table. See Recurly's lookup subscription documentation for more information.
January 2021
We have added a new table, GIFT_CARD. We are gradually rolling out this new feature to all existing connections. If you'd like to enable the table on your connector, contact our support team.
We have fixed a bug where the first name and last name values returned by the Recurly API were sometimes not synced to your destination. Trigger a re-sync to ensure data integrity.
October 2020
We now mask the characters you enter in the API Key field of the connector setup form. We have changed the API Key field type from TextField to PasswordField to improve security.
June 2020
We have added three new fields to replace the following fields in the TRANSACTION table:
payment_gateway_idreplacespayment_gatewayidpayment_gateway_typereplacespayment_gatewaytypepayment_gateway_namereplacespayment_gatewayname
Update your queries with the new field names to sync data into these fields.
April 2020
We have added a new child table, COUPON_DISCOUNT, to the COUPON_HISTORY table. We have moved the following fields from the parent table to the child table:
discount_typediscount_percentagediscount_currency_typediscount_currency_amountdiscount_trial_unitdiscount_trial_length
January 2020
We have added three new history tables to replace the following tables:
COUPON_PLAN_HISTORYwill replaceCOUPON_PLAN.INVOICE_SUBSCRIPTION_HISTORYwill replaceINVOICE_SUBSCRIPTION.SUBSCRIPTION_COUPON_REDEMPTION_HISTORYwill replaceSUBSCRIPTION_COUPON_REDEMPTION.
We will update all six tables with for three months, then discontinue the replaced tables. Be sure to update your queries with the new history table names before we remove the old tables.
July 2019
We have changed the way we perform the initial sync for our Recurly connector. Previously during the initial sync, our Recurly connector scanned for records from EPOCH to the time when the initial sync started.
Now Fivetran scans in reverse and completes the initial sync in small batches. Every sync fetches records created in the past between two dates that differ by 7 days. This process continues until we reach the beginning of time.
May 2019
We have released a new version of the Recurly connector. The new version contains changed, added, and deprecated tables. In the existing tables we have added new columns and removed the deprecated ones. See the schema for details.
Added tables:
ACCOUNT_BALANCEACCOUNT_NOTEACCOUNT_ACQUISITIONBILLING_INFOCOUPON_PLANCREDIT_PAYMENTINVOICE_SUBSCRIPTIONLINE_ITEMPAYMENT_METHODPLAN_ADD_ON_CURRENCYPLAN_CURRENCYSUBSCRIPTION_CHANGESUBSCRIPTION_COUPON_REDEMPTIONTRANSACTION_SUBSCRIPTION
Deprecated tables
ADJUSTMENTCURRENCY
Connect to the new Recurly connector.
Read our Recurly connector documentation..
May 2018
We have added two new columns, start_date and end_date, to the ADJUSTMENT table.