Check your import counts

An import is not finished when it says complete. It is finished when the numbers on both sides agree, or when every difference between them has a reason you accepted.

What this does

Compares what was in your export against what is in the platform, per record type, and lists what happened to the difference.

How to do it

1. Open Onboarding, then Import, then the run you want to check.
2. Read the reconciliation table. Each row is a record type with three figures: rows in your file, rows in the platform, and rows accounted for elsewhere.
3. Open each non-zero entry in the third column. Every one names a reason: merged as a duplicate, rejected on a missing required field, or held for review.

What proves it worked

The first two columns agree once the third is added back. Nothing in the third column is unexplained.

That is the whole check and it is deliberately arithmetic rather than a status. A progress bar that reached the end tells you the job ran. It does not tell you what arrived, and the gap between those two is where a migration quietly loses a decade of contacts.

When the numbers do not agree

Duplicates are the usual reason and they are usually correct. Two contact records with the same email address and the same mobile number are one person, and the merge screen shows both originals so you can disagree.

Rejections are the ones to read closely. A rejected row is not lost; it sits in the review queue with the field that failed named. Fix the field in the queue or fix it in the source and re-run the import for that record type alone.

What we will not do

We will not silently drop a row. If a record cannot be imported it appears in the review queue, and the reconciliation does not balance until you have dealt with it. A migration that balances by ignoring what it could not read is a migration that will surprise you in six months.