How to switch from Skimmer to PoolBoss

By The PoolBoss Team · Last updated September 29, 2026

Switching from Skimmer to PoolBoss takes a weekend with no downtime. Export your customer and pool list from Skimmer and set those customers and pools up in PoolBoss. Rebuild your routes and assign your techs. Then run both tools side by side for one billing cycle before you cancel Skimmer. Pick a slower week.

Most operators don't leave Skimmer because it stopped working. They leave because the per-location bill keeps climbing as the route grows. At some point, a flat rate that doesn't charge you for every new account looks a lot better. The software does the job. The pricing model is what sends people looking for the exit.

The fear with any switch is always the same. You worry about losing years of service history, or going dark for a week mid-season while you learn a new tool. Neither has to happen. Moving a pool service business is mostly moving a customer list and rebuilding routes. You can do it over one weekend, with both systems running side by side until you're sure. Here's the whole thing, step by step, plus a straight read on what it costs you and what it saves.

Key takeaways

  • Most operators switch for the pricing model, not missing features. Skimmer's per-location price rises as you grow, and a flat rate by pool count stops that climb.
  • Your day barely changes. Recurring routes, chemical logs for each pool, and proof-of-service reports all carry over.
  • Export your customers, pool specs, and recent history from Skimmer (Settings, then Export) before you cancel anything. Never let the old account lapse first.
  • Spend twenty minutes cleaning the export: addresses, gate codes, gallons, surface, and sanitizer. A clean file lets one person enter a whole book in an afternoon.
  • Import the cleaned export as a CSV instead of retyping it. Do customers first, then pools. You get a preview before anything saves, and rows you already have get skipped.
  • Run both tools side by side for one full service cycle, so you catch gaps before they cost you a stop. That overlap is why there's no downtime.
  • Switch during a slower week, and tell customers their service and reports won't change.

Why operators leave Skimmer, and what doesn't change

Before you move anything, get clear on what you're fixing. 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 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 on paid plans. There's also a free plan for a very small route. Growth stops being something your software taxes. For the line-by-line numbers, how PoolBoss and Skimmer compare lays out the pricing and features side by side.

Here's the good news. Your day barely changes. PoolBoss runs the work you count on Skimmer for the same way. You get recurring routes on your phone, chemical readings logged for each pool, and a proof-of-service summary sent after each visit. 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. What's left is the mechanics of the move, and those are simpler than you'd think.

Step 1: Export your data out of Skimmer

Pull your data out while your Skimmer account is still active. In Skimmer, open Settings and use the Export option. Download your customers and service locations to a spreadsheet. That covers names, contact info, service addresses, and each pool's specs. Skimmer gives 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-enter every visit. It's the record you'll want if a customer asks about work done before the switch.

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

Step 2: Clean and map the spreadsheet

Spend twenty minutes on the export before you touch the new system. This is where a sloppy switch goes wrong months later. Open the file and check the columns that matter on the route. That's 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 turns into a missed-stop call in week one.

Look for blanks and fix them now, while you still have Skimmer open to check against. If it helps, group the rows the way your routes run, by neighborhood or by service day. You're not formatting for a machine. You're making the next step fast and correct. A clean spreadsheet lets one person enter a whole book in an afternoon, instead of fighting it for a week. Save the cleaned file as a CSV while you're in it. That's the format importing a customer list reads.

Step 3: Set up your customers and pools in PoolBoss

Now build your book in PoolBoss. PoolBoss keeps each customer's contact info and address, with each pool hanging off its customer and carrying its specs. Your techs see gallons, surface, and sanitizer type right at the stop. This is most of the move. Once your accounts and pools are in the new system, routes and visits build on top of them.

You don't have to enter your book by hand. PoolBoss imports the cleaned CSV from Step 2. It reads your header row and matches columns like "Client Name" and "Svc Address" to the right fields on its own. It shows you a preview before anything saves. A solo operator running 50 pools around Tulsa and Broken Arrow gets through customers and pools in minutes, not an afternoon. Run them in order, customers first and then pools, so each pool attaches to the customer who owns it. Rows that match a customer you already have get skipped, not duplicated. So a second pass after a fix is safe.

Step 4: Rebuild your routes and assign your techs

With your pools in, group them into the routes you run, like Westside Monday and Eastside Tuesday. Set the stop order and assign each route to a tech. PoolBoss builds every route to recur. You set a route up once, and it repeats on the schedule you choose. You don't rebuild it every week. Your techs see today's stops in order on their phone, with the address and access notes you brought over.

This is also the time to fix anything that bugged you about the old setup. Maybe two routes should be three. Maybe a stop order got messy as you added accounts over the years. Rebuild it the way you wish it had been. You're entering it fresh anyway, so doing it right costs you nothing.

Step 5: Run both systems side by side, then cut over

Don't flip the switch cold. Run PoolBoss next to Skimmer for one full service cycle, which is a week for most routes. Your techs log 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. It's why the switch has no downtime.

Here's how it plays out. You run 50 pools around Tulsa and Broken Arrow on a Monday through Friday rotation. You spend a weekend on Steps 1 through 4. You run the first week in both tools and check that every stop logged correctly in PoolBoss. Then you cancel Skimmer at the end of that week. Pick a slower stretch for that week, not your peak summer load, so the learning curve doesn't hit on your busiest days. Once you've watched a clean week go through the new app, canceling the old account is the easy part.

What your customers see during the switch (almost nothing)

Some operators hold off on switching because of the customer side. Will clients notice? Will it look sloppy? Will the phone start ringing? For the customer, the switch is invisible. They get serviced on the same day by the same person. They still get a proof-of-service summary after each visit that shows what you tested, what you added, and that you showed up. That report doesn't depend on which software you send it from, so nothing changes on their end.

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. Finished visits become invoices, and customers pay online the same way. Give a short heads-up to anyone whose card statement might show a different payment name, so it doesn't look like a surprise charge. Past that, most operators say nothing and no one notices.

Frequently asked questions

Can I import my data from Skimmer?

Yes. In Skimmer, open Settings and export your customers and service locations to a spreadsheet while your account is still active. Save that export as a CSV and run it through the customer importer. The importer reads your header row and matches columns to the right fields on its own, so a Skimmer export usually needs no renaming first. Nothing is saved until you look over a preview. It shows the matched columns, the row counts, and the first few rows exactly as they'll be stored. Import customers first, then pools, then routes and service history, because each one attaches to what came before it. Re-running a customers, pools, or history file skips the rows you already have instead of duplicating them. So a second try after a fix is safe. Routes are the one exception. They always import fresh, so don't re-run a routes file you've already saved.

Will I lose my service history when I switch?

Not if you export it first. Your past service history lives in Skimmer, so export it before you close the account. PoolBoss imports service history from a CSV file. The visits you export attach to each pool's record, along with your customers and pools. Keep the original export too. It's your record for any customer who asks about work done before the switch. The history keeps filling in once the route is running.

How long does it take to switch from Skimmer to PoolBoss?

For a solo operator or small team, plan on a weekend of setup plus one service cycle of overlap. Cleaning your Skimmer export and entering your customers and pools takes an afternoon for a typical route. Rebuilding routes and assigning techs is another short block. Then you run both systems for about a week before you cancel Skimmer. The cutover itself is quick. The overlap week is what makes it safe, and it doesn't slow you down.

Will there be downtime during the migration?

No, not if you overlap the two systems. Keep Skimmer active while you set up PoolBoss, and run the first week in both. That way your techs always have a working tool in hand. Only cancel the old account after a full cycle logs correctly in the new one. Done this way, a tech never shows up without a route or a customer record.

Can I switch in the middle of the season?

Yes, plenty of operators do, and timing makes it easier. Set up your customers and routes ahead of time. Then run the first week with both systems open as a safety net. If you can, switch during a slower stretch so the learning curve doesn't hit during your busiest weeks. Mid-summer at peak load is the one window to avoid if your schedule gives you a choice.

Does PoolBoss cost less than Skimmer?

Usually, for a growing route. Skimmer charges per serviced location with a monthly minimum, so the bill rises with every account you add. PoolBoss charges a flat rate by pool-count tier, with unlimited users on paid plans, and there's a free plan for very small routes. The more pools you run, the more a flat rate tends to win. Run the numbers at the pool count you expect in a year, not today's. The gap usually grows in PoolBoss's favor as you grow.

Run your pool routes on PoolBoss

Start free today, no card needed. Flat-rate pricing by pool count, every feature on every plan.