Migrate from Oracle Field Service Cloud to HubSpot

Oracle FSM work orders become HubSpot tickets. Activity type maps to ticket pipeline and custom type property. Work-order status (scheduled, in-progress, completed, cancelled) maps to HubSpot ticket status. Original work-order ID stored as Source_System_ID__c custom property for traceability and delta-run de-duplication.

Oracle FSM customer records contain both person and organization data. The primary contact lands as a HubSpot Contact with name, email, and phone. The organization and service address are extracted to a HubSpot Company. Customer type (residential/commercial) maps to a custom company property.

Oracle FSM location records store full service addresses with geo-coordinates, access instructions, and site notes. Address lines migrate to HubSpot Company address fields. Latitude and longitude are stored as custom number fields on the company. Access notes map to a custom text property. Multiple locations per customer are handled as multiple Company records linked by a parent-company association.

Oracle FSM resources include field technicians, dispatchers, and admin users. Resources who also appear as service contacts in HubSpot become Contacts with a custom is_technician__c flag. Resource skills and certifications migrate as multi-select custom properties on the contact. Internal FSM users who are HubSpot users are linked by email match.

Oracle FSM activity types define the class of work (installation, repair, maintenance, inspection). Each activity type maps to a HubSpot ticket pipeline or a custom activity_type__c pick-list property. We preserve the activity type name for filtering and reporting in HubSpot.

Oracle FSM work orders specify required skills (HVAC certification, electrical license, etc.). Skills are extracted as a custom multi-select property (required_skills__c) on the ticket. Individual technician skills migrate as matching multi-select properties on Contact records. This enables manual skill-matching in HubSpot since HubSpot has no native routing logic.

Oracle FSM schedules activities with start-time windows, duration, and arrival-time targets. These migrate as scheduled_start__c and scheduled_end__c custom datetime fields on HubSpot tickets. The appointment window duration becomes a calculated duration field. Timezone information is preserved for reporting accuracy. If your organization tracks multiple time zones for field crews, we can also create a separate timezone__c property on the ticket to support reporting across regions.

Work-order attachments, completed forms, and photos from Oracle FSM are downloaded and re-uploaded to HubSpot Files, linked to the corresponding ticket. File size limits apply — HubSpot's default is 25MB per file for most plans. Large files are flagged for manual download links.

Oracle FSM tracks parts consumed per activity. Parts data migrates as a custom text property (parts_used__c) on the ticket listing item names and quantities. If your team uses HubSpot Products and Line Items for billing, we can create line-item records linked to the ticket representing parts as separate billable items.

Oracle FSM maintains a complete status-change log per work order (created, dispatched, started, paused, completed, cancelled). Each status change migrates as a HubSpot engagement timeline entry (note or call log) with the original timestamp and dispatcher name. This preserves the full audit trail of job progression within the ticket.

Oracle FSM routes group multiple activities for a single resource. Each route is decomposed — the route header becomes a custom route_id__c property on each individual ticket. Tickets sharing the same route_id can be grouped in HubSpot using a custom list or workflow filter for reporting purposes.

Oracle FSM's routing algorithm output (optimized route, travel distance, sequence order) has no native HubSpot equivalent. We preserve the original routing output as custom text properties (original_route__c, travel_sequence__c) on each ticket. Your team can use this data to manually rebuild route optimization in HubSpot via third-party scheduling integrations.