Make a backup and choose a cutover date
Save an unchanged copy of the spreadsheet before cleaning or importing anything. Record which version is the source for the move and who can edit it. If two people keep changing different copies, a successful import can still leave the new system out of date. Choose when the team will stop adding new work to the old sheet and start using the new records.
A customer migration is not automatically a migration of job history, accepted quotes or unpaid invoices. List what you need to carry over and verify which record types your import process supports. Preserve historical documents separately when they are not included. Do not assume a notes column recreates the original transactions or their payment status.
Separate the customer, property and visit
A homeowner with one address is straightforward; a property manager responsible for several storefronts is not. Identify who approves work, who pays and where the cleaning happens. Keep billing contacts distinct from site access contacts. Otherwise the next person may send an invoice to a store employee who cannot authorize payment or schedule every property under one address.
| Information | What to verify |
|---|---|
| Customer | Name or company, billing contact and existing reference |
| Service address | Street, unit, city and postal code for each property |
| Contact details | Email and phone, with the right person attached |
| Visit arrangement | Scope, frequency, next agreed date and expected duration |
| Commercial access | Opening hours, access contact and appointment restrictions |
| Outstanding work | Open quotes, jobs and balances checked separately |
These are preparation fields, not a promise that every importer has columns with these names. Download or inspect the destination template and map only supported fields. Where a relationship cannot be represented safely in a single row, plan a separate review or manual setup rather than hiding it in an ambiguous cell.
Clean duplicates without losing distinct properties
Look for repeated emails, phone numbers and spelling variants, but do not merge records just because a name matches. Two locations can share a billing contact. One household can also have several people who communicate with you. Keep the source reference while reviewing possible duplicates so you can trace a decision back to the original sheet.
- Remove leading or trailing spaces from contact fields.
- Keep phone numbers and postal codes as text so formatting is not lost.
- Use separate fields for distinct addresses rather than one long comma-separated cell.
- Check missing contact details against your own records instead of guessing.
- Keep opt-outs and contact preferences available for review; importing a customer does not create permission to market to them.
Avoid storing door codes or other sensitive access details in public-facing service descriptions. Transfer only information needed for the work and place it in the appropriate private record. A clean import is about accurate relationships as much as tidy spelling. If you are unsure which contact owns a property, resolve that before scheduling the next visit.
Test a small, representative batch
Pick a handful of records covering the shapes in your actual list: a single home, a commercial contact, a customer with more than one property, and a record with missing optional information. Do not start with only the easiest rows. Keep the test quiet: review any workflows that might send messages and avoid using the import as a reason to contact customers unexpectedly.
Map columns using the destination’s template or preview. Check how blank fields, phone formats and duplicate matches are handled. After importing, open each test record and compare the displayed name, contact, address and notes with the original. If the importer offers undo, understand its scope before assuming it reverses every later action or external message.
Write down the mapping that worked. If a field lands in the wrong place, fix the source or mapping and review the test records before retrying. Repeatedly uploading the same sheet without checking the previous result can multiply duplicates instead of repairing them.
Set up repeat visits after the customer records are correct
An imported customer is not necessarily a scheduled job. Review the next agreed date, frequency, scope, expected duration and assigned worker before setting up repeat work. A monthly storefront visit and an occasional residential clean should not inherit the same schedule simply because they appeared next to each other in the spreadsheet.
Use the recurring window-cleaning guide to plan the ongoing visits after the move. The window-cleaning pricing guide helps separate glass, screens, tracks and extras when the old sheet contains only a single amount. Preserve existing agreements; a migration is not permission to change the customer’s price or scope.
Reconcile unpaid balances against the original invoices separately from scheduling. Record whether a payment is already received or still processing. Do not recreate an outstanding amount as a new invoice until you understand how the destination handles historical records, invoice references and accounting exports.
Verify the full import and retire the duplicate workflow
After the test is correct, process the remaining records using the reviewed mapping. Compare the number of source rows with records created, skipped or matched; those totals may differ because several addresses belong to one customer. Investigate unexplained differences instead of expecting a simple row count to prove the move succeeded.
OmniOps for window cleaning provides a shared customer, scheduling and invoicing workflow. Review its import and customer features, then test the records you actually need. Compare pricing and trial terms before switching the whole team. A spreadsheet import does not remove the need to check property relationships, open work and communication preferences.
At cutover, tell the team where to enter new work and retain the old file as a read-only reference. Review the first scheduled day and first invoices carefully. Keep a short list of records needing manual attention, with an owner for each. This makes the change manageable without leaving two competing calendars in daily use.