Migrate from Hellotracks to Nutshell

Hellotracks Members are field workers, dispatchers, and admins. We map them to Nutshell People records with a custom field Worker_Role__c capturing their Hellotracks role type. Email addresses become Person email; unmatched workers get flagged before migration. Original Hellotracks member IDs are stored as Source_System_ID__c on the Nutshell Person record.

Hellotracks Places are geofenced saved locations (client sites, warehouses, offices). We map them to Nutshell Companies — name, address, contact info transfer directly. Geofence radius, coordinates, and place color are stored as Nutshell custom fields on the Company record. Multi-address places with distinct locations become separate Company records linked by a parent-company custom field.

Hellotracks Jobs are work orders with status, assigned worker, address, and custom fields — there is no native Job object in Nutshell. We store job details (title, description, status, address, assigned worker reference, service type, form submissions) as Nutshell custom fields on the associated Person or Company record, and create a Note linking the job context. This preserves the data but it is not a native Nutshell entity.

Hellotracks Location records capture real-time GPS coordinates, speed, and timestamp for a worker's device. Nutshell has no location tracking concept — we migrate the most recent location coordinates and last-seen timestamp as Nutshell custom fields on the Person record. Historical waypoint data is not carried forward as individual records.

Hellotracks Trips are complete route records with distance, duration, stops, and associated waypoints. Nutshell has no trip or route object. We migrate the trip name, total distance (miles or km), total duration, and trip status as custom fields on the Person record. A consolidated waypoints note stores the full GPS path as text for reference.

Hellotracks Alerts are system notifications triggered by geofence events, idling, or speed violations. We migrate alert records as Nutshell custom fields on the Person — Alert_Type__c, Alert_Status__c, and Alert_Created__c capture the alert name, current status, and original timestamp. Full alert history becomes a Note on the Person record for audit continuity.

Hellotracks Routes are scheduled recurring or one-time navigation paths assigned to workers. Nutshell has no native route object — we store route details (name, type, assigned worker, estimated duration) as custom fields on the Person record and create a linked Nutshell Event record for the scheduled route start time as a visual placeholder in the calendar.

Hellotracks supports custom fields on Members, Places, Jobs, and other entities — stored as key-value pairs or typed fields (bool, decimal, text, number) per the API docs. Nutshell custom fields are created per-entity (Person, Company, Lead) in Settings. We read the Hellotracks custom field definitions via API, create matching Nutshell custom fields, and migrate values — field types map to Nutshell's text, number, or boolean custom field types.

Hellotracks workflow rules govern auto-dispatch, route optimization triggers, Slack notifications, and Google Calendar sync — these are operational automation logic with no Nutshell CRM equivalent. We do not migrate them. We export workflow definitions as a structured reference document and advise rebuilding them using Nutshell's Sales Automation features or a dedicated field-service integration.

Hellotracks integrations connect job dispatch to Slack channels and worker calendars via Google Calendar API. Nutshell's integration ecosystem is CRM-focused (email, web forms, web chat, WhatsApp, Facebook Messenger) and does not include a field-service job dispatch integration. These integrations must be disconnected in Hellotracks and rebuilt or replaced post-migration.