A CRM import should start with a frozen source file and an agreed identity rule. Cleaning columns without defining how contacts, companies and deals relate can produce neat looking but wrong records. Preserve the original file, document every transformation and test a small sample before full import.
Decision framework
| Step | Practical check |
|---|---|
| Inventory files | List each source, owner, update date and purpose; remove fields with no lawful or useful business purpose. |
| Choose identifiers | Decide how email, phone, company and legacy IDs identify a person or deal, including shared addresses. |
| Normalize values | Standardize dates, country codes, stage labels and owner names in a working copy. |
| Reconcile | Count source rows, matched duplicates, rejected rows and imported records after a sample run. |
How to make the decision
Create a mapping sheet with source column, target field, transformation, exception rule and approver. Deduplicate only after reviewing collisions: two family members may share a phone, and a company may have several contacts. Test the import in a safe environment or a tiny reversible batch, export the result, and compare record counts and relationships. Keep a rollback route before importing thousands of rows.
Worked example
Synthetic five-row import: two rows share the same email but carry different last names; one has no owner and one deal refers to a missing company ID. The reviewer resolves the shared email manually, assigns the unowned contact to a queue and fixes the company reference. The sample imports four distinct contacts and one deal; the rejected-row log explains why the fifth source row was merged.
What can change the answer
Never overwrite a live CRM solely because a spreadsheet looks clean. Confirm consent and access rights for personal data, and do not expose real contact details in a test report.
Review checklist
- Is the untouched source file retained?
- Can every merged or rejected row be explained?
- Did a sample export prove owners and relationships survived?
Common question
Is email enough to deduplicate contacts?
It is a useful signal, but shared addresses, changed emails and incomplete records require an exception review.
Next useful step
For the wider CRM choice and requirements discussion, read: What a CRM needs to do for a business. For help applying this to a UAE business, see Megvi’s CRM development service. Bring the source records and the decision you need to make.
Source checked 25 October 2026: HubSpot Knowledge Base: format import files. Check the current interface and policy before editing an account or profile.
Worked examples are illustrative unless a public source is explicitly named; they are not claimed Megvi client outcomes.
Ahmed Elneil
https://megvidigital.comAhmed Elneil is a certified digital marketer and entrepreneur with over 5 years of experience helping brands grow through Search Engine Optimization (SEO), paid advertising, and CRM automation.