Back to app
Import CRM data

Import CRM data

Bring accounts, contacts, and notes into Vertiqa from a CSV export, with column mapping and duplicate-safe import.

Reviewed OperatorVertiqa 1.54+

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.)

How an import works

  1. Pick the legacy source. Choose where the CSV came from — Spreadsheet / CSV, HubSpot, Salesforce, Pipedrive, Zoho, Jobber, ServiceTitan, Housecall Pro, or Other. The source helps Vertiqa guess the column layout.
  2. Upload your CSV.
  3. Map the columns. Vertiqa auto-detects a mapping, then lets you adjust it: for each CSV column you see a sample value and the Vertiqa field it maps to, a running "X of N columns mapped" count, and a Don't import option for columns you want to skip.
  4. Preview. Before anything is written, you get counts (rows, ready, contacts, blocked) and a sample of the first rows, each tagged Ready, Ready with warnings, or Blocked.
  5. Import. 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 result log (Imported, Skipped, Partial, Failed) show what happened.
  6. Download the log as a CSV if you want a record of the run, and find past runs in the Recent imports list to 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.
Was this helpful?