Moving from Excel to Car Wash Software: A Controlled Customer Data Migration Guide

Moving from Excel to car wash management software involves more than opening a customer list on a different screen. Registration numbers, telephone numbers and names need to be consistent. Your team also needs to know where to create new records, when to stop editing the old spreadsheet and how to correct a mistake. An unprepared import can carry years of confusion into a new system. A controlled transition makes it easier to find the right customer at vehicle intake and maintain a consistent record afterwards. This guide offers a practical preparation and checking process for small customer lists and spreadsheets used by several employees.

OtoPatron’s current Excel customer import uses three fields: column A contains the vehicle registration, column B the telephone number and column C the customer name. A customer name is required. If the same registration already exists within the company, that row is skipped. New customer records are created as individual customers with a zero opening balance. Do not assume that this import also transfers historical jobs, outstanding debts or loyalty points. The plan below reflects those boundaries. To consider how your wider operation will work after the move, review the intake and tracking process on the car wash management software page.

1. Decide which information belongs in the new system

Start with three separate lists: information for the customer record, financial information requiring its own review, and historical documents that will remain in an archive. Registration, telephone number and name belong in the first list. An outstanding balance, advance payment, free wash entitlement or open job belongs in the second. Details of jobs completed years ago can be considered separately under your business’s record keeping arrangements. This separation prevents the mistaken expectation that one spreadsheet upload will recreate your entire business history. If a source field has no clear destination, do not force it into an unrelated column.

A cell reading “Alex, owes for two washes” combines a name with an account note. Separate the customer name from the amount, date and supporting record. Preserve the original entry before making changes. If an employee later asks where a balance came from, the number in the new system may not explain it. You should also be able to identify the source, when it was reviewed and who approved the decision. A clear preparation record makes the work understandable to someone other than the person performing the import.

2. Preserve an unchanged source copy

Before cleaning the data, make a copy and include a date and version in its name. For example, “customers_source_11_october” and “customers_import_working_01” make the distinction visible. Do not add customers, delete cells or change formatting in the source copy. Keep a brief log of corrections made to the working copy. Several files with identical names on different computers can lead to the wrong version being uploaded. Appoint one owner for the master preparation file and ask colleagues to send corrections to that person.

Also check that the backup opens and contains the expected worksheets. If the workbook has several tabs, prepare one clearly defined customer table for import. Look for hidden rows, filtered records and old period tabs. Do not assume that only the rows currently visible on screen will be processed. Restrict access to customer information to the people who need it for the transition. Avoid sharing screenshots containing real telephone numbers. When testing in a separate environment, use clearly identified test records wherever practical.

3. Prepare the three-column import table

Column position matters in OtoPatron’s current importer. Put the registration in A, the telephone number in B and the customer name in C. Changing a heading does not automatically teach the importer a different order. If the name is in A and the registration is in C, information may reach the wrong fields. Where the source workbook contains ten columns, create a separate sheet with only the verified destination fields. Keep source row numbers and review notes in your preparation workbook rather than treating them as customer data to upload.

The current import implementation does not contain a dedicated header-row mapping or skipping rule. Do not include “Registration, Telephone, Customer name” as though it were a customer. Headings can remain in your review workbook, but verify the final upload file separately. Merged cells, subtotals and section dividers are not customer rows either. Remove entries such as “Trade customers” used to divide groups. Inspecting the first few rows is insufficient: take samples from the middle and end of the table as well.

4. Use a consistent registration format

The same vehicle might appear as “34 ABC 123”, “34ABC123” or a lower-case variation in older files. Decide on your registration format and review entries that may represent the same vehicle. The current import converts registration letters to upper case and trims leading and trailing spaces. Do not assume that every internal space or punctuation variation will be treated as identical. Two entries looking similar on screen is not enough to establish a reliable duplicate check. Different source formats should be examined during preparation.

Be careful with letters resembling digits. Automatically changing an O to a zero or an I to a one can corrupt a valid registration. Check an unclear value against a reliable source rather than completing it by guesswork. Do not force a foreign registration into a domestic format. If one cell contains two registrations, identify the customer information associated with each vehicle before separating them. Changes of registration, vehicle ownership or regular driver require review; they are not a reason to merge records automatically.

5. Preserve telephone numbers as text

Excel may remove a leading zero when it interprets a telephone number as a number. It can also display long values in an unexpected way. Prepare telephone fields as text and check the underlying value as well as the visible cell. A local format and a country-code format may identify the same number, but that similarity does not justify inventing a missing digit. Mark uncertain information for review. Correct telephone records help your team find customers and reduce the risk of contacting the wrong person later.

Several registrations sharing a telephone number are not necessarily duplicates. A family, repair workshop, business owner or fleet contact may look after multiple vehicles. Do not reduce them to one registration. The telephone number helps describe the relationship; it does not replace each vehicle’s history. Commercial status and multiple registrations associated with a telephone number can affect OtoPatron’s loyalty defaults, but importing those vehicles does not automatically pool their points. See the guide to trade customers and multiple-vehicle loyalty rules for examples of those decisions.

6. Separate name cleaning from identity matching

“Sam”, “Mr Sam” and “Sam at the garage” might refer to the same person, but a similar name does not establish that relationship. Removing extra spaces or correcting an obvious spelling error is different from merging customer identities. Businesses serving several customers with the same name need particular care. Review the registration and telephone information together. Where a preferred name or business name has been confirmed, use it consistently. Keep uncertain records on a review list rather than deleting them; vehicle intake can provide an opportunity to verify the details.

Because a customer name is required, rows without one may be skipped. A registration and telephone number alone do not guarantee that a customer record will be created. Complete the missing name or hold that row outside the upload group. Assigning the same temporary label to many customers can make subsequent searches difficult. If temporary records are necessary for your operation, identify who will find and correct them and when. Do not include a skipped row in the count of successfully created customers.

7. Review duplicates before uploading

Check duplicates in two places: within the spreadsheet itself and among registrations already present in the destination system. If the same registration appears in several rows, decide which name and telephone details are correct. The newest row is not automatically the most reliable; it may contain a typing error. Review available dates and confirmed customer information together. When you retain one import row, note why the other entries were excluded. A documented decision makes the reduction in row count understandable rather than appearing to be unexplained data loss.

OtoPatron’s current customer import skips a row when the same registration already exists within the company. It does not use that row to update the existing customer’s telephone number or name. If an existing card needs correction, review and update it separately. Uploading the same file again does not resolve missing names or inconsistent registration formats. Instead of assuming a second attempt has completed the work, investigate why records were skipped. Where duplicates are numerous, verify the matching approach on a small group before preparing the full clean list.

8. Review trade customer status separately

The three-column import creates new records with the individual customer type. A repair workshop, vehicle dealer or fleet appearing in the source file does not automatically bring its classification into the new system. Identify those relationships in a separate preparation list and review the relevant customer settings after the import. Account arrangements, customer type and loyalty preference serve different purposes. A customer might be a private individual who pays regularly, or the contact for a business sending many vehicles. Record the actual relationship rather than relying on a label in an old spreadsheet.

For example, imagine a repair workshop sending eight vehicles under one telephone number. Those vehicles should not become one registration merely because the contact is shared. Their service histories can remain separate while trade status and loyalty decisions are managed appropriately. Current commercial or multiple-registration rules can make loyalty default to off, with an explicit user choice available. An old spreadsheet note reading “free wash” does not automatically create points or an entitlement. Consider customer management and the loyalty programme as related functions with distinct responsibilities.

9. Reconcile account balances independently

A zero opening balance on a newly created customer does not mean an old debt has been paid. Customer list import and account migration are separate tasks. Prepare a review table containing the customer, amount, date, explanation and supporting reference for outstanding items. Have the responsible person verify it before entering balances. Recording the same receivable through both an old job and an opening amount can double count it. Establish one clear treatment for each item, and hold uncertain entries for investigation rather than making the totals appear complete.

Consider a purely hypothetical list of twelve outstanding items: nine are verified, two are inconsistent and one awaits a payment record. Creating the customer cards does not resolve the three pending items. Only the verified group is ready for a decision about the next step. The example separates customer-count checking from financial reconciliation; it does not prescribe an accounting treatment. Review customer account tracking and agree a transition process with the person responsible for your records. Keep the status of pending items visible after the customer import has finished.

10. Select a meaningful pilot group

Testing only clean, ordinary records provides limited assurance. Include several situations in the pilot: a standard customer, two registrations sharing a telephone number, a registration already present in the system, a missing telephone number and a corrected registration format. The purpose is to check the destination fields and understand skipped rows, not simply to see whether an upload button responds. Use a separate test environment where available. If the pilot must be performed in production, use a small group already approved for genuine migration rather than creating unnecessary fictional customer records.

Write down the expected result before uploading. In a hypothetical ten-row group, eight rows might represent new customers, one an existing registration and one a missing customer name. You would expect eight new cards. The existing card should not be assumed to have been updated, and the missing name needs separate attention. If the result differs, do not proceed with the remaining file. Identify the affected row, check the column order and review the formats. Record the pilot findings so the same issue is easier to recognise during the main transition.

11. Reconcile counts rather than trusting one success message

A total row count is not enough. Count headings, blank rows, held records, duplicates within the file, registrations already present and genuinely added customers separately. You should be able to explain where every source row went. In a hypothetical source of two hundred rows, twenty might be duplicates, ten might await missing information and fifteen might already exist in the destination. That leaves one hundred and fifty-five planned new cards. Use your own verified figures; an unexpected count does not by itself prove that data has been lost.

Even matching totals do not replace sample checks. A file uploaded in the wrong column order might create the expected number of cards with incorrect field contents. Select customers outside the pilot and compare their names, telephone numbers and registrations against the source. Include several vehicles from a shared telephone group, entries near the end and names containing special characters. The transition owner should produce a short handover note describing the checks actually performed. Colleagues using the new system should be able to understand that note without having performed the import themselves.

12. Establish one place for new records on transition day

Keeping both the old spreadsheet and the new system open for normal editing can quickly produce conflicting versions of customer information. Set a transition time and appoint a responsible person. Changes before that time belong in the preparation file; new customer records afterwards belong in the new system. Vehicles arriving during the import may require a temporary pending-work list. Review that list afterwards and complete the entries deliberately. Make the recording point clear so the same customer is not added once from the pending list and again directly by another employee.

Where several employees handle vehicle intake, run a short exercise before the transition. Ask each person to find an existing customer by registration, check a telephone number and explain what to do when that customer brings another vehicle. Cover “same telephone, different registration”, “similar name, different person” and “old account note” scenarios. Training should explain decisions as well as button locations. Use the information about workflow management alongside your own allocation of responsibilities. Schedule the transition around the actual demands of vehicle intake rather than assuming every employee can stop work at once.

13. Prepare a correction process

Decide what will happen if an upload produces an incorrect result. Rushing to delete customer cards can affect new transactions already attached to them. First identify the affected group and arrange a controlled review by the responsible person. Record the file used, the import time and the examples checked. Do not assume there is a single button that reverses an entire import. Clarify the recovery method and any support process beforehand. An unchanged source copy becomes particularly valuable when you need to distinguish the original information from later corrections.

A common mistake is repeatedly uploading slightly altered versions of the same file. That can make it difficult to identify which attempt created a particular record. Isolate the cause first: wrong column order, inconsistent registration, missing name or an existing destination card. Once the cause is understood, reconsider only the relevant group. Where customers already have transactions in the new system, take those connections into account before deciding on a correction. Confirm completion through record samples and reconciled counts, not merely through another successful upload message.

14. Monitor data quality during the first week

Finishing the import does not permanently solve customer data quality. Watch how new cards are created during the first week. If employees continue placing debt notes in names, removing telephone prefixes or entering the same registration in different formats, the problems will return. Reviewing a small selection of new cards at the end of each day is a practical starting point. Treat recurring errors as process problems to solve rather than opportunities to blame individuals. Show the correct format through a short example when the same issue appears repeatedly.

Track records that cannot be found, incorrect telephone numbers, pending account reviews and suspected duplicate registrations alongside the customer count. These are transition-quality measures, not sales performance measures. Consider reporting tools when reviewing transaction records and customer information together. By the end of the first week, everyone should understand why the old file remains in the archive and where daily records now belong. Quietly adding customers to the archived workbook recreates two competing versions of the business’s customer list.

15. Agree acceptance criteria with the team

Define success through daily work rather than the number of uploaded files. Can an employee find an existing customer? Can they select the right vehicle when one person has several? Do names and telephone numbers appear correctly? Are unresolved account items still tracked separately? Choose a sample for each criterion. Include an employee who actually handles vehicle intake, rather than leaving every check to the person who performed the import. A second viewpoint can reveal fields that are populated correctly from a technical perspective but are confusing in normal use.

Prioritise outstanding issues. A registration attached to the wrong customer needs prompt investigation. Inconsistent capitalisation may be scheduled for later cleanup if it does not obstruct work. This distinction prevents minor presentation details from distracting you from genuine matching mistakes. Give each unresolved issue an owner, an expected check and a completion status. The goal is to know and resolve important errors in a controlled way, rather than pretending every row is perfect on the first day. Continue customer intake with those known issues clearly communicated.

16. Build a practical transition schedule

Your schedule can follow operational demand. Use one preparation session to protect the source and separate fields, another to review registrations, telephone numbers and duplicates, and the next step to validate pilot results. Perform the main transition when staff have time to check it. The sequence does not prescribe a fixed number of days: data quality and outstanding transactions affect the workload. A busy weekend morning may be unsuitable even if everyone is present. Ensure the person checking the import can step away from normal intake responsibilities long enough to concentrate.

Hold a short handover at the beginning of the next shift. Explain where new customers should be recorded, who handles existing-card corrections and who owns the pending financial list. Show authorised employees how to find the archive. Make clear that a transaction in the new system should not also generate a second customer entry in the old file. At the end of the first week, record completed checks as well as problems. This gives a future colleague a reliable account of which transition steps were actually verified.

17. A usable transition checklist

• An unchanged, dated source copy opens successfully.
• The A registration, B telephone, C customer name order has been verified.
• Headings, subtotals and section dividers have been removed from the upload file.
• Duplicate registrations and missing names have been reviewed.
• Telephone numbers remain text; missing details have not been guessed.
• Trade status, loyalty preferences and account balances have separate review lists.
• Pilot expectations have been compared against the actual customer cards.
• The transition time, responsible person and pending-work process are clear.
• The correction procedure has been agreed before the main import.
• Sample checks are scheduled for the first week.

Frequently asked questions

Does uploading Excel update an existing customer?

The current importer skips a row when the same registration already exists in the company. Do not assume that a new name or telephone value in the spreadsheet has updated that card. List required corrections separately and inspect the relevant records. Comparing a few old and new values after import helps reveal this mistaken expectation early.

Will old debts and loyalty points come across?

The three-column customer import does not transfer them automatically. New cards are created with a zero opening balance. Old receivables, advance payments and free-service entitlements need their own verification. Report customer import, financial reconciliation and loyalty decisions as separate workstreams, each with a responsible person and a documented check.

Should several vehicles belonging to one person be merged?

Do not create one vehicle record simply because names or telephone numbers match. Each registration can have its own service history. Verify the relationship and review trade use and loyalty preferences separately. A shared number does not mean points are automatically pooled. Investigate the scope and impact on past transactions before any consolidation decision.

Must every historical record be migrated before we start?

Your business defines the scope. Moving current customer details carefully and planning verified open items separately may be clearer than forcing every old note into unsuitable fields. Keep archived information retrievable and record new work in one place. Agree beforehand which information will live in the new system and which will remain in the source archive.