Migrate from Jobber to HighLevel

Jobber clients who are individuals map directly to HighLevel contacts. Email, phone, address, and name fields transfer 1:1. Clients who represent businesses map to both Contact and Company in HighLevel — we create both records and link them via the contact's company field.

Jobber clients with a company name or business flag create a HighLevel Company record. The Company holds business-level data (domain, industry, employee count if present) and serves as the parent for related Contact records. Clients without a company name skip the Company record and land only as a Contact.

Jobber properties store service-location data with address, access notes, and property-specific custom fields. HighLevel has no native property object. We create a Property custom object type in HighLevel with address, access instructions, and property custom fields, then link it to the parent Contact via a lookup relationship.

Jobber quotes map to HighLevel opportunities because both represent pre-sale proposals with amounts, line items, and status. Quote number becomes the opportunity name. Total amount maps to opportunity value. Status (Draft, Sent, Accepted, Declined) maps to a custom status field on the opportunity since HighLevel stage names differ.

Each line item on a Jobber quote — service name, quantity, unit price, total — migrates as a custom object record linked to the parent Opportunity. This preserves the full quote structure in HighLevel for reference even though HighLevel natively handles line items differently.

Jobber jobs are the core operational record — scheduled date, assigned team member, job type, status, and line items. HighLevel has no job object. We create a Job Record custom object with scheduled date, assigned user (resolved by email), job status, job type, and description fields. Original create and completion timestamps are preserved as custom datetime fields.

Services and materials attached to a Jobber job migrate as child custom object records linked to the parent Job Record custom object. This maintains the full job cost breakdown in HighLevel and supports job-costing reporting if needed.

Jobber invoices have invoice number, date, due date, total, status, and paid date. HighLevel has no invoice object. We create an Invoice Record custom object with those fields plus a link to the parent Contact and the originating Job Record custom object so payment history is traceable in HighLevel.

Jobber team members are operational users (technicians, dispatchers). HighLevel users are CRM users. We map team members by email match — if a HighLevel user exists with the same email, the team member maps to that user. Unmatched team members are flagged for manual HighLevel user creation before the migration runs.

Any custom fields defined on Jobber clients — for example, 'Preferred Service Day' or 'Equipment Make' — migrate as custom fields on the HighLevel Contact object. We create each custom field in HighLevel before import and map values row-by-row during bulk import.

Files attached to Jobber clients, jobs, or invoices are downloaded and re-uploaded to the corresponding HighLevel record. File size limits apply — HighLevel's default upload limit is 50MB per file. We flag any files exceeding that limit for manual download and re-upload.

Jobber notes attached to clients migrate as HighLevel contact notes. Original timestamps and the creating team member's name are preserved in the note body for audit continuity.