Importing septic business customers and tank spreadsheets
Keep the old record numbers and check what each column means before importing. A clean-looking spreadsheet can still attach the right tank to the wrong customer.

The most expensive import errors often look plausible. A date reads as a valid date but has its month and day swapped. A property manager becomes four separate customers. An interval of three months becomes three days and suddenly every system looks overdue.
Treat the import as a mapping exercise, with a saved source and a checked sample. The file opening without an error only proves that it can be read.
Preserve the starting point
Export the data from the current system and save an untouched copy with the export date. Work on a separate file. Keep the customer, site and tank numbers from the old system, even if you intend to use different numbers later.
Those identifiers let you reconcile results and distinguish records with similar names. They also help a repeated import update the intended record instead of creating another copy. Before choosing a field as an identifier, check that it stays stable and is unique at the right level.
Record what the export includes. Customer contact data, issued reports, photos and job history may arrive in separate files or formats. Don’t assume importing the customer sheet transfers every attachment and historical visit too. Make a list of anything that needs a separate archive or migration step.
Map the relationships
Decide what each row represents: a customer, a property or an individual system. A sheet with one row per tank may repeat the customer’s contact details several times. That doesn’t mean it contains several customers.
Give each property an unambiguous owner or account reference, and each system a property reference. Check the awkward cases deliberately: a customer with several sites, two systems at one address and two people sharing a surname.
Separate billing addresses from service addresses before mapping. Keep access instructions with the property and equipment details with the system. Our customer, site and tank record guide explains the structure you’re trying to create.
Check dates and units
Write down the meaning of each date column. Last pumped, last serviced, next due and invoice date are different facts. A column simply labelled date needs clarification before it can drive future bookings.
Use an unambiguous format and inspect the imported result, including values stored internally as spreadsheet date numbers. Check blank cells and text such as unknown. A missing date shouldn’t silently become today’s date.
Confirm the unit for every interval and quantity. Months, years and days aren’t interchangeable, and a rounded conversion can alter the intended maintenance cycle. If a source has both an interval and an explicit next due date, decide which should govern and verify the result after import.
Keep phone numbers as text so leading zeroes survive. Check postcodes and external reference numbers too. Spreadsheets sometimes turn identifiers into numbers or scientific notation long before you reach the importer.
Import a deliberately awkward sample
Choose a small sample containing normal rows and difficult cases. Include duplicate-looking names, multi-site accounts, a missing contact and several date formats you actually use. A sample of only tidy rows won’t reveal the mapping problems.
Use the import preview or dry-run check. Compare its proposed customer, site and system counts with the source. Read individual proposed records, not just the green success count.
After the sample import, open the records and follow their relationships. Check map points, contact routing and calculated due dates. Have an office person who knows those customers review them. They are more likely to notice that an apparently correct address belongs to the wrong account.
Control the full transfer
Choose when the old system stops being edited and how any later changes will be captured. Without that cutoff, a correct import can already be stale when staff start using it.
Import in a small enough batch to inspect and recover. Reconcile counts, review rejected rows and keep a record of what was imported when. Don’t retry the whole file until you understand how the importer matches existing records.
Before enabling recurring visits or messages, check the dates and contact details those processes will use. A mapping error can become hundreds of incorrect drafts or reminders if automation starts immediately.
Importing into Rangefront Waste
Rangefront Waste can import customers, sites and systems, with a preview before saving. The assistant also accepts CSV and Excel files and shows proposed records for confirmation. Imports can be reviewed and undone; check what a rollback will affect before relying on it as a substitute for a source backup.
File limits and matching behaviour can differ between import paths, so follow the current import documentation and assistant guide. Test your actual export before the office commits to a switch-over date.



