Keep the simplicity. Gain the board.
Scheduling, estimates, invoicing, and payments stay as easy as the app your team knows. What you gain is the operational layer above it: a real dispatch board, one price book, and reports the owner reads without asking.
Is it time?
The signs shops leave Housecall Pro on.
The plan caps your people
When users are the tier, the office manager is a pricing decision. Mike should not be a line item. Here he is a person on the record, at $0.
Dispatch outgrew the calendar
Three trucks fit a calendar. Five need a board that shows the overlap and the unassigned job before it ages.
The month is a mystery until it ends
What closed, what is still out, and who ran what should be a read, not a reconstruction.
What comes over
The history is yours. It comes along.
- Customers, contacts, and locations
- Jobs and appointments
- Estimates, invoices, payments, deposits, and outstanding balances
- Recurring work: where their export exposes it, confirmed in validation
- Price books
- Notes, tags, files, and photos
- Team members: every name, no seat count
And what doesn’t: said here, not discovered later.
In-app message and call logs
They come only where the Housecall Pro export exposes them. What we cannot pull, we say so, in the validation report, not after cutover.
Automation rules
Rebuilt deliberately on this side rather than copied, so the behavior you end up with is intentional.
Moving day
Leave without looking back.
The history comes with you, validated line by line. The only thing left behind is the bill.
How migration works
Nine steps. Not “import, then hope.”
01
Export
Pulled through the API or their export. Nothing is retyped by hand.
02
Mapping
Fields land in their Thorbis homes, custom fields and tags included.
03
Staging
A separate copy, away from anything live. The live shop is not the test environment.
04
Validation
A report you read: record counts, balances, unmapped fields. You sign off.
05
Parallel operation
Their system stays up beside the board while you confirm the data matches.
06
Cutover
Live when you approve it. You pick the morning, not a go-live calendar.
07
Reconciliation
Key totals compared against the old system. Money has to match or it waits.
08
Rollback prep
The original export is retained, so the load can re-run if something is wrong.
09
Post-launch review
Flagged records walked through with you. Nothing left in limbo.
No fixed clock is promised. The load is verified, and both systems run in parallel until you call the board the record.
Cutover controls
The switch is kept boring on purpose.
01
A freeze window
A short window where the old system stops changing, so the final delta is clean.
02
Owner sign-off
Nothing cuts over until the validation report has a name on it.
03
An exception list
Anything the importer could not map cleanly is flagged for review, not silently dropped.
04
Rollback notes
What we would do if Monday is wrong, written down before Monday.
Asked before the switch
Straight answers.
Do I lose the simplicity my team likes?
No. The everyday flow (book, estimate, invoice, collect) stays simple, and the heavier operational tools appear only when you turn them on.
Can memberships and recurring work come over?
Where Housecall Pro’s export exposes them, yes, and the validation report confirms exactly what mapped before you approve cutover. We do not guess at what a recurring rule meant.
Is there a per-seat cost for the office?
No. Unlimited people is the model. Only usage (the shop number, texts, AI) meters, at rates posted before anything runs.
Coming from somewhere else?
Start
Bring the history. Leave the mess.
Standard migration is in Core. You do not buy a project to leave the software you already paid for. The dry run is yours to reject.
Coming from Housecall Pro? We’ll extract your records.
Rather talk first? Email the team.