ChurnZero sync error external ID not found for account: usage data not matched to CRM accounts

TL;DR

The usage data is fine, the join key is not. ChurnZero matches incoming usage to accounts by external ID, and when that ID does not match the CRM account it expects, the sync rejects the rows instead of guessing. Find which ID each side is sending, repair the mapping for the mismatched accounts, usually merged, migrated, or re-keyed accounts, and replay the rejected usage so health and segment data reflect the usage that was there all along.

ChurnZero sync error external ID not found for account: usage data not matched to CRM accounts

Use this when

• ChurnZero sync logs show external ID not found errors for a set of accounts
• Those accounts exist in the CRM and in the product, under visibly similar records
• The errors started after a CRM migration, dedupe project, or product account re-keying

Not for this skill when

• The accounts were deleted from the CRM intentionally and their usage should be discarded
• No usage is arriving at all, which is an upstream sending problem, not a matching problem

Steps

1. Export the sync errors from ChurnZero with the exact external ID values it rejected, and keep the full list rather than sampling from the top, because the pattern across all rejected IDs is what reveals whether this is a prefix change, a Salesforce fifteen to eighteen character ID issue, or a set of individual merged accounts. Verify: the complete rejected ID list is exported with counts per account
2. Look up a sample of rejected IDs in the CRM and in the product database. In Salesforce, check both the record ID and any custom external ID field the integration was built on, and check whether the account was merged, which retires one ID and keeps another, or migrated from a legacy CRM whose IDs were carried in a separate field the sync no longer reads. Verify: each sampled account is classified by mismatch type with the correct ID identified
3. Compare the ID the product sends in the usage feed against the ID ChurnZero holds for the account. Decide the single authoritative key going forward, normally the CRM record ID or a stable product account ID mapped in one place, and document it, because syncs break repeatedly when two teams each believe a different field is the key. Verify: the authoritative key and its owner are written down and agreed
4. Fix the mapping using the right mechanism for the pattern, a bulk update of external IDs in ChurnZero, a correction in the feed so it sends the authoritative ID, or a crosswalk table the sync consults for legacy accounts. Avoid renaming IDs inside historical usage rows by hand, which corrupts the audit trail. Verify: the mapping fix is applied and a test usage batch for sampled accounts syncs with no rejections
5. Replay the rejected usage for the full error window from the original feed files or by retriggering the integration, and confirm the accounts usage curves in ChurnZero now cover the gap days so segments and health inputs that depend on usage recalculate correctly. Verify: replayed usage appears for the gap window and affected segments refresh
6. Add a sync error budget and alert. Route daily external ID rejection counts to the integrations owner with a threshold, and add new account creation checks so every new CRM account gets its external ID populated and verified in ChurnZero within a day of creation. Verify: the alert exists and a test account creation passes the verification check

Why it happens

ChurnZero refuses to guess account identity, which is correct behaviour for customer data. Matching depends on one shared key surviving unchanged across the CRM, the product, and the feed. Merges retire IDs, migrations introduce second keys, and Salesforce ID formats change shape between systems, so a feed that matched perfectly last quarter rejects a growing slice after any identity project, while both systems individually look healthy.

Compatibility: ChurnZero integrations and account matching, Salesforce account IDs and external ID fields, and product usage feeds, in current versions.

Variants and edge cases

ChurnZero external ID not found sync error

['The verbatim phrasing. The rejected ID values themselves are the evidence, so export them in full before changing any mapping.']

usage data not matched to CRM accounts ChurnZero

['The business phrasing. Count how much usage is unmatched before fixing, because leadership needs the size of the blind spot, not only its cause.']

Salesforce account ID mismatch ChurnZero after merge

['The merge variant. Salesforce ID case and length conversions are a frequent culprit, so compare the exact strings character by character, not by eye.']

Edge cases to work through before you close the incident:

• Salesforce fifteen character IDs are case sensitive in a way the eighteen character form is not. A system that lowercases IDs will break matches silently for some accounts only.
• Parent and subsidiary structures tempt teams to send parent IDs for child usage. Decide the level usage belongs to and keep it consistent, or health data splits across the hierarchy.
• Keep the rejected rows. They are the only record of what usage was lost during the gap, and deleting sync error logs destroys your backfill source.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_xLB2dioTvXj1IdacDJBjQg