Moving from Jobber to a CRM: Checklist

Moving from Jobber to a CRM: Migration Checklist for Field Service Teams

Moving from Jobber to a CRM is not just a CSV import. Field service teams may be moving client records, properties, tags, custom fields, quotes, invoices, appointments, jobs, notes, reminders, payment history, and active follow-up processes. If those pieces are not mapped before cutover, the new CRM starts with missing context.

Use this checklist before switching. It assumes Jobber is the current system and a CRM such as Tregovia is being evaluated for client records, appointments, billing, reminders, online booking, estimates, and follow-up.

Step 1: Decide Why You Are Leaving

Write the reason in one sentence:

• "We need simpler CRM and billing around appointment-based work."
• "We are paying for field-service features we do not use."
• "We need client records, appointments, invoices, and reminders in one place."
• "We need a different data or operating model."

Do not migrate because a comparison page says one product is cheaper. Start with the workflow that is failing. For the cost side, read the Jobber total cost model.

Step 2: Export What Jobber Allows

Jobber's help center says client lists can be exported as CSV or vCard on select plans. It also says CSV export handles up to 1,500 rows per file, and larger exports are sent as multiple files. Admin users can import/export clients, while some client data can be exported by team members with report permissions.

Use the official Jobber client export help article as the current source before planning the migration.

Create a migration folder with:

• Client export
• Property/address export, if available
• Tags and custom fields
• Products/services list
• Quotes or estimates
• Jobs or appointments
• Invoices and balances
• Payment records or reports
• Active reminders or follow-up lists
• Attachments or photos, if needed
• Current settings screenshots

Some of these may not be one-click exports. That is why the dry run matters.

Why "In Progress" Jobs Are The Riskiest Migration Item

Every category listed in the export folder above is easier to migrate than the one thing most migration guides gloss over: work that is actively underway at the moment of cutover. A completed job and its invoice are a static historical record; a job that is scheduled, partially quoted, or mid-dispute is a live process with state that doesn't export cleanly into a spreadsheet row.

This matters because the riskiest migration failures are rarely about lost history, they're about a job in progress landing in neither system cleanly. A quote sent to a customer last week, awaiting their decision, needs someone to actively track whether it lives in the old system, the new one, or both during the transition, or it risks being followed up twice or not at all. The safest practice is to explicitly freeze new work in the old system a few days before cutover, let everything already scheduled reach a natural completion point where possible, and treat any genuinely open in-progress items as a short, manually tracked list rather than assuming the export process will capture their current state correctly.

Step 3: Map Fields Before Import

Use a mapping table:

Jobber field	New CRM field	Keep, merge, or drop	Notes
Client name	Client name	Keep	Check split first/last names
Property address	Address/custom field	Keep	Some clients may have multiple properties
Tags	Tags/custom fields	Keep selectively	Remove old campaign tags
Custom field	Custom field	Review	Drop fields nobody uses
Open invoice	Invoice/balance	Keep	Reconcile before import
Job note	Note/task	Review	Sensitive notes need access control

Do not import every stale field just because it exists. Migration is a chance to remove dead tags, duplicate clients, old prospects, and outdated notes.

Step 4: Test A Small Sample

Choose 20 records:

• Five active customers
• Five customers with invoices
• Five customers with complex addresses or properties
• Five old customers you may keep for history

Import the sample, then ask staff to perform real tasks: find a client, book a service, create an invoice, review notes, send a reminder, and look up a past balance. If staff cannot do those tasks in the test system, do not run the full import yet.

Step 5: Rebuild Workflow, Not Just Data

A CRM migration fails when the team imports records but forgets operating rules:

• Who owns new enquiries?
• How are quotes followed up?
• When are invoices sent?
• What triggers a payment reminder?
• How are cancellations and no-shows recorded?
• Which staff roles can edit billing records?
• What happens to jobs already in progress?

For Tregovia, keep the public claim conservative: it can be evaluated as the receiving CRM for these workflows, but every Jobber export still needs mapping, cleanup, sample testing, and staff acceptance.

Use acceptance tests such as:

• Find a client with multiple properties
• Create an appointment or job-equivalent workflow
• Convert an estimate into billing work where applicable
• Check an open invoice balance
• Send or prepare a reminder
• Review staff permissions
• Export a record after import

Step 6: Choose Cutover Timing

Avoid switching during:

• Month-end billing
• Payroll week
• Peak season
• A heavy campaign
• A period with many open quotes
• A week when the owner is unavailable

Run the final export, freeze edits in the old system, import into the new CRM, test the critical workflow, then redirect staff to the new source of truth. Keep read-only access or backups long enough to resolve disputes and missing details.

Step 7: Post-Migration Checks

Within the first week, check:

• Client count
• Duplicate rate
• Future appointments
• Open invoices
• Paid invoices marked correctly
• Missing phone/email records
• Reminder rules
• Booking links
• Staff permissions
• Reports the owner uses weekly

Use Tregovia pricing and CRM alternatives only after the migration scope is clear. A cheaper subscription is not a cheaper switch if staff spend weeks cleaning up missed data.

Jobber Migration Questions

What should be exported from Jobber before switching?

Export clients first, then identify how to preserve properties, custom fields, tags, invoices, jobs, appointments, quotes, notes, and active workflow state where export options are available.

Can Jobber client data be exported?

Jobber's help center says client lists can be exported as CSV or vCard on select plans, and CSV exports are handled in files of up to 1,500 rows. Verify current export access before migrating.

What should be tested before cutover?

Test a sample import for clients, contact details, addresses, custom fields, appointment history, invoice balances, and the workflow staff use every day.

Where does Tregovia fit?

Tregovia can be evaluated as the receiving CRM, but every migration still needs export review, field mapping, duplicate cleanup, test import, and staff acceptance testing.

How should Jobber be evaluated?

Use Jobber as a current-state benchmark, not as a fixed target. Check its current pricing, data terms, export process, and workflow limits directly on the vendor site before comparing it with Tregovia or any CRM.

Final Cutover Rule

Moving from Jobber to a CRM should start with a dry run, not a final import. Export what you can, map fields carefully, test real staff tasks, and switch only when the new workflow is proven.