Importing data

Importing data#

Import brings existing records in from a CSV or Excel file. Every module has its own import: Companies, Contacts and Deals each have an Import button on their list page.

Import in the right order#

Relationships are matched by name, so the thing being referenced has to exist first:

1. Companies
2. Contacts — their company is matched by name
3. Deals — their contact is matched by email or full name

Importing deals into an empty workspace fails on every row, and correctly so: there is no person to attach them to.

Step by step#

1. Open Companies, Contacts or Deals and select Import.
2. Select Download template and fill the template in. It carries the exact column names the importer expects, plus two example rows to replace.
3. Upload the file. Nazzam.ai reads the header row and maps the columns for you.
4. Check the mapping. Anything it could not match shows as Ignore — change it, or leave it if that column really is not wanted.
5. Choose how to handle Duplicates (see below).
6. Select Preview import. Nothing is written yet.
7. Read the preview, fix the file if needed, and then select Import.

The preview is the whole point#

The preview is a real dry run: every row goes through exactly the same validation as a real import, and nothing is written. What it reports is what you will get — including duplicates within your file, not just against records that already exist.

It tells you three things:

• how many rows will be created, updated or skipped
• which rows cannot be imported, and why — grouped by cause, so one bad column reads as one line rather than four hundred
• which columns were left unmapped, by name

Duplicates#

Choose what happens when an incoming row matches an existing record:

Matching uses company name, contact email (falling back to full name), and deal title.

Getting the formats right#

Phone numbers — international format, +20 100 123 4567. Numbers are validated against the country's numbering plan.

Email — must be a real address. n/a and - are errors, not blanks; leave the cell empty instead.

Dates — YYYY-MM-DD, for example 2026-09-30.

Amounts — digits. 250000 and 1,250.00 are both accepted; twelve hundred is an error that names the cell. A value written 1.250,00 is rejected on purpose: there is no way to tell whether that means 1,250 or 1.25, and importing the wrong one silently is worse than asking.

Currency — a three-letter code that is active in your workspace (Settings → Currencies).

Limits#

• 1,000 rows per file. Split larger files; there is no limit on how many files you import.
• .csv and .xlsx. Other spreadsheet formats need exporting to one of these first.
• Imports do not fire notifications or automations. Importing a thousand records should not send a thousand alerts.

Common mistakes#

Importing deals before contacts. Every row fails with "Contact not found". Import in the order above.

Company names that do not match exactly. "Delta Foods Ltd" in the contacts file will not find "Delta Foods" in the CRM. Match the name, or import the company first.

Deleting the template's header row. The header is how columns are matched. The instruction block above it can be deleted or left in place — the importer ignores it either way.

Assuming a skipped row imported. Read the preview counts. "Skipped" means the record already existed and was left alone, which is usually what you want — but it is not the same as "imported".