Migrate from Jobber to Nutshell

Jobber Clients are individual contacts — they map directly to Nutshell People. Where a Jobber Client represents a business entity rather than an individual, the record can be split into a Nutshell Company with the primary contact as a Person linked to that Company.

When Jobber Client records contain a business name instead of an individual contact name, FlitStack creates a corresponding Nutshell Company record. The primary individual contact from Jobber maps to a Nutshell Person record that links to the new Company via Nutshell's Person-Company relationship (1:N cardinality). This preserves the business-to-contact hierarchy from Jobber while adapting it to Nutshell's organizational model.

Jobber Properties are service-site records attached to Clients — they contain address, site name, access instructions, and property-specific notes. FlitStack maps Property address data to Nutshell's address fields on the Person or Company record. Multiple Properties for one Client generate multiple address records via Nutshell's Person-Company relationship or a custom Property reference field.

Jobber Jobs have no native Nutshell equivalent — they are field service work orders with assigned team members, line items, scheduling, and status. FlitStack converts each Job to a Nutshell Deal, preserving job number as Source_Job_Number__c (a custom field on Deal or Person), amount from line items, and close date from scheduled completion. Job status (Scheduled, In Progress, Completed, Cancelled) maps to Nutshell Deal stage values.

Jobber Quotes are estimates sent to clients — they include line items, totals, and a status (Draft, Sent, Accepted, Declined). FlitStack converts each Quote to a Nutshell Deal with Deal amount from the Quote total, name from the Quote title, and stage set to a custom 'Estimate' stage value. Accepted Quotes can be marked Won and converted to a linked Job-Deal for tracking.

Jobber Invoices have no native Nutshell equivalent — Nutshell has no billing or payment processing module. FlitStack migrates Invoice records as Nutshell Deals with the invoice total as Deal amount, invoice number stored in a custom Source_Invoice_Number__c field, and payment status preserved in a custom Source_Payment_Status__c field. Full invoice line items migrate as Deal notes or a custom field for reference.

Jobber Team Members are the employees or contractors who perform work. FlitStack creates a Nutshell User account for each Team Member by email match. Historical assignment data (which Team Member was assigned to which Job) is preserved by mapping the Team Member as the Nutshell User on the Deal (Job record) or storing it in a custom Assigned_Team_Member__c field on the Person record.

Jobber file attachments on Jobs, Invoices, and Quotes are downloaded and re-uploaded to Nutshell as Note attachments linked to the corresponding Deal record. Nutshell's Notes attach to People, Companies, Leads, and Deals, covering the full range of Jobber attachment targets.

Jobber custom fields attached to Client records map directly to corresponding Nutshell custom fields on the Person object. Nutshell's custom field system supports text, number, date, picklist, and boolean field types, all of which align with Jobber's custom field type options. FlitStack inventories all Jobber Client custom fields before migration, creates matching Nutshell Person custom fields via Settings → Fields, and maps values field-by-field to preserve all original data without transformation.

When Jobber Client records represent business entities rather than individual contacts, FlitStack migrates their associated custom fields to Nutshell Company custom fields. Nutshell's Company custom field system supports the same type palette as Person fields — text, number, date, picklist, and boolean. FlitStack creates equivalent Company custom fields in Nutshell before migration, mapping values directly from Jobber's source fields to preserve all business-type custom field data without transformation.

Nutshell does not support custom fields on Deals. Jobber custom fields on Jobs cannot map to a Deal custom field in Nutshell. FlitStack creates a custom field on the linked Person record (e.g., Job_Type__c, Service_Category__c) and stores the original Job custom field values there as a reference. Customers should audit whether all Job custom field data is critical to preserve or can be stored in the Deal name or notes.

Invoice and Quote custom fields in Jobber face the same Nutshell limitation as Jobs — they cannot attach to Deals. FlitStack stores Invoice and Quote custom field values in a custom field on the Person record, with the original Invoice or Quote number stored alongside for traceability. Alternatively, a Note attached to the Deal captures the full custom field set in structured text.

Jobber's recurring service agreement and maintenance agreement features (Grow plan) have no direct Nutshell equivalent. Nutshell does not model service contracts. FlitStack migrates service agreement records as Notes on the Person record with key terms (agreement type, discount percentage, billing frequency) stored in custom fields. Customers must rebuild recurring billing logic externally or in Nutshell's email sequence model.