Migrate your Hellotracks data

Jobs are the core work-order object in Hellotracks with a stable schema covering status, assigned worker, team, scheduled time, location, and custom fields via the customFields array and extra_* prefixed inputs. We migrate Jobs 1:1 and map their status/progress fields to the destination's equivalent lifecycle stages.

Members represent field staff and are tied to location tracks, assigned jobs, and timesheet records. We map Members to the destination's user or employee object and preserve worker metadata including team assignments and tracking preferences.

Places are saved, geofenced locations with a configurable radius used for automatic check-in/check-out. We export Places with their geofence radius, associated contacts, color label, and custom fields, mapping them to destination location or site records.

Teams group Members for assignment and reporting purposes. We carry forward team membership so that worker-to-team relationships are preserved in the destination system and reporting can be segmented by team.

Tracks represent historical GPS traces recorded by the Hellotracks mobile app. The API returns waypoint arrays with speed, timestamp, and coordinates. We export these as route or location-history records but note that destination systems vary in how they store raw GPS path data.

Trips are complete journey records from start to finish including stops, duration, distance, and trip quality metadata. We export trips as time-and-distance events. Where the destination has a dedicated mileage log object, we map distance and trip purpose fields accordingly.

Waypoints are individual GPS points along a track with speed data. We export them as part of the trip record but note they are typically too granular to migrate as independent records in most destination systems.

Stops are logged arrivals and departures at Places or Jobs, including total time on site. We map these to destination check-in/check-out events or job visit records. Stops at unsaved locations are flagged separately for manual review.

Forms are custom data collection instruments attached to Jobs. Submission data is exportable as CSV or XLSX. We extract form submission records and map them to destination custom record types or attach them as job notes, depending on destination schema.

Alert records capture triggered notification events such as geofence breaches or speed violations. We export alert logs as event records and note that alert rules themselves are platform configuration that must be rebuilt in the destination.

Hellotracks exposes Timesheet, Mileage, and general Activity reports downloadable as CSV or XLSX. We export these as-is for re-import into the destination's reporting module or map line items into the appropriate financial or HR system.

Custom fields on Jobs are stored via the customFields array using key-value pairs and the extra_text_$ and extra_number_$ prefixed slots. We preserve all custom field labels and values during migration and map them to destination custom fields by name.

Hellotracks supports file uploads attached to Jobs but the API documentation does not expose a structured attachment download endpoint. We cannot guarantee file integrity during migration. Customers should download attachments manually or use Hellotracks support for bulk export.