Back to app
Migrating a client onto Vertiqa

Migrating a client onto Vertiqa

The import paths that exist today for moving a client off HubSpot, spreadsheets, Airtable, or another CRM — what comes across, what doesn't, and where assisted migration fits.

Reviewed AdminVertiqa 1.61+

Moving a client onto Vertiqa is a CSV import. Know exactly what that supports before you promise a timeline — a data-savvy client will drill here, and a specific answer earns credibility a vague one loses.

What the import brings across

The CRM Import Center loads, in one pass:

  • Accounts (the companies).
  • Contacts on those accounts.
  • Notes.
  • Custom fields you've defined on accounts and contacts.

The importer auto-detects a column mapping, lets you adjust it, previews every row (Ready / Ready with warnings / Blocked) before writing anything, and matches and skips existing records rather than duplicating — so a file can be re-run safely. Every batch is tagged so you can find or roll back what you loaded. See Import CRM data for the full step-by-step.

What it does not bring across

Be upfront about the edges:

  • Leads and opportunities are not imported through this tool — only accounts, contacts, and notes.
  • There is no bulk import for other record types (projects, meetings, invoices, and so on). Those are set up in-product, not migrated.

Source-by-source

  • HubSpot, Salesforce, Pipedrive, Zoho — named source presets. Export the client's contacts/companies to CSV from the old system, pick the matching preset, and the importer guesses the column layout for you.
  • Spreadsheets — choose the Spreadsheet / CSV preset. This is the cleanest path when the client already keeps customers in a sheet.
  • Airtable — export the relevant table to CSV, then import it as a spreadsheet. There's no direct Airtable connector; the CSV round-trip is the supported path.
  • Field-service systems (Jobber, ServiceTitan, Housecall Pro) and anything else — presets exist for the first three, and an "Other" option covers the rest.

Assisted migration for pilots

For a pilot or founding-partner client, migration is something you and Vertiqa do together — cleaning the export, mapping fields, and validating the result. That hands-on pass is the honest answer to "who does the migration": it isn't a fully self-serve, any-shape-of-data tool yet, and saying so beats promising migration tooling that doesn't exist.

Was this helpful?