Bring your customers, pools, and routes over in an afternoon

Upload a spreadsheet or an export from your old pool service software on the import screen. PoolBoss reads the file and automatically proposes which column maps to which field - customer name, contact info, address, and so on - without you filling out a column-by-column form. You then see that proposed mapping on a review screen, where you can correct anything it got wrong before confirming. Nothing is written to your account until you confirm the mapping. The same flow imports pools, routes, and service history, each keyed off the customers you've already brought in. You do not need to reformat your file first or match PoolBoss's exact column names - the mapping step exists specifically so an arbitrary export works.

Yes. Export your customer, pool, route, and service history data from your current software - most pool service tools, including Skimmer, offer a CSV or spreadsheet export - and upload it to PoolBoss's import screen. The column mapping is automatic: PoolBoss reads the header row (or detects where your data actually starts, if the export doesn't put headers on row one) and proposes a mapping for you to review and confirm. You are not manually re-entering your book of business or reformatting a file to match a rigid template. If the first import misses something and you need to re-run it, PoolBoss recognizes records it already has and skips them, so a second pass tops up rather than duplicating your customer list.

No. PoolBoss proposes the column mapping automatically by reading your file's headers and a sample of the data, then merges that against a deterministic set of common-pattern rules so the mapping is never worse than a basic heuristic would produce on its own. You see the finished proposal on a review screen rather than building the mapping field by field. From there you can correct anything that's ambiguous - a file with two address columns, for instance - before confirming. The goal is that a typical export needs little to no manual remapping, while an unusual file still gives you full control to fix what the automatic pass got wrong.

PoolBoss checks for records it already has before writing new ones, so re-uploading the same file does not create duplicate customers, pools, or service history entries. Pools are matched against the customer they belong to, and service history entries are matched against the specific pool and service date (or an external reference id when your export includes one). This means you can safely re-run an import if the first pass was incomplete, or if you're pulling in an updated export from your old system - PoolBoss tops up what's missing instead of doubling every record that was already imported successfully.

PoolBoss accepts CSV files and tab-separated files (including .tsv or .txt exports), so most spreadsheet and pool-service-software exports work without conversion. The parser sniffs the delimiter from the file itself rather than requiring you to specify it, and it detects where the header row actually is instead of assuming your data starts on row one - so an export with a few blank or title rows at the top doesn't get misread and doesn't lose real records. If you're not sure your file will work, the review step before import shows you exactly what got parsed and how many rows, if any, were skipped, so you can catch a formatting problem before anything commits.

Most operators bring their customers, pools, routes, and service history over in an afternoon. The bulk of that time is exporting the data from your current system - the import itself is upload, review the automatic column mapping, fix anything that needs it, and confirm. There's no manual data-entry step for your existing book of business, and no waiting on a migration specialist. If you want to double-check the results or your export was split across multiple files, you can re-run the import without creating duplicates, since PoolBoss recognizes records it's already brought in.