Migrate from Service Toolz to Nutshell

Service Toolz Customer records map to Nutshell People (the contact object). The primary contact name, email, phone, and address fields map directly. Service Toolz customers without a company association land as standalone People in Nutshell with no AccountId link. During migration, we preserve the original created date and last modified date as custom fields on the Person record to maintain full historical context.

Service Toolz Customers that have not had a quote accepted or work order completed split into Nutshell Leads. The split is based on whether the Service Toolz record has an associated quote in 'Accepted' status or a completed work order — if neither exists, the record routes to Lead to preserve the pipeline-entry distinction.

Service Toolz Company records map 1:1 to Nutshell Accounts. Company name, address, phone, and industry fields migrate directly. Nutshell's Account object supports a website field and custom fields, which we create before the migration run based on the Service Toolz company-field configuration.

Service Toolz Quote records become Nutshell Deals. The quote name maps to Deal name, total amount maps to Deal value, and quote status maps to a Nutshell custom status field because Nutshell Deals use a stage pick-list rather than a quote-status model. We preserve the original Service Toolz quote number as a custom field for audit traceability.

Service Toolz work order records — including work-order number, job description, status, technician assignment, and scheduled date — have no native equivalent in Nutshell's CRM model. We create a Work_Orders__c custom field on the associated Person record and serialize the work-order history as structured JSON stored in that field so the full history remains accessible in Nutshell without creating a separate object.

Individual line items on a Service Toolz work order — parts used, labor hours, and item-level pricing — are serialized as a custom text area field on the associated Deal record in Nutshell, preserving the item-level detail for reference while avoiding the creation of a separate object that Nutshell's CRM model does not support natively.

Service Toolz's Scheduler Integration stores technician appointments linked to work orders. Since Nutshell has no native scheduling or dispatch module, appointment data migrates as a custom datetime field and text description on the associated Person record. We flag this field in the rebuild plan so your team can configure a Google Calendar integration in Nutshell if desired.

Service Toolz product catalog items that appear on quotes do not have a native Nutshell equivalent. We migrate product names and SKU as a custom text field on the Deal record so line-item context is available to sales reps reviewing a migrated quote in Nutshell.

Service Toolz invoices are not CRM objects in Nutshell. Invoice number, amount, and status migrate as a custom field group on the associated Deal record, keeping financial reference data accessible alongside the deal without creating a billing module that Nutshell does not provide.

Any Service Toolz custom properties on the Customer object require pre-creation of a corresponding Nutshell Person custom field before migration. We audit the full custom property list, map data types to Nutshell field types (text, number, date, picklist), and deliver a pre-migration field-creation checklist so Nutshell is schema-ready before the data run.

Service Toolz user IDs and technician assignments resolve to Nutshell users by email match. We run an owner pre-resolution step before migration: any Service Toolz user without a matching Nutshell user email is flagged and assigned to a fallback owner, ensuring no record lands in Nutshell without an owner.

Service Toolz file attachments (photos, signed documents, invoices) linked to work orders have no native file-storage equivalent in Nutshell's base CRM. We capture the attachment URL or filename and store it in a custom text field on the associated Person or Deal record. Files that were hosted in Service Toolz should be downloaded and re-uploaded to a connected storage platform post-migration.