Clean phone numbers from Excel before a CRM import
Excel phone-number cleanup is preparing phone cells as text for a CRM import, keeping leading zeros and reviewing formulas before export.
Excel can turn phone values into numbers, remove leading zeros or interpret a value beginning with + as a formula. E164Flow reads the workbook locally, keeps the original columns and adds explicit validation details to the export.
How do I start this workflow?
Keep the source file, confirm the phone and country fields, and review the results before choosing the import layout.
- Save the source phone column as text where possible.
- Select the worksheet, header row and phone/country columns in E164Flow.
- Export an XLSX file for exact text, or a safe CSV for systems that require CSV.
Which spreadsheet cells need different handling?
Compare the stored value and its source type before deciding whether a cell can be formatted. A display that resembles a phone number is not enough to prove that its digits were preserved.
| Example source | What to check | Safe next step |
|---|---|---|
| Text: 041 123 456 | Country is SI | Convert to +38641123456 |
| Number with a missing initial zero | Original export or source system | Recover the original value; do not guess digits |
| Text: 4.42079460018E+11 | Scientific notation | Use an exact-text source value |
| Formula cell | The cell's formula and source | Review the original data before conversion |
A custom display format and an exact stored text value are different things. If the original workbook still contains the required formatting information, the import preview is where you check the extracted value. If the information has already been removed from the source, changing a cell's category afterward cannot establish what was originally intended.
How should I prepare phone columns before entering data in Excel?
Treat phone numbers and record IDs as text before entering or importing them. They are identifiers, so spreadsheet arithmetic is usually the wrong default for those fields.
Microsoft documents that Excel can remove leading zeros and display large numbers in scientific notation. Check the values themselves rather than assuming that a wider column or a different display format has preserved the original input. Keep a separate copy of the export you received before editing the workbook.
For a recurring import, agree on which columns contain phones, countries and source IDs. That small convention makes the next review easier, but it does not remove the need to inspect the new file. Country names and phone prefixes may still be inconsistent even when the workbook layout is unchanged.
What should I check in the worksheet and header preview?
Select the intended worksheet, header row, phone fields and country field before confirming the import. The preview should contain the records you expect, not a report title or a summary sheet.
An exported workbook may start with several report lines before its actual table. Choose the row containing field names so those report lines are not interpreted as contacts. Where CSV is the input, select the matching separator and encoding if the automatic interpretation does not show the expected columns.
E164flow samples rows to suggest the mapping. A suggestion is not a complete validation of the workbook, and a numeric ID can look phone-like. Inspect both the column name and several values. If a saved profile names a field that is missing from this file, update the mapping instead of silently substituting another column.
Can the tool restore a zero that Excel already removed?
It cannot reliably reconstruct missing digits. Use the original source or correct the record from information you can verify, rather than adding zeros to every value with a short length.
Phone-number rules differ between countries. A zero may be part of a national presentation, a meaningful part of the number, or evidence that a spreadsheet conversion has changed the source. A blanket rule such as add a zero until the cell has nine characters can turn one error into a plausible but incorrect number.
Scientific notation and formula inputs also need source review. If the source value has been rounded or replaced, converting its visible representation into a long digit string does not recover the missing information. Use the row reference to locate the original record and supply an exact value, then recheck the list.
How do I handle several phone columns and mixed countries?
Select each phone field that needs checking and map the country column for mixed-country rows. Use a default country only where that context is appropriate for national numbers.
Phone, Mobile and Work phone can stay on the same contact row. E164flow checks up to 10 selected phone columns and gives each result a row and column reference. Your record ID and original fields remain available beside the generated fields, so the review does not require rebuilding the contact list by hand.
An explicit international prefix takes priority over a default. For instance, a source value beginning with +44 is not reassigned to Slovenia because a default of SI was chosen. Review any mismatch warning. Keep extensions separate and check whether a duplicate refers to another field on this contact or a different source row.
Should I export an Excel file or a CSV file?
Choose XLSX when exact text cells and spreadsheet review are the priority. Choose CSV when the destination requires it, using the export mode that matches how the file will be consumed.
The XLSX export writes phone values as text. Spreadsheet-safe CSV protects values that a spreadsheet might interpret as formulas, which can add an apostrophe to a value beginning with +. CRM CSV preserves the plus sign in generated canonical phone fields, while original fields and headers remain escaped.
Do not use a normal Excel open-and-save cycle to inspect an exact CRM CSV and then assume it is unchanged. Review the converter's file preview, or use an XLSX report for the human check. If you must inspect the CSV itself, compare the text values and the destination's import preview before submitting the file.
How do I keep the cleanup traceable when I run it again?
Keep the original source, a review report and the final import file as separate stages. Use a stable record ID to connect a corrected phone value back to the right contact.
A reviewed value does not replace the original source field in the converter. The result can retain the original input, the generated format and review information. Resolve an error against the source rather than editing only a downloaded file whose relationship to the original row is no longer clear.
Save a local profile for repeated settings, not as a contact archive. It stores mapping and output choices on the device, without the rows themselves. Free accounts support files up to 50 rows and Pro up to 20,000 rows per file. A guest can check 25 pasted numbers before using the upload and export workflow.
Which primary sources support this workflow?
Use the underlying standard or the destination's own documentation when checking a numbering rule or an import requirement.
What should I check before the final import?
Compare a small sample with the source and the destination, then use this checklist to review the complete file.
- Do not re-open and resave an exact CRM CSV in Excel before importing it.
- Reject scientific notation instead of guessing missing digits.
- Use the original source row reference to correct a value in the source workbook.
Start with the data you have.
Use 25 pasted rows without an account, or sign up for the 50-row free workflow with CSV/XLSX and export.