Reconcile a Kit import with a batch tag and a change log
Count the rows you intended to import, then inspect the tagged batch and sample records after Kit reports completion.
An upload confirmation alone does not establish that fields, tags and automation membership match your plan.
Work through the setup
- Write expected totals. Record source rows, excluded contacts and the intended import count. Note duplicate email addresses separately, because a row count need not equal a unique subscriber count.
- Use a batch identifier. Name the import tag with an understandable date and purpose. Kit supports organizing an import with a tag; review trigger rules before adding it.
- Wait for completion. Kit notes that imports can take time and sends a completion email. Check the bulk-action progress rather than repeatedly importing the same file while the first run is still processing.
- Audit representative records. Check a new contact, an existing contact with changed fields, and a record with optional fields left untouched. Compare tags and sequence activity, then save the reconciliation note with the export.
A worked example
Example audit sheet: expected 120 unique permitted contacts; 20 are already in the destination; first-name updates apply to 35. Your checks should include an existing named contact whose source name was blank. If that name disappears, stop before importing the full file and correct the mapping strategy.
What to watch out for
- A missing record while an import is still running is not proof of failure.
- Re-importing can update data again and may activate workflows.
- A batch tag is useful organization, not an automatic rollback button.
Record differences explicitly
Create columns for source count, imported count, already-present addresses and records needing review. Note the import batch and the date beside each result. If the totals differ, investigate exclusions, duplicate addresses and status rules before uploading the same file again. Preserve one known record from each group as a spot-check reference. A reconciliation log explains a migration; it should not be used to turn unsubscribed or uncertain records into active subscribers merely to make the totals match.
Sources and evidence
- How to import a subscriber list | Kit Help Center (read November 7, 2026)
- Importing subscribers into Kit: what to know + FAQs | Kit Help Center (read November 7, 2026)
Common checks
Can I undo a batch by deleting its tag?
Do not assume so. Removing a label does not restore overwritten field values or undo emails already sent. Keep a real pre-import export.
Published November 7, 2026. Sources last read November 7, 2026. Send a correction.