CSV Import Guide

This is a concise version of the CSV Import guide. For the full API documentation version, see API Docs: CSV Import.

Overview

Import customers and pools for an organization. Each row usually represents one pool. Customers can have multiple pools; pools belong to one customer.

Format

• Required: organizationId, and either customer_name or both first_name and last_name.
• Use customer_id/pool_id to update.
• Header aliases are accepted.

Fields

The importer reads two logical groups of columns. You can include either group or both in the same row.

• Customer fields: customer_id, customer_name, first_name, last_name, email, phone, notes, address1, address2, city, state, zip, country
• Pool fields: pool_id, pool_name, gallons, is_indoor, sanitizer, filter, pool_type, (optional location on pool) address1, address2, city, state, zip, country

Creation & update rules

• Customer update/create:
  • Update when any of: customer_id, or email, or (customer_name or first_name+last_name) + phone, or name + address1 matches
  • Merge-only updates to name, primary address, email, phone; other fields remain unchanged
• Pool update/create:
  • Update by pool_id; if absent, by (pool_name + resolved customer)
  • Merge-only updates to: pool_name, gallons, is_indoor, sanitizer, filter, pool_type, pool address*
  • Pool-only rows (no customer fields):
    • Create: include pool_name (a new pool_id is generated)
    • Update: include pool_id

Updating tip: If you include customer_id and/or pool_id, those rows will update the matching records directly. If you don’t have IDs, the importer safely matches using these keys in order: (1) email, (2) name+phone, (3) name+address. Pools match by (1) pool_id or (2) matching customer + pool_name. If no match is found, a new record is created.

Enumerations & Defaults

• is_indoor (boolean): true/false, yes/no, 1/0 (default: false)
• sanitizer (default: chlorine): chlorine, bromine, swg, biguanides, peroxide, natural, freshwater
• filter (default: cartrige): cartrige, sand, de, dontKnow
• pool_type (default: plaster): vinyl, plaster, fiberglass

Example

organizationId,customer_id,pool_id,customer_name,first_name,last_name,email,phone,address1,city,state,zip,country,pool_name,gallons,is_indoor,sanitizer,filter,pool_type
abc123,,,,Jane Doe,Jane,Doe,jane@example.com,555-111-2222,123 Main St,Austin,TX,78701,US,Backyard Pool,15000,false,chlorine,cartrige,plaster
abc123,,,,Jane Doe,Jane,Doe,jane@example.com,555-111-2222,123 Main St,Austin,TX,78701,US,Spa,500,true,bromine,cartrige,fiberglass

Updating existing records

• Best: include customer_id and/or pool_id from a prior export or record to update precisely.
• Without IDs: use the same email or the same name+phone or name+address to update a customer. For pools, use the same pool_name under that customer.
• Renaming a pool: include pool_id if you’re changing pool_name to avoid creating a second pool.
• Safe to re-run: the importer is idempotent with the matching rules above—re-importing the same rows updates rather than duplicates.

To upload: In your organization dashboard or the app’s Customers/Pools screen, use the Import menu. You can also import from your Organization Pools dashboard (look for the "Import CSV" button in the Organization Pools section).