Import CRM data
Bring accounts, contacts, and notes into Vertiqa from a CSV export, with column mapping and duplicate-safe import.
The CRM Import Center brings your existing customer data into Vertiqa from a CSV export — accounts, contacts, and notes in one pass. It's the tool to reach for when you're migrating off another system or onboarding a backlog of records. You need both account-create and contact-create permissions to use it.
What it imports
Accounts, their contacts, and notes — plus your account and contact custom fields, if you've defined any. (Leads and opportunities aren't imported here.)
Import a CSV
-
Open CRM → Import (route
/crm/import). You can also get here from Import data on the Accounts or Contacts page.
Start by choosing where the file came from and uploading it. -
Pick the legacy source: Spreadsheet / CSV, HubSpot, Salesforce, Pipedrive, Zoho, Jobber, ServiceTitan, Housecall Pro, or Other. The source helps Vertiqa guess the column layout.
-
Upload your CSV. Vertiqa reads it and suggests a field for every column.
-
Check the mapping. Each row shows a CSV column, a sample value from it, and the Vertiqa field it goes to, with a running X of N columns mapped count. Change any field that's wrong, or choose Don't import to skip a column.

Company Phone wasn't recognized. Choose Phone so the number comes across. -
Preview. Before anything is written, you see how many rows are ready, how many contacts they create and how many are blocked, and the first rows tagged Ready, Ready with warnings or Blocked.

Only Ready rows are imported. Fix Blocked rows in the file and upload it again. -
Import. Select Import N. Only ready rows are imported. Existing accounts and contacts are matched and skipped rather than duplicated, so you can re-run a file safely. A progress bar and a per-row log (Imported, Skipped, Partial, Failed) show what happened.
-
Keep a record. Download log saves the results as a CSV, and past runs are listed under Recent imports, where you can reopen their results.
Source tags
Every import automatically tags the records it brings in — once with the
file's name and once with an import: tag — so you can always find or filter
the batch you loaded later.
Tips
- Clean the CSV first. The mapping step is only as good as your column headers — consistent headers mean less manual mapping.
- Trust skip-existing. If an import is interrupted or you're unsure what loaded, re-running the same file won't create duplicates.
- Check the Blocked rows in preview before importing — they won't load, and the reason is usually a missing required field you can fix in the CSV.