Keep the books. Move the work.
You do not have to leave QuickBooks to run the field in Thorbis. The books stay where the accountant likes them; scheduling, dispatch, estimates, invoicing, and collecting move to a system built for the truck.
Is it time?
The signs shops leave QuickBooks on.
Jobs are invoices with a memo field
QuickBooks can bill the work; it cannot run the day. When dispatch lives in a spreadsheet beside the books, the field side needs its own record.
The techs cannot touch it
The crew should close jobs from the truck (photos, notes, payment) without anyone re-entering the day into the accounting file at night.
The double entry is the job
Every job typed once for the schedule and once for the invoice is an error waiting for month-end. One record, entered once.
What comes over
The history is yours. It comes along.
- Customers, contacts, and locations
- Items: landing as your price book
- Estimates and invoices
- Outstanding balances, so the field record collects accurately
- Notes
- Team members
And what doesn’t: said here, not discovered later.
The books themselves
Chart of accounts, ledgers, and accounting history stay in QuickBooks, on purpose. Issued invoices post one way to QuickBooks after a readable dry run; the books stay in one place.
Payroll and tax filings
They remain in your existing accounting workflow. Thorbis payroll is Next on the roadmap and is never turned on for you.
Itemized transaction history
Old line-level transactions are reviewed rather than force-imported; balances transfer so the field side is accurate from day one.
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 have to stop using QuickBooks?
No. The recommended setup keeps QuickBooks as the books while Thorbis runs the field. Issued invoices post one way after a dry run you can read. We will not sell a replacement until Money is the product.
What actually comes over?
The customer list, items as your price book, estimates, invoices, and outstanding balances. Ledgers and the chart of accounts stay in QuickBooks, and the validation report shows exactly what mapped.
Can the crew work from their phones?
Yes. The field app carries the job, the address, the notes, and the book, and collects on site. That is the point of moving the work out of the accounting file.
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 a suite? We’ll extract your records.
Rather talk first? Email the team.