How to switch from Skimmer to PoolBoss

Before you move anything, get clear on what you're actually fixing, because that decides whether the switch is worth a weekend. For most operators leaving Skimmer it's the bill. Skimmer charges per serviced location with a monthly minimum, so every account you win quietly raises your software cost - the better you do, the more you pay to run the same tool. PoolBoss charges a flat rate by pool-count tier with unlimited users, and there's a free tier for a very small route, so growth stops being something your software taxes. If you want the line-by-line numbers, how PoolBoss and Skimmer compare lays the pricing and features out side by side.

Here's the reassuring part: the day-to-day barely changes. The work you rely on Skimmer for - recurring routes on your phone, chemical readings logged per pool, and a proof-of-service summary sent after each visit - all exist in PoolBoss and run the same way. You're not learning a new trade, you're moving the same routine to a tool that doesn't bill you more every time you add a pool. So the only real question is the mechanics of the move, and those are simpler than the dread suggests.

Start by pulling your data out while your Skimmer account is still active. In Skimmer, open Settings and use the Export option to download your customers and service locations to a spreadsheet - names, contact info, service addresses, and each pool's specs. Skimmer hands you this export directly, so the data itself isn't the hard part. If you can also export recent service and billing history, save it as a reference file even if you don't re-key every visit; it's the record you'll want if a customer ever asks about work done before the switch.

Do this first, before you cancel anything. The single mistake that turns a clean switch into a headache is letting the old account lapse before you've safely pulled everything out of it. Export, confirm the file opens and looks complete, then keep that file somewhere safe as your source of truth for the rest of the move.

Spend twenty focused minutes on the export before you touch the new system, because this is where a sloppy switch goes wrong months later. Open the file and check the columns that matter operationally: the service address on every line, gate codes and access notes, and each pool's gallons, surface type, and sanitizer (chlorine, salt, or other). A wrong gate code or a missing unit number is exactly what becomes a real missed-stop call in week one.

Scan for blanks and fix them now while you still have Skimmer open to check against. Group the rows the way your routes actually run if it helps you enter them faster later - by neighborhood or by service day. You're not reformatting for a machine; you're making the next step fast and accurate, and a clean spreadsheet is what lets one person enter a whole book in an afternoon instead of fighting it for a week.

Now build your book in PoolBoss. Each customer carries their contact info and address; each pool hangs off a customer and carries its specs, so your techs see gallons, surface, and sanitizer type right at the stop. This is the bulk of the move - once your accounts and pools exist in the new system, routes and visits build on top of them.

Today you enter your book by hand, and for a typical route that's a single focused afternoon, not a project - a solo operator running 50 pools across Mesa and Gilbert can get every customer and pool in before dinner if the spreadsheet from Step 2 is clean. A one-click importer that reads your Skimmer export and loads your customers and pools in a single pass is on our roadmap; until it ships, manual entry is the path, and because you only do it once, it's more forgiving than it sounds. Work top to bottom through your cleaned file in one sitting rather than spreading it across a distracted week.

With your pools in, group them into the routes you actually run - Westside Monday, Eastside Tuesday - set the stop order, and assign each route to a tech. PoolBoss route management is built around recurring routes, so you set a route up once and it repeats on the schedule you choose instead of being rebuilt every week. Your techs then see today's stops in order on their phone, with the address and access notes you brought over right there.

This is also the moment to fix anything that bugged you about the old setup. If two routes should really be three, or a stop order grew inefficient as you added accounts over the years, rebuild it the way you wish it had been - you're entering it fresh anyway, so there's no cost to doing it right this time.

Don't flip the switch cold. Run PoolBoss alongside Skimmer for one full service cycle - a week for most routes - with your techs logging visits in the new app while the old one stays open as a safety net. This overlap is how you catch a missing pool or a wrong gate code before it costs you a missed stop, and it's the reason the switch carries no downtime.

Here's the realistic version. You run 50 pools across Mesa and Gilbert on a Monday-through-Friday rotation. You spend a weekend on Steps 1 through 4, run the first week in both tools, confirm every stop logged correctly in PoolBoss, then cancel Skimmer at the end of that week. Time that week for a slower stretch, not your peak summer load, so the small learning curve never collides with your busiest days. Once you've watched a clean week go through the new app, cancelling the old account is the easy part.

One worry that stops operators from switching is the customer side: will clients notice, will it look unprofessional, will the phone start ringing. In practice the switch is invisible to them. They get serviced on the same day by the same person, and they still get a proof-of-service summary after each visit - what you tested, what you added, that you showed up. That report doesn't depend on which software you run it from, so the experience your customers see doesn't change.

Billing is the one place a customer might notice, and only a little. If you send invoices with an online payment link, that keeps working from the new tool - completed visits become invoices, and customers pay online the same way. The one courtesy worth extending is a short heads-up to anyone whose card statement might show a different payment descriptor, so it doesn't read as a surprise charge. Beyond that, most operators say nothing and no one notices the change.