Migrate from FRONTU to HubSpot

Frontu task records map 1:1 to HubSpot support tickets when the migration goal is service history retention. The ticket's subject, description, status, priority, and owner map directly from Frontu's task fields. Original task create date is preserved as a custom datetime field since HubSpot's Createdate is set at import time.

When full job-history granularity is needed — including parts used, location coordinates, and job-type classification — we create a HubSpot custom object (Field_Service_Job__c) rather than using standard tickets. This preserves Frontu's complete job record without mixing field-service data with general support tickets.

Frontu customer records split into HubSpot Contact (individual) and Company (organization) objects. The Frontu customer's address, phone, email, and primary contact name map directly. Multi-contact customer accounts in Frontu collapse to one primary contact with additional contacts added via HubSpot's contact association model.

Frontu technician records do not map to a HubSpot native object because HubSpot users are CRM users, not field technicians. We create a HubSpot user for each technician (with a placeholder login if they don't need CRM access) and add custom properties for skill certifications, service categories, and mobile app availability — derived from Frontu's technician profile fields.

Frontu's task-to-technician assignment maps to HubSpot Ticket owner. Resolution depends on whether the technician has a HubSpot user account: if yes, they are set as the ticket owner directly; if no, the assignment maps to a team lead or dispatcher who can re-assign in HubSpot.

Frontu's task status values (e.g., Pending, In Progress, Completed, Cancelled) map to HubSpot ticket pipeline stages. We apply a value-by-value translation because Frontu status naming conventions differ from HubSpot's default pipeline stages. Custom status values in Frontu require HubSpot custom pick-list values to be created before mapping can proceed.

Frontu job site address maps to the Contact or Company address fields in HubSpot. Frontu stores structured location data including GPS coordinates that cannot map to a native HubSpot field — we store latitude and longitude as custom number properties on the ticket or custom job object for integration with mapping tools post-migration.

Frontu's per-task parts consumption does not have a HubSpot native equivalent. We create a Job_Parts__c custom object linked to the Field_Service_Job__c custom object (or the ticket) via a custom association. Each part line maps: part name, quantity, unit cost, and total — preserving the financial detail of parts used per job for profitability reporting.

Frontu task comments and technician notes map to HubSpot ticket timeline entries. Each Frontu comment becomes a note or engagement on the corresponding HubSpot ticket, preserving the original timestamp and author (resolved to a HubSpot user where possible). This migration ensures that all historical communication and service notes remain accessible within the HubSpot interface, maintaining continuity in the customer service record.

Frontu's route planning and scheduling data has no HubSpot equivalent. Scheduling logic, dispatch rules, and technician routing must be rebuilt using HubSpot Service Hub workflows combined with a third-party scheduling integration (e.g., Jobber, Route4Me) post-migration. We export Frontu schedule data as a reference CSV for rebuilding.

Every Frontu custom field — including job-type categories, customer SLA tiers, warranty information, and field-specific metadata — maps to a HubSpot custom property. HubSpot's property type system (text, number, date, picklist, checkbox, etc.) determines the mapping type: direct for matching types, transformed for type conversions, and value_mapped for pick-list values that differ between platforms.

Frontu job attachments (photos, signed forms, PDFs) re-upload to HubSpot Files and attach to the corresponding ticket or custom job record. File size limits apply (25MB per file in HubSpot). Inline images in notes are extracted and rehosted as HubSpot file attachments.