A Jobber migration starts with relationships. One client may have several properties and contacts, and an approved quote may lead to a recurring job with many visits before it produces an invoice. Moving only the client list leaves that context behind.
Jobber provides useful CSV reports, individual PDFs, and a versioned API, but those routes do not produce one file that recreates an account elsewhere. Some records are reasonable import candidates. Others are better kept in a searchable archive, while forms, automations, schedules, and payment connections need to be rebuilt and tested.
This guide focuses on those Jobber-specific decisions. Use the step-by-step CRM switching guide for the broader project plan. Linked Jobber Help and Developer pages were reviewed August 31, 2026.
Decide what should move before you export
Decide which system will own customer growth, field operations, accounting, and payments. A full migration is optional: SMBcrm now has an official Jobber integration that keeps client and contact details aligned while Jobber runs jobs, visits, schedules, quotes, and invoices. It does not sync Jobber custom fields, notes, or attachments, so test the connection before choosing an export or rebuild.
Use SMBcrm vs Jobber for the direct comparison and the Jobber alternatives guide for a wider shortlist. The migration scope should follow the product decision.
Jobber source-to-target mapping
The table separates extraction from destination handling. “Import candidate” means the source data has a workable export to test, not that SMBcrm accepts the object directly.
| Jobber source | What official documentation supports | Target handling |
|---|---|---|
| Clients | The client export provides CSV or vCard files with contact details, property addresses, tags, and custom-field values. Exact ID headers are not promised. | Destination-specific import test. Retain stable Jobber IDs when present or retrieve them through the API; test duplicates and relationships. |
| Properties | Addresses appear in the client export, and the API exposes relationships. Jobber documents no standalone property export or guaranteed property-ID column. | Destination-specific import test. Inspect clients with several locations and use API IDs when needed. |
| Contacts | Contact information is included with clients, but the export guide does not promise that every additional contact, role, or property association is flattened completely. | Import candidate with a gap check. Sample multi-contact clients before the full load. |
| Tags | Client CSV files include client-level tag assignments. Jobber documents no separate master tag dictionary export. | Import candidate. Recreate only tags that still drive segmentation or workflows. |
| Custom fields | Values can appear in client and work-report exports; the API exposes several object definitions. | Map before import. Rebuild types first, then test values and defaults. |
| Requests | The requests report exports client, service, status, assessment, assignment, linked-work, and request-answer columns. | Archive plus selective import. Preserve the report and recreate active requests as leads, opportunities, or tasks after testing. |
| Quotes | The quotes report exports status, dates, line items, totals, deposits, salesperson, linked jobs, and other columns. Individual quote PDFs can also be downloaded. | Archive plus selective rebuild. Keep historical rows and PDFs; recreate open quotes only after amounts, approvals, signatures, and deposits reconcile. |
| Jobs | One-off and recurring job reports export separately with dates, assignments, line items, billing fields, and linked records, but not recurrence rules. | Archive plus operational rebuild. Recreate active work and recurrence in the field-operations system. |
| Visits and calendar | The visits report exports dates, completion, assignees, duration, and job context. Calendar sync starts with only two past weeks and 20 future weeks and is not real-time. | Manual schedule rebuild. Treat the feed as a convenience, not a backup; test recurrence, owners, time zones, and incomplete work. |
| Invoices | The invoices report exports dates, status, line items, taxes, deposits, discounts, balance, jobs, and custom fields. For multi-address invoices, it uses the earliest-created job address. | Archive and reconcile. Recreate approved open balances only under finance oversight. |
| Payments | The transaction list exports successful payments; Jobber Payments reports add deposits, refunds, fees, and payouts. Saved credentials are not documented as portable. | Archive and reconcile. Never move card data in a spreadsheet. Resolve financial exceptions before cutover. |
| Products and services | The products and services list exports its saved catalog to CSV. Custom line items may exist only on individual work records. | Import candidate or manual rebuild. Verify names, descriptions, prices, costs, tax rules, and unsaved line items. |
| Notes | The API documents notes on several records, but Jobber documents no account-wide UI export. | Custom extraction or archive. Confirm API scope and timestamps, or retain a read-only source archive. |
| Attachments | Files download individually; a note with at least five attachments can produce a per-note ZIP. There is no documented account-wide export. | Archive plus selective import. Verify each file’s parent and readable content. |
| Communications | Jobber’s newer two-way messaging guide says replies and Message Center conversations stay out of the report, while another Jobber page describes some inbound dedicated-number messages appearing. | Verify the live account and archive critical threads. Full thread portability is not established; rebuild templates and reconnect channels. |
| Request forms and checklists | Reports can include responses, but renamed questions can hide earlier answers and duplicate checklist questions can break CSV export. Definitions are not exported. | Archive every current version and completed PDFs; rebuild forms. Test required fields, uploads, signatures, and rules. |
| Automations and templates | Jobber documents request, quote, invoice, and custom automations, but no cross-platform export for their definitions or message templates. | Manual rebuild. Record every trigger, condition, delay, time zone, message, channel, opt-out rule, and stop condition. |
| Users and assignments | Job and visit reports carry assignment data, and the API exposes users and assigned users. There is no documented standalone team-directory export. | Manual user mapping. Create destination users and roles first; map inactive staff without changing historical ownership. |
| Reports | Most Jobber reports export as CSV where the plan and permissions allow. Taxation, Waypoints, Job Follow-ups, and Team Productivity do not. | Archive and rebuild. Save exports and filters; recreate only needed dashboards. |
| Audit history | Requests, quotes, invoices, and timesheets have interactive history, while the unfiltered activity feed shows the most recent 100 notifications. No bulk audit export is documented. | Read-only archive or manual evidence capture. Preserve the source account long enough to answer audit questions. |
An API-assisted extraction can preserve more relationships than UI reports, but it is a software project. Jobber uses OAuth scopes and a versioned GraphQL schema, which must be checked before anyone promises coverage.
Rebuild behavior, not just records
Data portability does not establish workflow parity. For lead intake, test review-first requests, assessment bookings, and automatic job bookings, including uploads and duplicates. Confirm the property, source, owner, acknowledgement, generated records, and assignment. For quotes, test optional items, approvals, signatures, deposits, change requests, follow-up timing, conversion, and the condition that stops reminders.
Next, run one-off and recurring schedules through assignment, rescheduling, reminders, arrival communication, completion, late work, and invoicing. Confirm rescheduling cancels obsolete reminders, completed visits clear late status, and no-future-visit jobs reach the correct action state.
Then test invoice numbering, terms, tax, deposits, overdue follow-up, a failed automatic payment that is not retried, reauthorization, refunds, payouts, visit-complete, job-closed, and invoice-paid review triggers, plus opt-outs. Reconnect each integration under a current owner before deactivating the source user; confirm sync direction and the finance source of truth.
SMBcrm has CRM pipelines, forms, online booking, email and SMS, workflows, invoicing, review management, and integration tools. Those features do not prove equivalence with Jobber’s dispatch, route optimization, recurring-visit logic, technician time, offline field forms, payment processing, or job costing. They also do not replace separate payroll, fleet, or inventory systems without direct evidence. Keep a specialized tool where the exact workflow has not been replaced and verified.
Run a staged cutover
- Inventory and back up. Record counts, workflows, integrations, owners, custom fields, open work, financial exceptions, and retention needs. Save untouched exports and PDFs in a dated, access-controlled folder.
- Clean and map a working copy. Deduplicate clients, standardize dates and phone numbers, retain source IDs, map field types, and define how Jobber statuses translate. Do not delete opt-outs or old financial records merely because they look inactive.
- Pilot the import and rebuild. Use awkward samples: clients with multiple properties, changed quotes, recurring jobs, partial payments, old owners, attachments, and failed workflow paths. Resolve skipped rows before the full load.
- Validate in parallel. Reconcile counts for clients, quotes, jobs, visits, invoices, and payments. Sample old and recent records across owners and statuses. Check dates, amounts, relationships, assignments, roles, attachments, notes, and available audit history. Run each rebuilt workflow once on the expected path and once on a condition that should stop it.
- Capture the final delta and cut over. Freeze edits, identify changes through each report’s date filters, API timestamps, and a manual exception log, then move forms, inboxes, calendars, integrations, and staff activity in order.
- Keep a rollback archive. Document who can reverse each connection, how post-cutover records will be handled, and when the source can be retired.
Do not use cancellation as the archive
Jobber says a canceled account remains accessible only through the subscription term, after which reactivation is required to regain access. Its permanent-closure guidance says closure is final and the information cannot be retrieved.
Keep original exports, PDFs, file downloads, reconciliation reports, mapping decisions, and validation results under your retention and security policy. Accounting records, taxes, payment disputes, legal holds, chemical or service records, privacy obligations, and required retention periods should be reviewed with the appropriate accounting, legal, tax, or compliance professional. This guide is not legal or accounting advice.
If SMBcrm is the destination
SMBcrm onboarding includes group training and 24/7 support on every plan. Professional and Enterprise include four guided sessions; Startup can add them at signup. That support can help configure the destination, but it is not proof that every Jobber object, file, workflow, or payment relationship will transfer. Agree on a written migration scope and acceptance test first.
Eligible new Startup and Professional customers can request a refund of the initial base subscription fee within 60 days; exclusions apply. Use that fit window to validate real records and operating workflows, not to skip the cutover checklist.
Move after the evidence matches
Finish the exports, reconcile the open work, and prove the rebuilt workflows before you retire Jobber. The goal is a traceable move with known exceptions, not a clean import screen.
See plans & pricing or schedule a demo to review your Jobber migration scope.
