Coming Soon
Since Census joined Fivetran, we've been hard at work to make reverse ETL feel like a native part of the Fivetran platform. The first step in that process launched February 1st of this year. We’ve now entered the second phase, which includes some upcoming changes to the product experience, as well as to our API.
Adopting the Fivetran model
This next phase of integration is focused on making activations “work like the rest of Fivetran”. Our goal is to make Activations work as seamlessly as Fivetran’s other features.
To that end, we are beginning the transition of making Activation Sources work similarly to Fivetran Destinations. The end goal is to enable you to set up a Destination once and use it across Connectors and Activations (including advanced networking configuration). Until then, they will remain separate within the UI.
Activations will move into Fivetran's clouds and regions. We'll roll out additional regions over time, beginning with our highest-priority regions on Fivetran's default GCP cloud. Geography, cloud, and region will be configurable according to your Fivetran plan. Our aim is to make Activations available in every Fivetran-supported public (non Government) Cloud and Region.
Activations will adopt Fivetran’s existing access controls, which brings SCIM, team management, and finer-grained permissions. Enterprise customers using Census custom roles will be supported one-on-one in translating those to Fivetran custom roles that preserve your intended access.
Activation syncs will be grouped into individual activations in the UI and API, with their own trial state and access controls, exactly like connections in Fivetran today.
What's changing for Census customers
Workspaces are going away. Most current workspace-level settings such as access controls will be moved to individual sources. Activations in Powered By Fivetran use cases still support the multi-tenant deployments that Census Embedded customers require.
Customers with heavy API usage across multiple workspaces will have a migration path, including access to both old and new approaches in parallel and a generous transition window to make code changes.
Networking is changing. Census will begin reaching out from Fivetran's IP addresses and AWS/GCP account IDs. If you maintain static IP allow lists, you'll need to update them. We'll share specifics well in advance.
What to do now
For the majority of customers, no action is needed. The changes we describe will begin showing up in your Fivetran Activations UI. We're sharing this early to provide context for the upcoming UI changes.
For API users, put some time for API migration on your roadmap in the coming months. New API endpoints will begin rolling out over the coming weeks and we expect the old API endpoints to be deprecated in Q3 2026. Exact deprecation dates and migration guides will follow in the coming weeks so you’ll know what those changes look like ahead of the deadlines, and we'll notify affected accounts directly.
For specific questions, keep an eye on our public FAQ which will be updated with our migration plans, in addition to the existing details around pricing model.
