Prepare phone numbers for a HubSpot import
Create a predictable E.164 phone column, keep source identifiers and review invalid rows before importing into HubSpot.
A CRM import is easier to troubleshoot when the source record, cleaned number, validation status and duplicate reference are visible in the same file. E164Flow prepares that staging file locally; it does not connect to or write to HubSpot.
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.
- Export a contact view from HubSpot with its record ID and phone fields.
- Map the relevant phone and country columns in E164Flow.
- Export a reviewed file, then import the E.164 column using HubSpot’s normal import flow.
Which fields should I keep in a HubSpot staging file?
Keep the existing contact identifier next to the source phone fields and cleaned output. The demonstration below keeps one row per contact and shows an extension separately.
| Record ID | Source phone | Country | Generated phone | Extension |
|---|---|---|---|---|
| 101 | 020 7946 0018 | GB | +442079460018 | |
| 102 | 041 123 456 | SI | +38641123456 | |
| 103 | +44 20 7946 0018 ext. 007 | GB | +442079460018 | 007 |
These IDs are illustrative. Export the actual identifiers from your own HubSpot records; do not invent replacements for an update. The generated phone column is ready for mapping only after the row's warnings and its relationship to the source contact have been reviewed.
How do I update existing contacts without losing their identity?
Include a HubSpot-supported unique identifier and preserve it through the cleanup. A formatted phone value is an output field, not a substitute for the contact's existing record identity.
HubSpot's import documentation requires a unique identifier when updating records, with choices depending on the object and import. A Record ID from the source export is useful for keeping a phone correction connected to a particular existing contact. Keep that field beside the phone columns while reviewing the file.
Separate an update of existing records from creating new records. A row without the expected identifier should not be mixed into an update merely because its name or phone looks familiar. Decide what that row represents before importing, and keep the original export so you can compare the chosen identifier with the source record.
Should I clean Phone and Mobile phone in the same pass?
Yes, when both fields need review: select them as separate phone columns and keep one output row per original contact. E164flow supports up to 10 selected phone fields.
Check the mapping explicitly rather than relying on column order. A phone-like value can appear under an unfamiliar header, while a column called Contact number may actually be an internal identifier. The import preview suggests fields from sampled values; your confirmation determines which columns the full conversion processes.
Review results using both source row and source column. If Mobile needs correction, that does not mean the contact's other phone field should be overwritten. The export can carry separate generated phone and extension fields for each selected source, making the final CRM mapping a deliberate choice rather than a single combined phone column.
What country information does the conversion need?
Map a country field for mixed-country national numbers, or choose a suitable default for a single-country list. An explicit international prefix takes priority over that default.
For example, 020 7946 0018 needs British country context, whereas +44 20 7946 0018 already carries an international prefix. Do not apply one country to every row simply because the business has one headquarters. The contact's phone may use a different country's numbering plan.
Include uncertain examples in the initial sample: a national number, an explicit international number, a blank country and a conflicting country hint. If the source does not establish the missing context, correct it from reliable information instead of guessing. A successful formatting result does not establish that the number is current or belongs to that contact.
Should I import every valid result or only Ready rows?
Begin with Ready results and investigate Needs review and Invalid results separately. A numbering-rule match is not enough to dismiss a warning about the source or country context.
Compare the original value with the generated output and read the warning attached to the relevant phone field. A numeric spreadsheet source deserves inspection because a zero or other information may have been lost before the converter received it. Keep the source row reference so the correction can be checked against the original record.
Duplicate references also need a business decision. Two HubSpot contacts can share a company switchboard, and one contact can repeat a number in several fields. E164flow does not merge records in HubSpot. Retain the contact identifier and decide which field to update instead of using a unique-number export as a contact-merging instruction.
How do I build the file that HubSpot will import?
Choose the record ID and the reviewed generated phone fields, then rename and order the export headers to match the mapping you intend to make in HubSpot.
The CRM columns shortcut is a starting layout for IDs, E.164 fields and extensions. Keep a full review report when you need the original values and validation details as well. If multiple phone columns are selected, check that each generated field is mapped to its corresponding destination rather than replacing an unrelated phone property.
Choose XLSX for a text-cell workbook, or CRM CSV when that suits the importing system. Spreadsheet-safe CSV is a different export choice and can add an apostrophe to protect a value beginning with +. Avoid opening and resaving an exact CRM CSV in Excel between the final preview and the import.
What should I compare after a small test import?
Compare the same source contacts before and after the import: their identifiers, the phone field you intended to change, the retained plus sign and any extension handling.
Use a sample containing a single-country number, an international number and a reviewed exception. Check the result in HubSpot rather than assuming the import preview guarantees the final display. Confirm that the operation updated the intended existing contacts and did not create new records because an identifier was missing or mapped incorrectly.
Only then apply the mapping to a larger reviewed file. E164flow's free account supports up to 50 rows per file and Pro up to 20,000. It prepares the file locally and does not sign in to HubSpot, send records to it or execute the import on your behalf. Keep the source, review report and imported file separately for traceability.
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.
- Keep the HubSpot record ID unchanged.
- Resolve invalid rows before overwriting an existing phone property.
- Import a small sample first and compare the result in HubSpot.
Start with the data you have.
Try sample contacts without an account. Create a free account to map your contact fields, check duplicates and export up to 50 contact rows.