DATA · 4 MIN READ

Importing contacts

Bulk-load contacts from any CRM you're migrating from (Salesforce, HubSpot, Pipedrive) or a spreadsheet. Up to 10,000 rows per upload, dedupes on email automatically.

1. Export from your old CRM

Export a CSV. Most tools call this "Export contacts" or "Export leads." You don't need a specific column layout — you'll map your columns to OraTek's in step 3.

2. Open the importer

Settings → Bulk import → Choose CSV file. The wizard opens with your first 5 rows previewed.

3. Map your columns

OraTek auto-guesses based on column names ("Email" → email, "Company Name" → company). Anything it can't guess shows "— skip —"; you can map manually from the dropdown.

Supported target fields

full_name or first_name + last_name
email (used for dedup; lowercased)
phone, title, company, industry, location, website
deal_stage (one of your pipeline stages — see Settings → Pipeline)
deal_value (number)
notes
tags (comma- or semicolon-separated)

4. Preview

Click Preview import. You'll get four counts:

Create — net-new rows.
Update — emails matching an existing contact. Empty fields in the CSV won't overwrite real data on the existing row.
Skip — rows with validation issues (no name and no company, malformed email).
Total — what was in the CSV.

The issues section lists the first 5 problem rows with line numbers so you can fix the source file.

5. Commit

Click Commit import →. The whole thing runs in a single transaction — if something fails midway, nothing lands. On success, your contact list reloads with everything in place.

Dedupe behavior: matching is by (organization_id, email). Two rows with the same email update each other; rows with empty email always create new contacts. If you want to merge non-email duplicates, do it after import via the Settings → Lead types page.

Templates

A working CSV template lives at /help/templates/contacts-template.csv (coming soon — for now just match the field names above).