Migrate from ServiceTitan to Nutshell

ServiceTitan operational records have no native Nutshell equivalent — job history loses structural fidelity

ServiceTitan stores job records with status, line items, technician assignments, and GPS timestamps that describe field operations. Nutshell's object model has no native work-order or job entity — only People, Companies, Leads, Deals, and Activities. We convert ServiceTitan jobs to Nutshell activity notes attached to the Person record, preserving the job date, description, and invoice total. However, technician dispatch routing, job scheduling windows, and GPS route data cannot be represented in Nutshell and are not migrated. Teams should decide before migration whether job history as activities meets reporting needs, or whether a separate reporting tool is required for field operational analysis.

Equipment and installed-base records require a custom field structure that Nutshell does not support at scale

ServiceTitan's equipment registry tracks installed units by location with make, model, serial number, install date, and maintenance history. Nutshell Companies have no native equipment sub-object — equipment data must be stored as individual custom fields on each Company record. For ServiceTitan setups with hundreds of equipment records per location, this means the equipment history becomes a text block or a series of custom fields that cannot be queried or reported on efficiently in Nutshell's native reporting interface. We provide a structured manifest for manual field creation in Nutshell before migration, but the data model limitation is structural and cannot be resolved through migration tooling alone.

ServiceTitan custom fields on multiple object types require manual Nutshell field creation

ServiceTitan allows custom fields on customer records, service locations, jobs, and equipment. Nutshell's custom field system is scoped to People, Companies, and Leads only — custom fields cannot be created on Activities or Deals in the same way. We deliver a pre-migration field manifest that maps each ServiceTitan custom field to its recommended Nutshell equivalent, with field type guidance (text, pick-list, date, numeric). However, each Nutshell custom field must be created manually in Nutshell's Settings > Custom Fields before migration runs. ServiceTitan setups with 20+ custom fields across multiple objects extend planning time and require careful sequencing to avoid mapping errors during the migration run.

Workflows, dispatching rules, and automations in ServiceTitan do not migrate to Nutshell

ServiceTitan automations including job-triggered reminders, technician dispatch routing, automatic invoicing rules, and marketing sequences have no equivalent structure in Nutshell. Nutshell's automation model is limited to personal email sequences triggered by lead status changes and task assignment rules. We export your ServiceTitan workflow definitions as a structured reference document your Nutshell admin can use to rebuild equivalent rules in Nutshell's automation settings. The absence of job-triggered logic is a fundamental platform difference — Nutshell cannot replicate the operational automation logic that ServiceTitan was designed to execute.

ServiceTitan's per-technician billing model creates a different cost structure than Nutshell

ServiceTitan charges $245–$500 per technician per month, with pricing tied to the number of field employees who use the platform. Nutshell charges $13–$79 per user per month, with pricing tied to CRM seat count regardless of role. Teams migrating from ServiceTitan to Nutshell often find that the CRM seat count is lower than the technician count — dispatchers, schedulers, and back-office staff who were counted in ServiceTitan's pricing may not all need Nutshell CRM licenses. However, Nutshell does not natively support the dispatch, scheduling, or route-optimization workflows that justify those ServiceTitan licenses, so the cost savings must be weighed against the loss of field operations functionality.