Migrate from Mobile Worker to HubSpot

Field workers map directly to HubSpot contacts. First name, last name, email, phone, and address fields migrate as direct property mappings. Role, certification, and skill data migrate as HubSpot custom properties (text or pick-list). Primary service territory or region migrates as a custom contact property.

Customer accounts in the mobile workforce system map to HubSpot companies. Company name, address, and industry standard fields migrate directly. Multi-location customers with multiple service sites become one HubSpot company with custom properties capturing additional location addresses. Billing contact information and service-level agreements associated with the account are preserved as custom properties on the company record to maintain operational context.

Work orders become HubSpot deals in a dedicated service pipeline. The pipeline maps to a HubSpot deal pipeline with custom stage values representing work order status (e.g., Scheduled, In Progress, On Hold, Completed). Deal amount can carry estimated or actual service revenue if captured in the source.

Source work order status values (e.g., Open, Assigned, In Transit, Completed, Cancelled) map to HubSpot deal stage values via value-by-value mapping. Each status in the source becomes a corresponding deal stage in the service pipeline. Probability values are assigned per stage during configuration.

The technician assigned to a work order maps to the HubSpot deal owner via email match. Unmatched assignments are flagged before migration — either the technician's HubSpot user account is created first or their work orders are assigned to a fallback owner until their account is provisioned.

The service site address from the work order migrates as custom address properties on the HubSpot deal. If the customer account also carries the service address, a HubSpot associations workflow links the deal to the appropriate company contact and address record.

Equipment and assets linked to work orders map to HubSpot products or a custom Asset object depending on your HubSpot plan. Asset ID, model, serial number, and installation date migrate as custom fields. Service history per asset is preserved as engagement notes on the linked deal or contact.

Billable hours logged per work order migrate as custom number fields on the deal (hours_scheduled, hours_actual) and as engagement notes on the linked contact. HubSpot has no native time-tracking object; the data is preserved for reference and reporting, not as a functional time-tracking system.

GPS coordinates and service territory data migrate as custom number fields (latitude, longitude) on the contact record. Real-time geo-tracking requires a location integration post-migration. HubSpot does not natively display geo-positioning on contacts. Historical location data from completed work orders is preserved to support territory-based reporting and future route optimization analysis within the migrated dataset.

Work order attachments, before/after photos, and customer signatures migrate to HubSpot Files and attach to the associated deal or contact record. File size limits and inline image handling follow HubSpot's standard attachment model. Large photo batches are bulk-uploaded via HubSpot's file API.

Source system custom fields on worker records (certifications, insurance expiry, vehicle ID, skills matrix) map to HubSpot custom properties on the contact. Pick-list values are recreated as HubSpot pick-list options. Multi-select skill fields become comma-separated text or multi-select custom properties depending on HubSpot plan support.

Automated scheduling logic, dispatch rules, and route-optimization algorithms do not transfer. These are platform-native constructs that require manual rebuilding in HubSpot workflows or a third-party field-service integration. We document the current rule logic as a reference spec for your implementation team.