Migrate from Hellotracks to Twenty CRM

Hellotracks Workers map directly to Twenty People. The worker's name, email, phone, and role in Hellotracks populate the corresponding Twenty People fields. Hellotracks device_id and team membership are preserved as custom fields on the People record to maintain operational context and organizational structure after migration.

Hellotracks Jobs are the operational work orders. We map them to Twenty Opportunities so they appear in Twenty's pipeline kanban view. The job title becomes the Opportunity name, the assigned worker becomes the Opportunity's linked Person, and the status field undergoes value mapping to Twenty stage pick-list values.

Hellotracks has no standard stage taxonomy. We map job status to Twenty Opportunity Stage values based on your configured stages. In-progress jobs typically map to 'Proposition', completed jobs to 'Won', and cancelled jobs to 'Lost'. Custom Hellotracks status strings are mapped individually during the planning phase.

Hellotracks Places (saved geofenced locations with radius and contact details) map to Twenty Companies. The place name becomes the Company name, the address becomes the Company address, and any place-level custom fields migrate to Company custom fields. Customer site Places become Companies representing the client organization.

Hellotracks Trips (complete GPS traces including start, waypoints, stops, end, speed data, and duration) migrate as Twenty Notes attached to the relevant People or Company record. The Note body contains a structured summary of the trip: distance, duration, stops, and peak speed, preserving the operational context without requiring a dedicated GPS object in Twenty.

Individual GPS waypoints are too granular for Twenty's data model to handle efficiently. We merge all waypoints into the parent Trip Note as a structured section within the Note body, preserving route precision and sequence while keeping the data in a Twenty-native format that your team can reference.

Hellotracks Alerts (geofence violations, speed violations, no-show triggers) map to Twenty Tasks. The alert type becomes the Task subject, the alert message becomes the Task description, and the triggering worker is linked as the Task assignee. Note: Hellotracks alert trigger logic does not migrate; Tasks are created for historical alerts only.

Hellotracks Forms with extra_number_$ and extra_text_$ fields map to a Twenty custom object named 'FieldForm'. Each form instance becomes a custom object record, linked to the relevant Job (Opportunity) and Worker (People). The form field labels become custom field names in Twenty.

Hellotracks customFields JSON arrays (e.g., {key: 'PO_Number', val: 'PO-2026-1234'}) are exploded into named Twenty custom fields on the parent object. The custom field is created in Twenty's Settings → Data Model during schema setup, then populated from the key-value data during migration.

Hellotracks team membership (worker-to-team relationships) has no direct Twenty equivalent for organizational hierarchy. We preserve team assignment as a custom pick-list or text field on the People record, mapping team names to a consistent set of values in Twenty for reporting and filtering.

Hellotracks Routes (scheduled sequences of Jobs) are preserved as Notes on the assigned Worker's People record. The Note captures the route name, scheduled sequence of stops, and the order of job assignments active at the time the route was executed.

Hellotracks file attachments on Jobs or Places are downloaded from source storage and re-uploaded to Twenty as native attachments on the corresponding Opportunity (Job) or Company (Place) record. File size limits and supported formats from Hellotracks export are respected during transfer.