A lead file that imports cleanly saves hours of fixing records by hand later. Run through this list before you upload.

Before you upload

One lead per row. Remove subtotal rows, merged cells and blank rows between blocks.
One header row. The first row should contain column names only. Mapping is done by header name, so Mobile, Phone or Contact No are all fine — just be consistent.
A phone number on every row. Phone is how VM CRM recognises a person. Rows without one are imported but can’t be checked for duplicates.
Any phone format is fine. 98765 43210, +91-98765-43210, 09876543210 and 919876543210 are all stored as +919876543210. Numbers that Excel has turned into scientific notation (9.88E+09) must be fixed first — format the column as Text.
Split names if you can. Separate First name and Last name columns give better search and personalisation. If you only have one Name column, map it to First name.
Use the same values for dropdown fields. “Mumbai”, “mumbai” and “Bombay” become three different cities in reports.
Dates as dates. Use a real Excel date format, not text like “next Tuesday”.

Choosing options

Duplicate policy.
- Skip — the safest default. Existing leads are left untouched.
- Update — fills in new information on existing leads (for refreshed portal exports).
- Allow — imports everything; use only when you deliberately want repeat enquiries as separate leads.
Assignment. Assign round-robin during the import to save a step, or leave the leads unassigned and distribute them later.

Download the error report if any rows failed. It lists each failed row with the reason. Fix those rows in the file and import just them again.

Large files (up to 200,000 rows) are processed in the background in chunks. You can keep working while the progress bar fills.

Need a starting point? Download the lead import template.