You already know the job. This is where each job lives in RouteSplash, so you are not hunting for a button that your old software put somewhere else.
Switching software is not really a data problem - it is a muscle-memory problem. The import takes an afternoon; the first week is spent looking for things. Below is the same work you already do, with where it lives now and the detail that trips people up.
| What your old program may have called it | What it is in RouteSplash |
|---|---|
| Service location / property / account | Customer, with one or more bodies of water (pool, spa) under it |
| Job / visit / work order | Service stop on a route, or a Repair job for non-routine work |
| Route / run / dispatch board | Routes in the portal, Day in the app |
| Service plan / schedule / contract | Recurring service rule |
| Service report / job report | Service report (photos + notes + optional signature) |
| Water test / chemical log | Chemical log against a body of water |
| Timesheet / clock | Time clock on the Day tab |
| Truck stock / inventory | Truck weigh-in and Truck Weights |
Each one lists where it is now, and the detail most people miss on day one.
You may know it as: Called the day sheet, route sheet, dispatch list or run sheet. Often a printed list with handwritten order.
Watch out: A route is tied to a day of the week. If a customer needs a Tuesday visit, they must be on a Tuesday route - that is what makes the Day tab correct.
You may know it as: Called a service plan, schedule, service level, contract or frequency.
Watch out: Pausing keeps the pool in your billing pool count. Disabling the customer is the action that stops billing and frees the pool slot.
You may know it as: Called a chemical log, water test, reading, or dosage calculator. Many programs leave the math to you.
Watch out: Readings attach to a body of water, not just a customer. A property with a pool and a spa is one customer with two pools.
You may know it as: Called invoicing, billing run, statements, or recurring charges.
Watch out: Chemical billing starts from the day you switch it on. It never back-bills the months before that.
You may know it as: Called accounting sync, export, or "my bookkeeper does it".
Watch out: Desktop is file-based. If your bookkeeper needs a live two-way feed, that is QuickBooks Online only.
You may know it as: Called a service report, job report, visit note or work order.
Watch out: Customer emails and texts are off by default. Turn on the master switch and only the message types you want under Portal → Settings / Customer Texts.
You may know it as: Called a work order, job, ticket, or callback.
Watch out: A repair is not a service stop. Repairs are their own queue, so a broken pump does not disturb the weekly route.
You may know it as: Called a time clock, timesheet, payroll export, or tech scorecard.
Watch out: An open shift with no clock-out is listed, never guessed. Close it before you run payroll.
You may know it as: Called inventory, stock, or "ask the tech".
Watch out: Entering 0 for an empty jug is real usage. A blank is not the same thing.
You may know it as: Called merchant processing, card on file, or autopay.
Watch out: Saved cards do not move between processors. If you change processors, customers re-enrol once.
You may know it as: Called import, data migration, or a CSV export.
Watch out: Preview first. The import shows you exactly which rows are duplicates before anything is written.
Do not switch a whole company on a Monday morning. Import a few routes, run them beside the old program for a week, and let the techs complain early. Once the day sheet, the chemical log and one invoice look right, move the rest.
The full data walkthrough - what comes across, what does not, and how the preview works - is on the switching page. If you are weighing us against a specific product, the comparison pages cover pricing model and feature differences.
On a route. Each customer is attached to a route that runs on a day of the week, and a recurring service rule generates the stops. The Day tab shows today's route in driving order.
Yes. Import the spreadsheet as customers, then put each customer on a route. The Day tab lists the stops in driving order and Route Optimization can reorder them to cut miles.
It does not import. Your customer list, pools and equipment come across; readings start fresh in RouteSplash. Keep the old program read-only for a season if you need to look back.
For the customer portal, yes - they get a portal link and an access code. Homeowner portal logins do not carry over from another program.
Not automatically. Saved cards live with the payment processor and do not transfer between programs, so customers re-enter a card once through your Stripe or Square account.
A small company can import and run its first route the same day. For a larger book, import selected routes first, run them for a week alongside the old program, then move the rest.
Import a copy of your customer list, run a couple of routes beside your current program, and see whether the day sheet and the chemical log feel right. 30 days, every feature, up to 50 active pools.
Start free trial