Switching pool service software: a 30 day migration plan that does not break your route

The myth of cutover weekend

The mental model most operators carry is that switching software means a Sunday night where you export from the old system, import to the new system, hope nothing breaks, and start Monday morning with crossed fingers. That model exists because it is what enterprise software migrations looked like in 2008.

Modern pool service software does not work that way. The right pattern is parallel running: keep the old system live for billing and routing while you bring the new system up to speed in the background. Customers do not notice. Routes do not disrupt. The operator gets to validate everything before pulling the trigger.

Week 1: Import customer records and accounts receivable

Day 1: Export your full customer list from the old system. Most platforms (Skimmer, Pool Brain, Jobber, Housecall Pro, Pool Office Manager) export to CSV from the customer page. If yours does not, contact support — every reputable platform offers customer export.

Day 2-3: Import to the new platform. The new platform should accept CSV directly. If it does not, that is a red flag.

Day 4-5: Spot check 20 random customers. Are addresses correct? Are notes preserved? Are recurring service amounts correct?

Day 6-7: Pull your accounts receivable report. Match it against the imported records. Anyone with an outstanding balance gets manually flagged in the new system so you can collect against it during the transition.

Week 2: Import service history and chemistry

Service history imports are where most migrations stall. The old system has 3 to 5 years of visits, chemical readings, equipment notes, and photos. The export is messy. The import is messier.

The right approach is to import the most recent 12 months of service history (which covers seasonal patterns and recent equipment issues) and archive the rest as a CSV download for reference. Customers do not need their 2019 chemistry log in the live system. Operators rarely look back further than 12 months in active workflow.

Equipment notes get imported into the customer record as long form text. Pool dimensions, equipment models, install dates, warranty info — all in one place where techs can see it on the truck.

Week 3: Switch routes one tech at a time

This is the week most operators dread and the week that actually goes smoothly. The trick is not to switch the entire team at once.

Day 1: Pick your most experienced tech. Brief them: "We are testing new software. Same route, same customers, same schedule. The app on your phone changes. Tell me what works and what doesn't."

Day 2-3: That tech runs their route on the new system. They use the old system as a backup for any visit that the new system can't handle.

Day 4-5: Add a second tech. Now you have two techs running on the new system, two on the old.

Day 6-7: Add the rest of the team. Daily standup at end of day to capture issues. By Friday everyone is on the new system for routing.

“Tech adoption is the part of the migration most operators fear. Done one tech at a time over a week, it is the easiest part.”

Week 4: Switch billing and cancel the old contract

The last week is where the financial side switches over. By this point routes are running on the new system and the old system is mostly idle. Now you flip billing.

Day 1-2: Run a test invoice batch from the new system to a small group of customers (10 to 20 accounts you trust). Verify the invoices look right, payment processing works, and customers can pay through the new portal.

Day 3-4: Run the full month's billing through the new system. The old system stays available as backup but is no longer the source of truth.

Day 5: Reconcile against the previous month's billing from the old system. Numbers should match within a small rounding margin.

Day 6-7: Cancel the old contract. Most software vendors require 30 day written notice — file it now if you have not already.

What happens to data you leave behind

Most migrations leave behind some historical data. That is fine. Pull a full export of everything (customers, routes, history, billing, equipment) from the old system as a backup CSV before you cancel. Save it to cloud storage. You almost certainly will never need it. But for the rare audit, dispute, or warranty claim, having the historical record is worth the 20 minutes it takes to export.

The migration features that matter

When evaluating new pool service software for switchability, the questions to ask are specific and short.

• Do you offer a free trial? At least 30 days?
• Do you import customer records from CSV out of the box?
• Do you import service history and chemistry readings?
• Do you support running parallel with my existing software during the trial?
• How do I export my data if I leave?
• What does the support look like during the first 30 days?

How Pooly handles migration

Pooly comes with a 30 day free trial designed exactly for the parallel run model above. The trial includes data import support: customer records, route assignments, service history, and chemical readings come over from your existing platform. Run both systems through the trial. At the end of 30 days, if Pooly works for your business, cancel the old platform and you are fully running on Pooly. No cutover weekend. No double billing.

The founders sit on every migration personally during beta. If something does not import cleanly, you talk to the people who built the import tooling, not a support queue.