pplCRM

Import from CSV

One guided wizard imports people, companies, households, or tasks from a spreadsheet in four steps. Matched, tagged, and deduplicated.

2 min read

Import / export in the DATA section of the sidebar is history for both directions. To start an import, use Import CSV at the top of that page, or Import CSV in the People, Companies, Households, or Tasks toolbars. Either opens the wizard at /imports/new: Upload → Map columns → Review → Import. The upload step asks what you are importing (people, companies, households, or tasks); coming from a grid preselects its type. Nothing is written to your database until the last step.

Prepare the file

  • Use a CSV with a header row. Column names like “First name”, “Email”, “Phone”, “Company”, or “Tags” are preselected automatically on the mapping step.
  • For people: a Company column links each person to a company, creating the company if no existing one matches its name. Addresses do the same for households. A Tags column applies its comma-separated tags to just that person.
  • For companies and tasks the wizard needs a mapped name column. Rows without one are skipped. For households, rows matching an address you already have (or repeated in the file) are skipped, and new addresses are queued for geocoding.
  • Both UTF-8 and Excel-exported CSVs work as-is.

The four steps

  1. UploadDrop the file or browse to it. You’ll see the row and column counts before anything else happens.
  2. Map columnsEach column gets a best-guess field match. Review and correct it. Anything left unmapped shows a “Skipped” chip and is left out.
  3. ReviewFor people, duplicates are matched by email, the same identity rule used everywhere in pplCRM. Rows that match an existing person let you merge (fills blank fields, never overwrites), skip, or import as new anyway. Rows with a broken email address get their own choice: skip them or import without an email. Add a comma-separated tag list and/or a list here too (tags also apply to household imports). Other types show a plain recap: how many rows will import and how many will be skipped, and why.
  4. ImportConfirm the recap and click Import N people (or companies, households, tasks). The import runs in the background, so you can navigate away while it works. It lands in import history and the Activity log either way. If you stay, the done screen offers View imported records, Import another file, or Back to import history.

After the import

  • Spot-check a few records against the source file.
  • If you chose "import as new anyway" for any matched duplicates, run the Duplicates finder to reconcile them when convenient.
  • The import history row shows what type each import was and keeps the original file downloadable for 90 days; for people imports, skipped rows are downloadable with the reason each was skipped.
Test with a small file first
Run a ten-row slice through the wizard before the full file. If the column mapping is off you fix ten records, not ten thousand.
Related

Try this on sample data.

Every feature in the docs is live in the free demo workspace — no card, nothing to lose.

Start free