Implementation & migration
Move the records your team uses.
Bring one awkward enquiry and one export from the system you use today. We map how the office works, preview the records and agree who signs off before the team changes over.
Discuss your rolloutFirst morning in the office
One customer, two contacts.
- Customer
- Example Facilities
- Site contact
- Facilities coordinator
- Shared mobile
- Owner reviews the match
- First visit
- Linked to the right profile
Start with the person doing the work.
The owner takes us through a job from the first call to approval. We research your public website, services, area and working style, then agree the questions the call desk asks, the exceptions that go to a person and the rate sources the owner accepts.
Bring a real export
Keep an untouched copy in your existing system. Work on a separately authorised contact CSV and agree which office is responsible for the handover.
Map a sample
Map name or company, contact person, email, phone and address. A contact needs a name and a usable phone or email. Review each correction in the preview.
Check the first morning
An office lead checks the saved contacts, explicitly links the right job and confirms which diary and accounting ledger remain authoritative.
See what happened to every row.
This illustrative four-row contact file contains one new customer, one exact duplicate, one shared household phone and one incomplete entry. The owner can keep two people separate even when they share a number.
| Source row | Preview result | Owner action |
|---|---|---|
| 01 · Harbour Maintenance | Ready | Save the contact. |
| 02 · Harbour Maintenance | Exact duplicate | Keep the existing record. |
| 03 · Alex and Sam share a phone | Review | Confirm a separate person or leave the row out. |
| 04 · Name only | Invalid | Add a reachable phone or email. |
After saving the ready row alone, the receipt should reconcile to one saved, one duplicate, one held and one invalid. Verify those counts before processing the next batch.
Keep the original history intact.
| Source | How it moves |
|---|---|
| Customer contacts | A reviewed CSV creates business-scoped profiles. An explicit owner link connects an existing job to its customer. |
| Calendar events | Preview an .ics export, review the time zone and overlaps, and confirm the events you want. Agree which diary owns future changes. |
| Invoices, payments and attachments | A contact import carries no financial history, job notes, balances, permissions or files. Keep the original system and agree any further export or connector separately. |
Keep the right customer when details change.
Two property managers can share a switchboard and manage different sites. When your export includes a stable customer ID, give its source account a name and stage the file. The office chooses which local profile belongs to each ID. A matching phone or email brings up possible matches for review.
On the next export the same ID finds the same profile, even if its phone and email have changed. Choose individual fields to update, such as the new email. The review records who made the decision. If it needs correcting, undo the latest change first. Previous job addresses, property contacts, accepted quotes and invoice drafts keep their original records.
Exports without a reliable ID use the contact preview above. Start with one representative file and check the ID against the original software before running the full batch.
Agree the handover in writing.
Nominate an owner and an office lead. List which records move, which checks each person performs, how the team reports discrepancies and what stays open in the previous system. For larger teams, agree staff access, service areas and business continuity before switching your number or diary.
Prepare a rollout enquiry