Moving your septic business to new software
Move a checked sample first. Set the cutoff for live bookings and decide where old reports and unpaid invoices will stay.

The difficult part of changing software is usually deciding which records belong where. Customer names may import cleanly while service dates, attachments and unpaid invoices still need a plan.
Write down the changeover process before importing the full list. It should say what moves, what remains accessible in the old system and when the team stops entering new work there.
Make an inventory
List the records your business uses, including customers, properties, tanks, future bookings, service plans, open defects, quotes, reports and invoices. Add photos and other attachments rather than assuming they are included in a customer export.
For each group, record the source, the available export and who will check it. Keep original exports unchanged in a separate folder. Do the clean-up in working copies so you can return to the source when a date or address looks wrong.
Pay particular attention to historical documents. A record saying a report once existed is different from the actual issued PDF. Decide how staff will find the document after changeover, even if it stays in an archive outside the new app.
Agree what stays behind
An unpaid invoice needs a clear home. If accounts will continue collecting it through the old system or Xero, don’t recreate it as a new charge in the replacement software. Tell staff where to look before promising a customer an updated balance.
Make the same decision for accepted quotes and deposits. Identify work that’s already agreed but not yet booked. Keep the acceptance and any money received available to the person creating the new booking.
Some historical records can remain in an archive if the office can retrieve them. Test access using a real enquiry: find a property, locate its previous report and explain the last service without asking the person who performed the migration.
Import a difficult sample
Choose a sample that includes awkward records, rather than only the neatest customers. Include a property manager, duplicate-looking names, missing mobile numbers and a site with several systems. Inspect the dates in the source and destination side by side.
Use stable customer, site and system identifiers where possible. Keep the relationships intact: a site belongs to a customer, and the system belongs to the site. Our multiple-system guide explains why merging those records causes trouble later.
Check how repeat work is created. A mistaken last-service date or interval can produce a large number of misleading due visits. Confirm the next dates on the sample before enabling recurrence for the whole business.
Set the live cutoff
Choose a time after which all new bookings go into the new system. Make a named person responsible for changes made during the final export and import. A booking moved by phone while files are being prepared can otherwise disappear between the two lists.
Print or export the next few days’ schedule before the switch. Compare it with the new schedule, including assignments and access notes. Have technicians open their own day and confirm that the records they need are present before leaving the yard.
Give the office a short exception list. Missing records, unmatched customers and incomplete addresses need owners and dates, so the migration doesn’t leave a permanent collection of sticky notes.
Check the first week
Review a small set of jobs through to report and invoice. Check what customers received, which payments were recorded and whether the next service date moved as intended. Fix one root record where possible instead of correcting every future booking separately.
Rangefront Waste supports spreadsheet imports for customers, sites and systems, with a check before saving. The assistant can prepare a proposed import for review, including matched customers and rows that need attention. See importing records for the process and choosing software for the workflow tests to run before committing to a change.



