Migrate from WorkBuddy to Nutshell

WorkBuddy contacts map directly to Nutshell People. Name, email, phone, and address fields transfer 1:1 via WorkBuddy's API. WorkBuddy contact roles — such as client contact assigned to a job — become Nutshell Person records linked to the relevant Company. Each Person record preserves the original WorkBuddy contact ID for traceability during delta runs.

WorkBuddy company records map to Nutshell Companies. Company name, domain/website, address, and industry fields map directly through WorkBuddy's API. Multi-site WorkBuddy companies with multiple physical locations become a primary Company record in Nutshell, with site location details preserved in a custom field on the Company record. Each Company retains the original WorkBuddy company ID for reference and delta reconciliation.

WorkBuddy Jobs — the primary work order container — map to Nutshell Deals. Job name becomes the Deal name, estimated value becomes Amount, and job status (quoted, in-progress, completed) maps to a corresponding Nutshell pipeline stage. Job type, priority, and assigned technician are stored as custom fields on the Deal.

WorkBuddy work orders under a Job split into separate Nutshell Deal line items or activity notes. If WorkBuddy has individual work orders tracked as standalone revenue items, each becomes a separate Nutshell Deal linked to the parent Job-Deal via a custom reference field. Multiple work orders per job are consolidated into a primary Deal with work order IDs stored in a custom field.

WorkBuddy asset records — covering equipment, location, and maintenance history — have no direct Nutshell equivalent. Asset name, type, location, and maintenance status are stored as custom fields on the Nutshell Company record. Detailed asset lifecycle history is preserved as a JSON-encoded custom field for admin reference.

WorkBuddy technicians map to Nutshell user accounts resolved by email match. Unmatched technicians are flagged for team action — either creating a Nutshell user account or assigning a fallback owner. WorkBuddy role assignments (field worker, subcontractor) become Nutshell team role assignments.

WorkBuddy scheduling data — job timeslots, technician assignments, dispatch notes — transfers as Nutshell Activities. Native scheduling and dispatch routing does not have a Nutshell equivalent; timeslot information and dispatch notes are stored as task descriptions or custom fields on the associated Deal.

WorkBuddy quotes and estimates map to Nutshell Deal Amount fields. Quote status values — including draft, sent, accepted, and rejected — map to the nearest corresponding Nutshell pipeline stage. Detailed quote line items with product descriptions, quantities, and unit pricing that have no direct Nutshell equivalent are preserved as a custom text field or note attachment on the Nutshell Deal record for reference.

WorkBuddy custom fields on Jobs migrate to Nutshell custom fields on the Deal object. The migration plan flags each custom field by data type (text, number, pick-list, date) and the Nutshell admin creates corresponding fields before the migration run. Custom pick-list values require value-by-value mapping in Nutshell.

WorkBuddy invoice records do not have a native Nutshell equivalent — Nutshell is a CRM and does not include billing or invoicing. Invoice number, amount, and status are stored as custom fields on the associated Nutshell Deal for financial reference.

WorkBuddy technician timesheets migrate as Nutshell Tasks with time-in and time-out timestamps captured in the task description field, and total hours logged in a custom numeric field on the Activity. Labor cost data including hourly rates and total labor charges are preserved as a custom currency field on the associated Nutshell Deal record for financial reference and reporting.

WorkBuddy safety checklist and compliance data attached to jobs transfers as a custom field on the Nutshell Deal. Detailed compliance records are stored as note attachments or JSON-encoded text for admin reference. Nutshell does not have a native compliance module.