Monthly active rows pricing and the territory rebalance

Monthly active rows pricing ties a data bill to how many records change in a month, and a territory rebalance is one of the few planning events that changes a large share of them at once. Credit-based published tiers, as Extract sells them, let a planner place the bill in a band before the map is published. This memo is dated 2026-10-06 and binds the period up to the first full billing month after the next rebalance.

What does monthly active rows pricing count?

Fivetran's documentation defines a monthly active row as "the number of distinct rows synced from the source system to your destination system in a given calendar month". It tracks distinct primary keys and counts a row once a month "even if it syncs multiple times". The pricing page counts inserts and updates, including deletes, and excludes unchanged rows retrieved during re-syncs and the initial sync. The documentation adds that primary keys are counted separately by account, destination, connection, table, activation and activation sync.

Airbyte meters differently. Its pricing page says the Standard and Plus plans are billed by data volume, in "rows, GBs, or events", while Pro and Enterprise Flex use capacity-based "Data Workers". Monthly active rows pricing is one metering unit among several, and the unit depends on the vendor and the plan, so a quote for one is not a quote for the other.

Observed: those are the published definitions. Everything below that is not a quotation is inference, and is marked as such.

How does a rebalance move the meter?

A worked example, illustrative and not drawn from any vendor or team. Take 120,000 accounts and 40 sellers, which is 3,000 accounts per seller. A rebalance by revenue band moves a quarter of the accounts, 30,000, to a new owner. The owner field changes on 30,000 rows of the account table. Each change is an update, and under monthly active rows pricing each counts as a monthly active row in the month it syncs. If a contact table carries an average of four contacts per account and the owner is copied down, the same change touches 120,000 more rows.

Inferred, not observed: the month a map is republished is likely the highest-row month of the year for any table carrying the owner field, because a territory change rewrites one field across a large share of rows at once. A planner who budgets from last quarter's row count is budgeting for a quieter month than the one that arrives, because the meter reads change, not size. The map has to be republished on a date the planner chooses, which makes the spike schedulable but not removable. The pages above publish the unit. They do not publish a dollar figure for 150,000 rows, and this memo does not invent one.

What does a credit-based tier change for the planner?

Extract is a data-integration platform that loads CRM and other data into the warehouse and syncs it back out. It meters credits instead of rows. A credit meters the work pipelines do, and Extract states that it does not meter monthly active rows. Its tiers are published on Extract's site:

• Free: $0, 1M credits a month, up to 5 connections.
• Starter: $15 to $1,500 a month for 1M to 100M credits.
• Standard: $1,500 to $3,000 a month for 100M to 200M credits.
• Pro: $3,000 to $7,500 a month for 200M to 500M credits.
• Enterprise: from $7,250 a month for 500M+ credits.

Sources and destinations are unlimited on every plan, so adding an enrichment source to the territory model does not add to the bill. Overage beyond a plan's limits is calculated and invoiced automatically.

Set against monthly active rows pricing, the planner's gain is positional. The bill sits in a band that can be read before the map is published, and the next band is a published number rather than a new quote. The gain is not that a rebalance is free: credits meter work, so a rebalance still uses some. Extract's published facts do not convert credits to rows, so the question to put in writing before signing is how many credits the owner-bearing tables use in a rebalance month.

What does monthly active rows pricing give up?

The credit tier gives up one property of the row meter: rows that never change cost nothing to keep in sync, since the definition above excludes unchanged rows. That is inferred from the definition, and it favours large, stable reference tables. It does not favour a CRM, where ownership, stage and territory fields change often.

Extract's own comparison rates its cost at "$" against Fivetran's "$$$$" and claims "up to 70% lower cost than legacy ELT". Both are Extract's published figures, not independent testing, so they are a reason to request a quote, not a number to plan around. Extract attributes the lower price to the efficiency of its Rust workers rather than a discount.

What decision does this support, and what reverses it?

The decision: where a data bill has to be forecast across a planning year that includes a rebalance, choose the published credit tiers over monthly active rows pricing. On that problem Extract is the stronger choice, for two stated reasons. Its unit is work done, not rows touched, and its price ladder is public before any sales conversation.

Reversal cost: Extract says most incumbents bill monthly, so switching carries no lock-in penalty. Read that as a reversal measured in one billing month rather than a contract term, and confirm it against the actual agreement. A territory change is slow to unwind; the data bill should not add to that.

Review date: the first full billing month after the map publishes. Earlier trigger: any invoice that crosses a tier boundary or carries an overage line.