HELP
Migrating to Conduit

Migrating from Jobber

Step-by-step guide for moving your data from Jobber into Conduit. OAuth flow, what transfers, what to verify after.

Updated May 4, 2026 · 3 min read · For Owner + Prospect

Jobber is one of the largest contractor SaaS platforms; we see a lot of migrations from it. Conduit pulls 4 data types from Jobber: customers, jobs, invoices, and quotes. Authentication uses OAuth (no API key to copy). You log into Jobber in a popup window from Conduit, authorize access, and the data starts flowing.

This guide walks the full migration: connecting via OAuth, what transfers, common gotchas, and what to verify after.

01Connect to Jobber via OAuth

You don’t need to copy or paste anything. The OAuth handoff happens in a popup.

  1. Open Conduit’s migration wizard at Settings → Import Data → Import from Another Tool.
  2. Click the Jobber tile.
  3. Click the orange Connect to Jobber button. A new window opens to jobber.com.
  4. Sign in to Jobber with your existing credentials.
  5. Jobber asks: “Do you want to grant Conduit access to your account?” Click Authorize.
  6. The popup closes. Conduit’s wizard advances to Pull Data.
SCREENSHOT · migration/jobber/01-oauth.png
OAuth handoff. Conduit never sees your Jobber password; Jobber issues a token directly.

02What transfers

Conduit pulls 4 data types from Jobber:

  1. Customers (clients). Names, emails, phones, addresses, type (residential/commercial), tags, notes.
  2. Jobs (visits). Job title, scheduled date and time, status, assigned technician, line items.
  3. Invoices. Line items, totals, paid/unpaid status, customer link, issue date, due date.
  4. Quotes. Same shape as invoices, imported as Conduit bids.

Each record gets a jobber_external_id so re-importing updates rather than duplicates.

03What doesn’t transfer

Some Jobber features don’t have a Conduit equivalent or aren’t on the OAuth scope:

  • Properties. Jobber’s “Property” model (multiple addresses per client) flattens. The primary property becomes the customer’s address; secondary properties don’t transfer.
  • Visits with multiple line items per visit. Each visit becomes one Conduit job; complex visit/job relationships flatten.
  • Recurring schedules. A one-time job lands in Conduit, not a recurring template. Recreate the recurring schedule in Conduit if you need it.
  • Job costing data. Jobber has limited job-cost tracking; what transfers is the line-item total only. Detailed cost tracking starts fresh in Conduit.
  • Photos and notes attached to visits. Job notes transfer; photos attached to specific visits don’t bulk-import.
  • Time entries from your team. Conduit’s time tracking starts fresh.

04After import

Once the wizard finishes, verify before going live:

  1. Spot-check 5-10 customers. Confirm names, emails, addresses are correct. Watch for any with the secondary-property issue (where the primary property’s address is wrong because they had multiple).
  2. Verify totals. Check a customer’s lifetime spend in Conduit against Jobber’s records. Small differences expected (date ranges, tax handling).
  3. Connect Stripe. Conduit handles payments through your own Stripe Connect account; Jobber’s Stripe relationship doesn’t carry over. Connect Stripe in Settings → Payments.
  4. Invite your team. Technicians need Conduit accounts; team membership doesn’t carry over.
  5. Update outgoing notifications. If you send invoice reminders by SMS or email, the “from” sender changes once you move to Conduit. Worth a one-line heads-up to active customers.

Your Jobber account is untouched throughout. Run them in parallel for a few days if you want to verify before deactivating the Jobber subscription.

Was this guide helpful?