Census Migration FAQ

Find answers to frequently asked questions about migrating from Census to Fivetran.

Pricing

Where can I find my legacy Census plan information?

If you were on a paid Annual Census plan when you linked your account, you'll continue to see usage information related to your plan in the Billing section of the Activations Organization Settings page.

Once your plan has ended and migrated to new consumption-based pricing, this report will no longer be accessible. Instead, you'll use Fivetran's Billing & Usage page located at the bottom of the left-hand navigation.

Where can I estimate my updated pricing?

You can estimate your Activations pricing using Fivetran's Pricing Estimator, like you can for Connections and Transformations.

How is Census priced moving forward?

Customers on a paid Annual Census plan will be able to continue using Census within Fivetran until the end of your current Census plan. You can see the end date of your specific plan during migration and in the Activations settings legacy billing page. Note that all month-to-month Census plans ended in March 2026.

Once your legacy Census plan ends, your account will move to Fivetran's usage-based pricing model, which tracks usage in Monthly Active Rows (MAR). Like Census, you can pay for Fivetran on an annual contract or a monthly pay-as-you-go model.
Here's what to expect based on your situation:

• I have a Census plan but I'm new to Fivetran: Your Census plan will continue to cover your use of Census features inside Fivetran until your contract ends. During this period, you'll need to select the Fivetran paid or free plan that you'll use after your Census plan expires. This plan will include both Fivetran features alongside your migrated Census features. If you do not choose a plan before your Census plan expires, your account may be frozen until you select a plan. You can change your Fivetran plan at any time.
• I have a Census plan and a Fivetran account and plan: You'll continue to pay for Census and Fivetran separately until your Census contract ends. Once your Census contract ends, your Census usage will simply begin applying to your Fivetran plan. You can change your pricing plan at any time.

What are Fivetran's different plan options?

Learn more about Fivetran's pricing plans and what they cost in our service consumption table.
The Fivetran plan depends on your existing Census plan and which features you are using. During the migration, if you're unsure or require more time to configure payment mechanisms, you can simply select the Fivetran Free plan to start. You can change your pricing plan at any time.

Which Census features are available in which Fivetran plan?

In most cases, each Census plan has an equivalent Fivetran plan which contains the same features.

There are a small set of exceptions:

• PrivateLink will only be available in Fivetran's Business Critical plan.
• The list of Enterprise connectors have changed to match Fivetran's.
• Access Controls will be available on all plans. (Custom roles will remain an Enterprise plan-only feature.)
• Activations in Powered by Fivetran (formerly Census Embedded) will be available on all plans.

What is MAR?

Monthly Active Rows (MAR) is the number of unique rows of data synced from your activation source to your activation destination in a month. For Activations, we determine unique rows by using the sync key or matching key specified in each activation sync. Each row is counted only once, even if it's updated multiple times in the same month. Learn more in our Monthly Active Rows documentation.

Will I save money if I move from a monthly to an annual contract?

Yes, you unlock discounts when you switch to an annual contract. We calculate your discount based on the total annual list price of your contract and the plan you choose. Learn more in our Discounts with annual contracts documentation.

What's happening with Census Embedded?

We now support Census Embedded use cases through Activations in Powered By Fivetran. Migrations for Census Embedded customers are the same as all other user accounts. Workspaces and access controls are not changed by the migration.

Migration

What is an activation?

In Fivetran, an activation is a set of activation syncs that define how data from various tables and datasets in a specific source are synced to the objects in a specific destination, such as Salesforce or Braze.

An activation sync is an individual sync that moves data from an activation source to an activation destination (distinct from Fivetran connector destinations). Previously, this was called a "sync" in Census. Multiple activation syncs can write to the same destination.

Why are these changes happening?

Census joined Fivetran, and we're integrating Activations into the broader Fivetran platform. The goal is a single, consistent experience: the same access controls, regions, networking, and operational model across all of Fivetran.

Will any features become unavailable?

A small number of features are being sunset because equivalent functionality exists elsewhere in Fivetran or is no longer aligned with our product direction. Learn more in the Features being sunset section below.

Workspaces

What's happening to workspaces?

Workspaces are being removed as a core organization concept. The majority of their functionality is being migrated onto individual activation sources. Some functionality is available in API-only for backward compatibility, and one capability specific to Census Embedded is being sunset. The Fivetran Activations product is evolving to focus on sources rather than workspaces, and new accounts will be created without workspaces at all.

Will my existing workspaces stop working?

No. Existing workspaces continue to function during the transition. While your UI will shift to a source-centric view, your workspaces still remain intact.

What happens if I have multiple sources in one workspace?

Initially, you won't see a change. Over time, these individual sources will receive their own access controls. You can then manage their settings directly on each source rather than at the workspace level.

Can I still create new workspaces with multiple sources via the API?

For now, yes. However, this feature will go away in a few months (exact date to be confirmed). Roughly 60 days after the deadline announcement, we'll prevent creation of more than one source within a workspace. About 30 days after that, any remaining multi-source workspaces will be automatically subdivided. It's a breaking change for the affected API configurations, so we recommend migrating ahead of the deadline.

To avoid IDs changing unexpectedly, we recommend that API users proactively request workspace migration when you are ready to handle the ID and API key changes.

Where do my workspace settings go?

Within the Activations UI, most settings will instead be configured on each activation source. The current workspace settings page will remain accessible from the Activations source list to make the association clear. Specific settings are as follows:

• Access Controls -> Moved to Fivetran's Users & Permissions page
• Regions, Datadog, Extended Alert Recipients → Moved to activation source settings
• Webhooks, Workspace API Keys → Accessible only via API

Activation sources

How are activation sources changing moving forward?

Activation sources will increasingly behave like Fivetran destinations. Changes include adopting Fivetran's naming constraints and becoming the primary unit of access control. In the future, you'll be able to use existing Fivetran destinations as activation sources directly, given the appropriate permissions.

Can I use a Fivetran destination as an activation source?

Not yet. We will announce this change once it is ready, so you can take advantage of Fivetran's private networking support without configuring a separate connection.

Activations (Source-Destination Pairs)

What is an activation?

An activation is the set of syncs between a single activation Source and a single destination. Your Activations are already visible in the Fivetran Billing & Usage dashboard. Each activation has a 14 day trial and MAR-based consumption pricing like all Fivetran connections. In the near future, these activations as well as trial status will be visible inside Fivetran Activations as well.

What changes for Activations in the UI moving forward?

Activations remain visible and manageable like connections are in the Fivetran UI today, including their own trial state and per-activation access controls.

Access Controls and Permissions

How are access controls changing?

Activations access controls are moving to Fivetran's existing access controls. You can manage access to activation sources using Fivetran's standard roles and teams, the same way you manage Fivetran destinations.

What new capabilities does this bring?

SCIM provisioning, teams management, and finer-grained permissions, including the ability to grant access at the activation destination level.

What happens during the transition?

For most users, your existing permissions will be moved automatically into Fivetran with no action required on your part.

If you define users and permissions via the API, we will give you a time window to migrate permissions yourself (exact date to be confirmed). During this period, permissions defined on sources and on the workspaces that contain them will both apply (additive). This overlap prevents interruption of existing API integrations and allows development against the new model. We recommend that you standardize on source-based access control as soon as you can.

How long will workspace-based access controls continue to work?

Workspace-based access controls and tokens will continue to be available in the API through the announced deprecation date (exact date to be confirmed).

I have Census custom roles. What happens to them?

For Enterprise customers using Census custom roles, our support team will work with you one-on-one to translate them into Fivetran custom roles that preserve your intended access.

Will Census Embedded customers still be able to support multi-tenant use cases?

Yes. Multi-tenant use cases are still supported via the source-based access control model, matching the approach used for Powered by Fivetran (PBF).

Regions, Cloud, and Networking

Which regions and clouds will be supported?

Activations is moving to Fivetran's clouds and regions. We're starting with high-priority regions on Fivetran's default GCP cloud, where most Fivetran destinations live today, and adding more over time.

Will I be able to choose my region?

It depends - geography, cloud, and region are configurable for certain Fivetran pricing plans.

Are Census's outbound IP addresses changing?

Yes. Activations is migrating from our legacy IP addresses to Fivetran's IP addresses listed in the following chart. If you currently use a legacy IP address, you must also grant access to the upcoming IP addresses in order to avoid disruption during migration.

All other regions use Fivetran's Standard IP addresses.

Are the AWS and GCP account IDs changing?

Yes. Activations is moving to Fivetran's AWS and GCP account IDs. Old GCP service account IDs will remain the same - only new GCP service account IDs will have a new format.

Any IAM configuration for AWS sources and destinations using the old Census account ID 341876425553 will need to be updated to include Fivetran's account ID 834469178297 as well in order to ensure a smooth transition. For example, the Principal section inside a AssumeRolePolicyDocument should be extended to include both account IDs:

...
"Principal": {
  "AWS": [
    "arn:aws:iam::341876425553:root",
    "arn:aws:iam::834469178297:root"
  ]
},...

API

What are the main changes for API users?

• If you haven't already, start using Activations PATs (separate from Fivetran PATs).
• Expect user and access management to move to Fivetran's APIs.
• Start working with single source workspaces. When you create new activation destinations, associate them with activation sources.

Which API endpoints are being deprecated?

Workspace, workspace token, and workspace permission endpoints are being deprecated. User and access control management is moving to Fivetran's APIs. We plan to eventually deprecate api.getcensus.com and the Activations V1 API (exact date to be confirmed).

Will Destination APIs change?

Yes. Destination APIs will use a Fivetran group ID instead of a workspace ID.

How long do I have to migrate?

The V1 API continues to work during the transition. We will confirm specific deprecation dates in the future. We are giving API users get the longest migration window to account for the impact of the changes.

Will workspace API keys be removed entirely?

No. Workspace API keys will remain part of the V1 API for backward compatibility. Admins can use their PAT to access workspace keys for access to legacy parts of the API. The API will be extended to support workspace API key rotation.

What about sync triggers in the UI?

Sync triggers in the UI currently use workspace API keys. As workspace API keys move to API-only, the UI's sync triggers will be updated to use PATs instead.

I use the Terraform provider. What do I need to do?

Other than planning to update to the latest version, you don't need to do anything. The Activations Terraform provider already uses the Activations PAT. We recommend Terraform for customers previously using workspace cloning, templates, or variables to manage multi-tenant configurations.

I use the Airflow or Prefect integrations. What do I need to do?

You'll need to upgrade to the latest version of the integration and switch to PATs.

Is the Census API being migrated as well?

APIs are not being integrated as part of this migration. API endpoints, SDKs, Terraform provider, and other orchestration tools continue to work as they always have. We plan to integrate our APIs in the future, so we'll communicate those changes and their timeline when they're finalized.

Features being sunset

Census Store / CSV Uploads / Mesh Datasets - Census Store is being sunset August 1, 2026. See details and timelines in the January 28 announcement in the Census changelog.

Workspace cloning, templates, and variables - These features were primarily used to support multi-tenancy for Census Embedded and Powered by Fivetran customers. We recommend moving to Terraform for managing these configurations going forward.