WRAPTORHelp & Docs

Imports — bring your shop's data from another tool

Who it's for

The owner or manager moving the shop off another CRM — OrbisX, Urable, Tint Wiz, Zoho, Jobber, or anything that can export a CSV. Ten minutes with an export file replaces weeks of retyping the book of business.

Where it fits

Migration is a day-0 job: bring your customers (with their vehicles) and the work already in flight, then run everything in Wraptor from the first real day. The onboarding checklist and first-run screen both point here. See workflow-map.md.

Overview

The migration hub (/import) lists the tools shops usually come from. Pick yours (or "Another tool / plain CSV") and it routes you into the right wizard with the source pre-selected. Two lanes:

  • Customers & vehicles (/customers/import) — names, contact details, addresses, notes, plus one vehicle per row (year, make, model, color, VIN, plate). A customer appearing on several rows gets several vehicles.
  • Jobs (/jobs/import) — active work from Trello, Asana, Monday, Jobber, or ClickUp, mapped onto your workflow stages. Jobs without a customer land in a triage bucket you can reassign from the board.

Column mapping, three tiers:

  1. Recognized exports (Jobber Clients, Zoho CRM Contacts, and the four PM-tool job formats) are detected from their headers and pre-mapped.
  2. Everything else auto-maps by header name — "Cell Phone", "E-mail Address", "Vehicle Make" and dozens of synonyms land on the right fields instantly, free.
  3. AI auto-map — when header names are too weird for the synonym table, one click sends the headers plus three sample rows (never the whole file) to AI for a proposed mapping. You always see and can change the proposal before anything imports.

Safe to re-run. Every imported record carries its source and original id. Re-uploading a corrected export updates the same customers, vehicles, and jobs instead of duplicating them; existing customers also match by email or phone. Within-file duplicates fold onto one record.

Rules worth knowing

  • Files are parsed in your browser — the CSV itself never uploads; only the mapped rows do, in small batches.
  • Bulk imports deliberately do not push each customer to QuickBooks/Xero (a 5,000-row import must not fire 5,000 accounting writes). Synced customers pick up on their next normal touch.
  • A vehicle row identified only by VIN or plate imports with "TBD" make/model placeholders you can fix later.
  • OrbisX, Urable, and Tint Wiz don't publish their export formats, so their tiles run the auto-mapper rather than a fixed template. If a file won't map, email it to support — we'll map it with you (and teach the importer its format).

Common tasks

  1. Migrate from another CRM
    1. In your old tool, export customers (include vehicle columns if it has them) as CSV.
    2. Open /import, pick the tool, upload the file.
    3. Check the mapping (fix anything mis-guessed), preview, import.
    4. Re-export and re-upload any time — records update, never duplicate.
  2. Bring your active jobs — same flow from the Jobs card; you'll also map your old tool's columns/statuses onto your workflow stages.