Migrate from JobTread to Nutshell

JobTread Customers map 1:1 to Nutshell Companies. The primary address, phone, and website carry over directly. Customers with multiple locations in JobTread require the team to specify which address is primary — the rest are noted in a custom field.

JobTread Customer Contacts map to Nutshell People records linked to the corresponding Company. The first_name, last_name, email, phone, and title fields migrate directly. If the same contact appears under multiple JobTread customers, the primary company association is used and the duplicate is surfaced as an Account Contact Relationship.

JobTread Jobs map to Nutshell Deals — each deal receives the job name, amount, status, close date, and owner. The job_phase, job_type, location, and cost_group are stored as custom fields on the deal since Nutshell has no native job-phase concept. The full cost item summary is appended to the deal as a note.

JobTread Cost Items do not map to a native Nutshell object. We flatten each cost item into a structured note on the associated Deal — format: '[Cost Group] Item Name | Qty | Unit | Unit Price | Total'. The cost_group_name is preserved in a custom field on the deal so filtering by cost category is possible in Nutshell's list view.

JobTread Cost Groups are a grouping layer above cost items with a group name and optional description. Since Nutshell has no native grouping object, the cost_group_name migrates as a custom pick-list or text field (Cost_Group__c) on the Deal. Teams that want to query deals by cost group in Nutshell use this field as the filter.

JobTread Proposals contain line items, text content, and customer e-signature status. Nutshell has no native proposal object — we export the proposal PDF from JobTread and attach it to the corresponding Nutshell Deal. The line-item totals and signature status are also stored as custom fields on the deal for reference.

JobTread POs carry a vendor, PO number, amount, status, and line items. Nutshell has no PO object — we create a Task on the Deal with the vendor as the task name, store the PO number and status in custom fields (PO_Number__c, PO_Status__c), and attach the PO document as a file if available. PO line items are summarized in the task description.

JobTread Vendors map to Nutshell Companies with a custom 'Company_Type__c' field set to 'Vendor'. This design keeps all vendor records visible in Nutshell's standard Company list while clearly distinguishing them from customer companies for reporting, filtering, and segmentation purposes.

JobTread Vendor Contacts map directly to Nutshell People records linked to the corresponding vendor Company. Standard fields including first name, last name, email address, phone number, and job title transfer directly without transformation. Vendor-specific roles such as Estimator, Project Manager, Accounts Payable Contact, or Field Supervisor are preserved in a custom field (Vendor_Role__c) on the Person record for accurate role identification.

JobTread schedule items and tasks that belong to a specific job link to the corresponding Nutshell Deal as a Task with the task subject, due date, and assigned user preserved. Tasks without a specific job link are migrated as standalone Nutshell tasks.

JobTread custom fields on Jobs, Customers, Cost Items, and Vendors each map to a Nutshell custom field on the equivalent object (Deal, Company, Person). Field type is preserved as closely as possible — pick-lists become Nutshell choice fields, text fields become text fields, date fields become date fields.

JobTread file attachments on jobs, proposals, or customers are re-uploaded to Nutshell and attached to the corresponding record. File size limits per Nutshell apply (25 MB per file for uploads via the API). Inline images in notes are downloaded and rehosted as file attachments.

JobTread user IDs are resolved against Nutshell users by email match before migration. Any JobTread user whose email does not correspond to an active Nutshell account is flagged before migration — the team either creates the Nutshell account first or reassigns those records to a fallback owner.

JobTread Workflows are automation rules that trigger on job status changes, date reminders, and field updates. Nutshell's automation is scoped to lead routing and email sequences — job-based workflow triggers have no equivalent. We export your workflow definitions as a JSON reference document for your Nutshell admin to rebuild using Nutshell's automation tools.

JobTread reports and dashboards are platform-specific visualizations. Nutshell has its own reporting model. We migrate the underlying data (deals, activities, custom fields) so reports can be rebuilt in Nutshell, but the report definitions themselves do not transfer and must be recreated manually.