Lead Import
Overview
Convertly CRM supports bulk lead import via CSV. Use this to migrate leads from another CRM, an ad platform export, or a spreadsheet.
Supported file formats
| Format | Supported |
|---|---|
| CSV (comma-separated) | ✅ Yes |
| Excel (.xlsx) | ❌ No — convert to CSV first |
| JSON | ❌ No |
How to import leads
- Go to Dashboard → Leads → Import
- Click Download Template to get the standard CSV format
- Fill in your data using the template
- Click Upload CSV and select your file
- Map each column to a lead field
- Review the validation summary
- Click Import Leads
Field mapping
During import, you will see a column mapping screen. Match each column in your CSV to a Convertly field.
| Convertly field | Required? | Notes |
|---|---|---|
first_name | ✅ Required | |
last_name | Optional | |
email | Recommended | Used for deduplication |
phone | Optional | |
status | Optional | Defaults to first pipeline stage |
source | Optional | |
notes | Optional | |
gclid | Optional | Attribution data |
fbclid | Optional | Attribution data |
utm_source | Optional | |
utm_medium | Optional | |
utm_campaign | Optional | |
assigned_to | Optional | Must match a team member’s email |
Import validation
Before the import finalizes, Convertly runs validation checks:
| Check | Behavior |
|---|---|
| Missing required fields | Row is skipped; listed in the error report |
| Duplicate email | Flagged; you can choose to skip or update the existing record |
| Invalid phone format | Warning logged; row is imported but phone may be unusable |
| Unrecognized status value | Defaults to the first pipeline stage |
| Unrecognized assignee email | Assignment is skipped; lead is created unassigned |
After import, you receive a summary showing:
- Total rows processed
- Leads successfully imported
- Rows skipped (with reasons)
Import limits
Each import file supports a maximum of 5,000 leads. For larger data sets, split into multiple files and import each batch separately.
There are no plan-based limits on import file size — the 5,000 per file cap applies to all accounts.
Notes on attribution data
If you are importing leads that already have gclid or fbclid values from a previous system:
- Include them in the import CSV using the
gclidandfbclidcolumns - These are stored with the lead record
- They will be used if you later trigger a conversion event manually on that lead
Imported leads do not automatically trigger offline conversion events to Google or Meta — only pipeline stage changes trigger those events.