Migrating from another platform? Import records first, run identity resolution, then bulk-enrich in batches with the migration profile — cache-aware, deduped, and cost-estimated before you commit.
Order of operations
Import → dedupe/identity resolution → bulk enrich. Enriching before deduping pays twice for duplicate records; always resolve identities first.
The migration profile
Data → Enrichment → Bulk → Migration profile. It fills only empty fields (never overwrites your imported values), uses the full cascade, and processes in rate-limit-friendly batches.
Cost estimate before commit
The bulk job shows an estimate: matchable records, expected fills per field, and projected cost by provider. Review before running — a 500K-record migration is a real invoice.
Verify after
Post-run, check the fill-rate report against the pre-migration baseline and spot-check 50 records manually. Common issue: title/industry taxonomy mismatches from the legacy system — fix with a mapping rule, not manual edits.
