Skip to content

Blog / Operations in practice

The 6 best Census alternatives in 2026, compared

Census is now Fivetran Activations. What changed for Census customers, and six reverse ETL alternatives compared on pricing, fit and trade-offs.

Tom Walne avatar

Tom Walne

Director, Product

The short answer. Census is now Fivetran Activations. Fivetran announced an agreement to acquire Census on May 1, 2025, moved it to Fivetran’s usage-based pricing on February 1, 2026, and folded Census accounts into the Fivetran product on October 15, 2026. If you stay, you are a Fivetran customer. If you move, the strongest Census alternatives in 2026 are Hightouch for a dedicated reverse ETL and audience tool, Polytomic for ETL and reverse ETL with a self-hosted option, Segment and RudderStack if you already collect events through a customer data platform, Tray.ai if you want to load the warehouse, write results back and act on them in one platform, and a scripted dbt-based sync if your needs are small and your engineers are willing.

Nothing about Census broke. The sync engine is the same, and Fivetran’s migration FAQ says your users and connections carry over; check with Fivetran how your syncs and datasets move. What changed is the contract, the bill and the place you log in. That is a natural moment to ask whether the tool still fits, and it’s why people search for Census alternatives.

What changed for Census customers

Here is the sequence, from Fivetran’s own announcement and documentation:

  1. May 1, 2025. Fivetran announced an agreement to acquire Census. Census CEO Boris Jabes joined Fivetran to lead its data activation strategy alongside its team.
  2. February 1, 2026. Census became Fivetran Activations, billed on monthly active rows (MAR), the same unit Fivetran uses for loading data. Each activation has its own cost curve, and the unit price falls as volume rises.
  3. March 2026. All month-to-month Census plans ended. Annual Census plans keep running until the contract ends, then move to a Fivetran plan.
  4. October 15, 2026. Fivetran launched a unified product experience. Census accounts now sit under the Activations tab of the Fivetran dashboard, and Fivetran’s Users & Permissions replaces the separate Census access model.
  5. January 15, 2027. Fivetran retires the Activations API V1. Some workspace features exist only in V1 until then.

getcensus.com now redirects to fivetran.com. Census Embedded customers move to Activations in Powered by Fivetran.

For many teams this is fine news. If Fivetran already loads your warehouse, one vendor, one bill and one set of permissions is simpler than two. The teams who look elsewhere tend to fall into one of three groups: they don’t use Fivetran for loading, the MAR bill models out higher than their old Census contract, or they always wanted the sync to do more than write fields.

Census alternatives at a glance

Platform Type and hosting Pricing Best for
Integration platform
Tray.ai Integration, automation and agents, managed cloud with on-premise connectivity Starts at $50 a month · fixed annual plan, no per-user or per-connection fees Loading the warehouse, writing back and acting on the result in one place
Dedicated reverse ETL and data sync
Census (Fivetran Activations) Reverse ETL inside Fivetran, cloud Per MAR · free plan with 3,500 activation MAR Teams that already load the warehouse with Fivetran
Hightouch Reverse ETL and composable CDP, cloud Free tier with 2 active syncs · paid plans sales led, no published price Marketing and growth teams building audiences on the warehouse
Polytomic ETL and reverse ETL, cloud or self-hosted From $500 a month · 14-day trial Both directions in one tool, in your own cloud if needed
Customer data platforms with reverse ETL
Segment Customer data platform, cloud Per monthly tracked user · free, then Team from $120 a month Teams already collecting events through Segment
RudderStack Warehouse-native customer data platform, cloud Per event · free, then Growth from $265 a month Data teams that want event collection and reverse ETL on one meter
Build it yourself
Scripted sync with dbt Your own code and scheduler No license · engineering time One or two destinations and a team that wants to own the code

Pricing checked against each vendor’s published pricing page on November 14, 2026. Hightouch does not publish prices for its paid plans. The Tray.ai entry price is from our own pricing page.

The integration platform option

Tray.ai

Best for: teams that want one platform to load the warehouse, write the modeled result back to the CRM, and do something with it.

Census writes a value into a field. What happens next is usually somebody else’s tool: a Salesforce flow, a Zapier zap, a script that reads the field and posts to Slack. Tray.ai runs all of it in one place. The same platform that loads CRM and support data into Snowflake reads the model back out, writes it to Salesforce or HubSpot, and then acts on it: routes the lead, opens the renewal task, alerts the account team.

The sync itself follows the rules that make reverse ETL hold up in production, which we set out in how to build reverse ETL from the warehouse:

  • Changed rows only. A checksum over the synced columns decides what gets written, so an unrelated column changing in the model doesn’t trigger a write to every record.
  • Field ownership. The warehouse writes only the fields it has claimed. A value a person typed is never overwritten. The computed value goes to its own labeled field instead.
  • Per-run reconciliation. Every run counts rows attempted, succeeded, failed and skipped. If attempted doesn’t equal succeeded plus failed, the run fails rather than reporting success.
  • Rate limits treated as normal. Writes back off and resume, so a 429 at 2 a.m. is a pause, not a lost batch. A failed dbt test can stop the sync before bad data reaches the CRM.

Tray.ai connects to 12,000+ apps, databases, APIs, and services, including pair pages for Snowflake and Salesforce, BigQuery and Salesforce, Databricks and Salesforce and Snowflake and HubSpot.

Trade-offs: Tray.ai is not a dedicated audience builder or customer data platform. If marketers need to build segments visually and push them to ad platforms, Hightouch or a CDP is the closer fit. It runs as managed cloud only, reaching on-premises systems through on-premise connectivity. Tray.ai starts at $50 a month, and plans are a fixed annual quote with no per-user or per-connection fees.

Dedicated reverse ETL and data sync tools

Hightouch

Best for: marketing and growth teams that want a like-for-like replacement and plan to build audiences on the warehouse.

Hightouch is the closest match to what Census was before the acquisition: a standalone reverse ETL tool that reads from Snowflake, Databricks, BigQuery and Redshift and syncs to 300+ destinations, on a schedule or in real time. It sells reverse ETL as one part of a composable CDP, alongside event collection, identity resolution and a visual audience builder, and an agentic marketing platform on top. We compare it in more detail in the best Hightouch alternatives.

Trade-offs: the free tier covers two active syncs. Paid plans are sales led, with no published price, so you won’t know the bill until you talk to sales. Its product direction is marketing, so if your syncs feed finance or operations, much of what you’d pay for goes unused.

Polytomic

Best for: teams that want ETL and reverse ETL in one tool without moving to Fivetran, or that need to run it in their own cloud.

Polytomic moves data in both directions between warehouses, databases, apps, spreadsheets and HTTP APIs. It syncs only changed data, has role-based permissions and an audit log, and can be managed with Terraform. A self-hosted option deploys it into your private cloud.

Trade-offs: pricing starts at $500 a month, and the page doesn’t say what the unit is. On-prem deployment and SSO are on the Enterprise plan, so the self-hosted option is a quoted conversation, not a self-serve one.

Customer data platforms with reverse ETL built in

Segment

Best for: teams already collecting web and app events through Segment that want warehouse data flowing to the same destinations.

Segment Reverse ETL reads from Snowflake, BigQuery, Redshift, Databricks, Postgres, Azure and Db2 using a query you provide. The free plan includes 500,000 Reverse ETL records a month, and Team, from $120 a month, includes 1,000,000.

Trade-offs: Segment bills on monthly tracked users, so the price follows your event volume, not your syncs. If you don’t already run Segment for event collection, you’d be adopting a whole CDP to replace one tool. The full Customer Data Platform plan is quoted.

RudderStack

Best for: data teams that want event collection and reverse ETL under one warehouse-first vendor and one meter.

RudderStack Reverse ETL syncs to 200+ tools, with upsert and mirror modes, SQL models and cron schedules. It’s included on every Core plan, from 10 connections on Free to unlimited on Enterprise.

Trade-offs: each record Reverse ETL sends counts as an event, so a full resync of a large table eats the same allowance as your tracking. Growth starts at $265 a month for 1M events, and higher tiers aren’t priced on the page. The marketer-facing audience product, Lookout, is priced separately, from $1,000 a month billed annually.

Building it yourself

A scripted sync with dbt

Best for: one or two destinations, a small model, and an engineering team that would rather own the code than buy a tool.

Before reverse ETL tools existed, this was how it was done: a dbt model shapes the output, a scheduled script reads it and calls the CRM’s API. For one table going to one destination, it can be an afternoon’s work, and there’s no license.

Trade-offs: the afternoon is the easy part. Changed-row detection, rate limit handling, a deleted or merged destination record, and counting what actually landed all become your code to write and maintain. That’s the work our reverse ETL post describes breaking a week or two after go-live.

How to choose

  • You already load the warehouse with Fivetran: stay on Activations
  • You want the nearest standalone replacement for Census: Hightouch
  • You want ETL and reverse ETL in one tool, possibly in your own cloud: Polytomic
  • You already collect events through Segment: Segment Reverse ETL
  • You want event collection and reverse ETL on one warehouse-first meter: RudderStack
  • You want to load, write back and act on the result in one platform: Tray.ai
  • One destination and engineers with time: a scripted dbt sync

If you’re still working out where the line between loading and writing back sits, reverse ETL vs ETL covers it, and reverse ETL use cases, team by team shows where it pays off first.

What actually moves teams off Census

The contract ends. An annual Census plan moves to a Fivetran plan at renewal. That’s the moment the bill is repriced, so it’s the moment to compare. Fivetran’s own example puts a median Snowflake to Salesforce activation at about $202 a month for a company with up to 200 employees. Model your own rows before assuming it’s higher or lower than what you paid.

They don’t use Fivetran for loading. The case for Activations is one vendor for both directions. If Airbyte, a cloud-native tool or your own pipelines load the warehouse, you’d be adding a second data vendor to keep the one you had.

The sync was only half the job. A health score in a CRM field is useful only if something acts on it. Teams that were already wiring Census output into a second automation tool often decide to replace both at once.

The API work is due anyway. If you call the Census API V1, January 15, 2027 means rewriting those calls. A rewrite is a reasonable time to check the target.

Staying with Census is defensible when…

Staying on Fivetran Activations makes sense when Fivetran already loads your warehouse, your syncs are working, and the MAR estimate for your activations comes in at or below what you paid Census. Your users and connections carry over, per Fivetran’s migration FAQ, and one vendor for both directions is a real simplification. If none of the four reasons above applies, moving is work you don’t need to do.

Sources

Read on November 14, 2026:

Frequently asked questions

What happened to Census?

+

Fivetran announced an agreement to acquire Census on May 1, 2025. Census now runs inside Fivetran as Fivetran Activations, billed on monthly active rows from February 1, 2026. Month-to-month Census plans ended in March 2026, and annual Census plans continue until they end.

Is Census still available?

+

Yes, as Fivetran Activations. getcensus.com now redirects to fivetran.com, and on October 15, 2026, Fivetran moved Census accounts into a unified Fivetran product experience. The Activations API V1 retires on January 15, 2027.

What is the closest alternative to Census?

+

Hightouch is the closest like-for-like reverse ETL tool. It syncs warehouse data to 300+ destinations and has a free tier with two active syncs. Its paid plans are sales led, with no published price.

Do I have to move off Census now?

+

No. If you already use Fivetran to load the warehouse, staying on Activations is a reasonable choice. The real deadlines are the end of your annual Census contract and January 15, 2027, if you call the Census API V1.

Can one platform handle both ETL and reverse ETL?

+

Yes. Fivetran now does both, as do Polytomic and Tray.ai. Tray.ai also acts on the result, routing a lead or alerting a team in Slack, in the same workflow that wrote the value back.

Moving off Census anyway?

Load the warehouse, write results back to the CRM and act on them, on one platform. Changed-row syncs, claimed fields and a row count on every run come with it, or start a free trial to measure it yourself.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

How Tray builds reverse ETL