Migrate from Workiz to Nutshell

Workiz Clients store the primary contact information for each service location — name, email, phone, service address, billing address. We map these directly to Nutshell People. If the client has no associated company in Workiz, the Person record stands alone. A client's secondary contacts migrate as additional Person records linked to the primary.

Workiz clients with a company name populate both a Nutshell Person record (for the primary contact) and a Nutshell Company record (for the business entity). The company record holds the business address, website, and industry if present. Multiple Workiz clients sharing the same company name collapse to one Company record with multiple Person associations.

Workiz Jobs are the core operational record — each job belongs to a client, has a job type, assigned technician, scheduled window, status, and price. Nutshell Deals have a name, value, pipeline stage, close date, and party associations. We transform Workiz jobs into Nutshell Deals using a mapping where job status (new, in-progress, done, cancelled) routes to specific Nutshell pipeline stages configured for field service reporting.

Workiz job statuses (new, scheduled, in-progress, completed, cancelled) need explicit value-by-value mapping to Nutshell pipeline stages. The Workiz technician can rename statuses in Workiz, so we read the actual status labels from the Workiz account during discovery and configure matching pick-list values in Nutshell's pipeline before migration runs.

Workiz Leads and Nutshell Leads share the same concept — an unqualified prospect captured from a phone call, web form, or third-party lead feed (Angi Leads, Thumbtack, Genius Leads). Source attribution fields in Workiz (ad_source, lead_source) map to Nutshell's standard lead source pick-list, with unmapped values stored as a custom field.

Workiz Estimates contain line items, tax rates, and discount fields with an approval status. Nutshell has no native estimate object. Estimates migrate as Nutshell Deals using the Workiz estimate total as the Deal value. Line items are preserved as a custom text field on the Deal for reference — your team rebuilds formal quotes using Nutshell's proposal tool or a third-party document integration post-migration.

Workiz Invoices carry payment status, balance due, and service fee information. Nutshell has no native invoice object. Invoices migrate as Deals with a custom payment_status field storing the Workiz invoice balance (paid, partially paid, overdue). Workiz payment history is preserved as activity notes on the Deal record — full financial reconciliation requires your accounting software.

Workiz Items are reusable service and product line items stored in a price book. Nutshell Products serve the same function — a catalog of services and parts that can be attached to Deals. We map Workiz Items to Nutshell Products preserving name, unit price, and description. Products must exist in Nutshell before they can be added to Deals, so Product migration runs before Deal migration.

Workiz custom fields assigned to jobs (e.g., job-type-specific inspection checklists, equipment serial numbers, warranty codes) have no native equivalent in Nutshell Deals. We create matching Nutshell custom fields on the Deal object — pick-list values map value-by-value, text fields pass through directly, and date fields preserve the original ISO format.

Workiz custom fields on clients (e.g., billing preferences, property type, key contact notes) map to Nutshell Person custom fields. Nutshell separates Person and Company custom fields, so client-level custom fields live on the Person record. Any company-level attributes from Workiz custom fields are placed on the Nutshell Company record.

Workiz job types categorize work (e.g., lockout, rekey, safe opening) and drive which custom fields appear. Nutshell has no native job-type concept. We store Workiz job type as a custom pick-list field on Nutshell Deals so you can filter pipelines by service category. Job-type taxonomy is preserved as-is; your team defines how to use it in Nutshell reporting.

Workiz Users (technicians, dispatchers, admins) are resolved by email match against Nutshell Users. A Workiz technician assigned to a job maps to a custom field on the Nutshell Deal (Assigned_Technician__c) since Nutshell has no native technician or scheduling concept. Unmatched Workiz users are flagged before migration so you can create Nutshell accounts or assign to a fallback owner.

Workiz Automations are event-driven rules with conditions and actions — e.g., send an SMS when a job status changes to 'completed', or email the client 30 minutes before the scheduled window. Nutshell has no automation engine for field-service events. We export Workiz automation definitions as a reference document for your team to rebuild using Nutshell Sequences or a third-party tool like Zapier.

Workiz stores file attachments on jobs, clients, and invoices (photos, signed documents, equipment specs). Files migrate as Nutshell attachments linked to the corresponding Person or Deal record. File size limits apply — Nutshell's attachment limit is 25 MB per file. Large files or image-heavy attachments that exceed this are flagged for manual re-upload.