DATA MIGRATION
Bring your important records with you.
A good data migration protects the customer history and work your business relies on. It starts with a clear plan for what will move and how it will be checked.
Something to build on · 01
Inventory the records
Identify contacts, service addresses, equipment, past appointments, active jobs, unpaid invoices, and notes. Record where each dataset lives and whether it can be exported. Check the contract and privacy rules before moving personal data.
Something to build on · 02
Clean before importing
Old records often include duplicate names, missing apartment numbers, shared phone numbers, and free-text fields. Flag uncertain records instead of making silent guesses. Keep a source copy and migration log.
Something to build on · 03
Map the relationships
A customer may have several service properties, and each property may have several assets. Preserve those links. A flat import that merges equipment from different sites can create expensive field mistakes.
Something to build on · 04
Reconcile and sign off
Count records before and after. Spot-check representative accounts, open balances, appointments and long notes. Train staff to report missing history, and plan a controlled process for changes made during cutover.
Example to try: A customer has three homes and five HVAC units. The migration is correct only if each unit remains linked to the right property and service history.
Something to build on · 05
A practical checklist
- Count source and imported records by customer, property and job type.
- Preserve relationships and historical IDs needed for audit or service lookup.
- Flag uncertain merges or missing data for human review.
- Keep encrypted source backups and a verified rollback or correction path.
Good questions
What else would
you like to know?
Can ServiceCanopy move all our history?
That depends on data availability, import support, quality and scope; no universal guarantee is made.
What about photos and attachments?
Binary files and external references need a separate migration plan and permission checks.
Is a CSV enough?
CSV works for many tabular records, but relationships, files, and statuses may require additional mapping or tooling.