Importing customers from a CSV or QuickBooks

Two paths in: a one-click QuickBooks Online sync, or a CSV upload. Both end at the same place — your customer list ready to attach to jobs and quotes.

QuickBooks Online (recommended)

1. Open Customers → Import → QuickBooks.
2. Sign in to QuickBooks. We use the official OAuth flow — your credentials never touch our servers.
3. Pick which company file to sync (most owners only have one).
4. Hit Pull customers. The import runs in the background and you'll get a notification when it's done. Most lists finish in under a minute.

CSV upload

If your list lives in a spreadsheet, export it as CSV and upload it from Customers → Import → CSV. We auto-detect column headers and let you remap any that look off. The file can include unrelated columns — we just ignore them.

Supported encodings: UTF-8 and Windows-1252. If you exported from Excel, save as CSV UTF-8 rather than the default to avoid mangling accents and dashes in customer names.

Field mapping reference

Here's the minimum we need for an import to be useful:

• name — required, free text
• email — optional but lets you send digital quotes
• phone — optional but required for SMS notifications
• address_line_1, city, state, zip — optional, used for routing
• notes — optional, anything you want surfaced on the customer page

How we handle duplicates

We match on email first, then phone, then a fuzzy name match within the same address. If we find a likely duplicate during import, we'll flag it on the review screen and let you choose whether to merge or keep both. We never silently overwrite an existing record.

Fixing import problems

• Wrong column mapped: open the import and click Re-map columns at the top — your previous mapping is saved as a starting point.
• A whole batch went to the wrong customer: every import has its own ID. Open Settings → Imports, find the run, and click Roll back. The customers and any auto-created jobs are cleanly removed.
• QuickBooks sync stuck: disconnect and reconnect from Settings → Integrations. Stuck syncs are almost always an expired refresh token after a long idle period.