Intent boundary: This guide answers how to switch systems safely. It does not rank products or replace a vendor-specific implementation statement of work.
complete jobs and collect payments during the changeover
The process succeeds only when the team can explain the result, recover from exceptions, and retain evidence.
The control sequence
Name the systems of record
Decide where customer identity, accounting truth, scheduling, price book, payroll, files, and communication history live before and after cutover.
Freeze the data inventory
Count customers, properties, open work, recurring jobs, agreements, equipment, estimates, invoices, payments, attachments, custom fields, users, and integrations.
Export before cleaning
Save untouched source exports, field definitions, reports, attachments, and screenshots. Work only from copies so the original evidence remains recoverable.
Map and normalize
Resolve duplicates, required fields, customer-versus-property relationships, tax treatment, service codes, price-book structure, status values, and staff ownership.
Run a reversible test batch
Import a small representative set that includes multi-property customers, open balances, recurring work, special taxes, notes, equipment, and archived records.
Reconcile the result
Compare counts and control totals, inspect exceptions, verify attachments and history, and obtain accounting approval before the full import.
Cut over by workflow
Choose a precise stop-entry time, migration window, open-job rule, payment rule, rollback trigger, and named decision owner.
Preserve the old evidence
Keep compliant read-only access or exports for the required retention period and document how staff can retrieve historical records.
The minimum migration control sheet
| Data group | Control total | Acceptance test | Owner |
|---|---|---|---|
| Customers + properties | Records and unique contacts | Addresses, relationships, duplicates | Operations |
| Open jobs + recurring work | Jobs by status and next visit | Schedule, assignment, recurrence | Dispatch |
| Price book | Active items and categories | Price, tax, cost, duration | Operations + finance |
| Invoices + payments | Open balance and aging total | Document, status, customer balance | Finance |
| Files + equipment history | Attachment and asset counts | Retrieve from customer/property | Service manager |
Failure modes to expose
- Starting the import before choosing the system of record
- Using production as the first test batch
- Assuming notes, files, equipment, and custom fields migrate because customers do
- Changing accounting and operational systems on the same unowned date
- Canceling source access before retention and reconciliation are complete
Worksheet questions
- 01
Who can stop the cutover, and what exact condition triggers rollback?
- 02
Which records must stay editable in the old system during transition?
- 03
How will open estimates, deposits, partial invoices, credits, and refunds be handled?
- 04
Which field mappings need finance, dispatch, or service-manager approval?
- 05
What export will prove the new record counts and balances?
- 06
How long must the old system remain accessible for tax, legal, warranty, or customer-service needs?