Migrate from Contractor+ to Nutshell

Contractor+ clients are person-level records with name, email, phone, address, company name, and tags. Nutshell People store the same attributes, with phones as an array and address as a nested object. The primary mapping is by contact email — unmatched contacts are flagged before migration. We preserve the original client ID in a custom field (e.g., Source_ContractorPlus_ID__c) and the original created date in a custom datetime field for reporting continuity.

Nutshell Companies store business‑level data: name, domain, industry, employee count, revenue. Contractor+ companies map directly if the source tracks business entities separately from clients. Multi‑contact companies in Contractor+ collapse to one Company record per business. We also map the company phone and address fields, store the original company ID in a custom field (e.g., Source_ContractorPlus_ID__c) for reconciliation, and flag duplicate companies by domain matching before creating the Nutshell Company record.

Contractor+ leads that are not yet converted to clients migrate as Nutshell Leads. Lead status, source, and notes map to the corresponding Nutshell Lead fields. Nutshell Lead outcomes map from Contractor+ lead disposition values. We also preserve the original lead ID in a custom field (e.g., Source_ContractorPlus_ID__c), map the lead owner by email lookup to a Nutshell user, and flag duplicate leads by email before insertion.

Contractor+ jobs are project records with job type, status, cost, billing type, description, start/end dates, and line items. Nutshell has no native job object. We map jobs to Deals: the Deal name carries the job title, and we create custom fields on each Deal for job_type, job_status, cost, and billing_type. Estimate line items attach to the Deal as deal line items. Job timelines map to the Deal close date with custom date fields for start and target end.

Contractor+ estimates contain line items with description, quantity, unit cost, and total. Nutshell Deals support line items with product name, quantity, and price. We transform each Contractor+ estimate into Deal line items attached to the corresponding Deal, preserving description, quantity, and unit cost. Standalone estimates without a linked job become Deals with line items and no pipeline stage.

Contractor+ stores notes, tasks, call logs, and email records linked to clients or jobs. Nutshell Activities include notes and tasks linked to People or Deals. We migrate notes and tasks directly with original timestamps and owner assignments preserved. Call logs migrate as Activity records with call-type metadata.

Contractor+ custom fields on clients, companies, and jobs migrate to Nutshell custom fields on the equivalent entity. Nutshell supports custom fields on People, Companies, and Leads. Deal custom fields are created for contractor‑specific attributes like job_type__c and billing_type__c. We map pick‑list values to Nutshell pick‑lists; multi‑select values are stored as comma‑separated strings. Required fields are flagged in the mapping document for the Nutshell admin to set as mandatory after migration.

Contractor+ owner IDs on jobs and clients are resolved by matching the owner email to Nutshell users. Unmatched owners are flagged before migration — teams either invite them to Nutshell first or assign records to a fallback owner. Impersonation mode in the Nutshell API ensures changes log as the correct user.

We store the original Contractor+ record ID as a custom field on each migrated record (e.g., Source_ContractorPlus_ID__c on Nutshell Person). This enables delta‑run de‑duplication, rollback targeting, and cross‑reference for ongoing data governance. The custom field is applied to People, Companies, Leads, and Deals, allowing any record to be traced back to its source and supporting reconciliation reports that compare record counts and field values between Contractor+ and Nutshell after migration.

Contractor+ automations (payment reminders, client notifications, job‑scheduling triggers, follow‑up sequences) are disclosed as non‑transferable. We export the automation definitions as a structured document so the Nutshell admin can rebuild triggers using Nutshell's sequence automation and lead‑stage action features. The export includes the rule name, trigger event, condition logic, and the sequence of actions, along with screenshots of the original configuration to guide the rebuild in Nutshell.