Phone Import QA Checklist for CSV Files
This page is for the final review before import. It is not about running the tool step by step. It is about checking whether the phone column is actually safe to import once cleanup is finished.
Quick answer
Review the phone field itself, the country context behind each row, and the rows that were held back for review. A smaller clean import is usually safer than a larger batch that still contains ambiguous phone data.
What This Checklist Is For
A phone import can fail even after basic cleanup if the final CSV still contains rows that are structurally risky, context-poor, or mixed with extra text. This checklist is meant to catch those problems before the file reaches your CRM, dialer, or API import screen.
The goal is not to force every row through. The goal is to verify which rows are ready now and which rows should stay out of the import batch until reviewed.
Phone Field QA Checklist
- Each row has only one phone number in the phone field.
- The phone field does not contain labels, comments, or call instructions.
- The value still looks like a phone number after formatting is removed.
- Extensions are not mixed into the main phone field unless your destination system explicitly supports that format.
- The cleaned phone value means the same thing as the original source row.
Country Context Checklist
- Rows that start with
+already carry international context. - Local-format rows have enough country context to interpret them safely.
- A default country is only filling a small gap, not guessing the meaning of most of the file.
- Mixed-country rows are not being forced through one country assumption.
- If the file came from more than one market, the country logic still makes sense row by row.
Needs-Review Checklist
- Rows with missing country context are kept out of the import-ready batch.
- Rows with multiple numbers in one cell are still separated.
- Rows with extension text are not being treated as clean import-ready numbers.
- Rows with note text in the phone field are still flagged for review.
- Rows that are unclear are not being promoted into the final import file just to increase row count.
Safe to Import Now vs Hold for Review
Usually safe to import now
- One clear phone number in the field
- Reliable country context
- No extension or note text mixed in
- No unresolved ambiguity about what the number means
Hold for review
- Missing or weak country context
- Multiple numbers in one cell
- Extension text inside the field
- Free-text notes or labels mixed into the number
Before You Import the Cleaned File
- Spot-check a few clean rows against the original source file.
- Confirm that the import-ready file contains only the rows you trust.
- Keep the needs-review file separate from the main import batch.
- Do a final pass on rows from mixed-country or multi-source datasets.
- Make sure you are importing the cleaned file, not the raw export.
If the destination is platform-specific, do one last prep check against the HubSpot phone import guide or Salesforce phone import guide.
Important Caution
A final QA pass is not about squeezing every row into a passing format. It is about protecting the quality of the imported data. When a row is unclear, review first is safer than guess first.
More resources
Browse the Resources hub, review clean phone numbers for CRM import, or learn why some phone rows need review before import.
Ready to review a real CSV before import? Open the Bulk Phone Normalizer and keep risky rows out of the final batch.
Open Bulk Phone Normalizer