Skip to main content
Import multiple leads from one CSV or Excel file. Nexor creates the leads in the background and reports how many rows were imported, skipped, or failed.

​
Prepare the file

  • Use a .csv or .xlsx file. Legacy .xls files are not accepted.
  • Keep the file at or below 50 MB. The current importer limits file size. It does not enforce a separate 10,000-row maximum.
  • Put column names in the first row and include at least one data row.
  • For CSV files, Nexor detects common delimiters and accepts UTF-8 or Windows-1252 text.
  • For Excel files with more than one worksheet, select the worksheet to import in the mapping step.
  • The mapping screen validates up to 50,000 rows in the browser. For a larger file, it shows an estimate instead of an exact row-by-row preview; the background importer still processes the file.
The upload panel includes a downloadable template with first_name, last_name, email, phone, and company columns.

​
Required fields

The column mapping must include:
  • First name (first_name).
  • At least one contact field: Email (email) or Phone (phone).
The same rule applies to every row. Nexor skips a row if its first name is empty or if both its email and phone are empty.
A last name by itself does not satisfy the required name. Map a column to First name and make sure each row has a value in that column.
Use complete international phone numbers, such as +56912345678, when possible. This avoids ambiguity when a number belongs to a country other than the one configured for the account. Use YYYY-MM-DD for dates of birth.

​
Upload and map the columns

1

Open the importer

Go to Leads → New → Upload CSV or XLSX.
2

Choose the file

Drop the file into the panel or select Upload. You can also download the formatted CSV template.
3

Review the mapping

Nexor suggests a destination for each file column. Review every suggestion and change it when necessary.
4

Choose what to keep

Map columns to lead fields, store additional columns as Metadata, or choose Skip column. Each standard lead field can be mapped once; several columns can be stored as metadata.
5

Choose an Agent

Assignment is optional. Select an Agent to create the leads in that Agent, or leave None to create them without an Agent.
6

Start the import

Select Import and keep the panel open until it shows the result. Closing the panel while the import is running requests cancellation and waits for the worker to confirm it.
The available destinations are first name, last name, email, phone, company, title, city, date of birth, external ID, and metadata.

​
How duplicates are handled

The file importer uses a skip strategy for duplicates. It does not offer an update or merge option. An archived lead with a matching external ID is the exception and can be restored.
  • If the same phone appears more than once in the file, Nexor keeps one valid row and skips the other rows with that phone. Equivalent national and international formats are also compared when Nexor can normalize them.
  • If an Agent is selected, Nexor skips a phone that already has an active conversation with that same Agent.
  • If an external ID already belongs to an active lead from the same import source, Nexor skips the row. An archived matching lead can be restored instead.
  • Email by itself is not a general duplicate key in this importer. Two email-only rows with the same address can create separate leads.
  • Nexor compares the file’s exact bytes within the account and stores a checksum, which is a fingerprint of those bytes. The same content cannot start a second import while another import retains that checksum, including while that import is still running.
Changing even one byte makes it a different file, but the row-level duplicate rules still apply.

​
Cancellation, retries, and Agent assignment

  • Cancelling stops new import work, but leads created before the cancellation remain in Nexor.
  • A failed or cancelled import that created no leads releases the exact-file checksum. You can upload those same bytes again.
  • Once an import creates at least one lead, it keeps the checksum. The exact same file remains blocked so a retry cannot create a second copy of the rows that already landed.
  • Technical creation errors are retried per row. A row that exhausts those retries appears as failed. Missing required values and duplicates appear as skipped.
  • If an Agent is selected, Nexor creates each lead before completing the Agent assignment and contact setup. A failure in that later step does not remove the lead. The created count confirms lead records, not that every selected Agent started successfully.
Correct skipped rows and upload a new file if they still need to be imported. After an Agent import, open a sample of the new leads and confirm the expected Agent and stage before relying on automated outreach.
Last modified on September 7, 2026