Migrate from MobileWorker to HubSpot

MobileWorker workers map directly to HubSpot contacts. The worker's name, email, phone, and address fields migrate to Contact properties. Workers without email addresses receive generated placeholders and are flagged for manual review post-migration. The placeholder email format follows worker-{id}@placeholder.migration, ensuring uniqueness while your team updates records with real contact information before activating outreach workflows.

Skill names, certification levels, and expiry dates have no native HubSpot equivalent. We create custom properties (Skills_Certifications__c, Certification_Level__c, Certification_Expiry__c) on the Contact record for each unique skill type in MobileWorker. This allows your team to filter contacts by skill, set up renewal alerts for expiring certifications, and rebuild skill-based assignment matching logic in HubSpot workflows using these custom fields as criteria.

Working hours and off-duty periods migrate as custom text or datetime properties on the Contact. HubSpot's availability-based routing must be rebuilt as workflow criteria using these properties. You can configure workflows to check Availability_Hours__c and Availability_Off_Duty__c fields before assigning new deals to workers, ensuring assignments only route to available personnel during their scheduled shifts.

Billable work assignments become HubSpot Deals. The assignment name maps to Deal name, amount to Deal amount, close date to CloseDate, and dispatcher to Owner. Job status text values map to Deal stage via a custom pick-list. This preserves the full financial history of each assignment and allows your sales team to track field-service revenue within the same pipeline view used for traditional sales deals.

Non-billable assignments that should not appear in revenue pipelines migrate as HubSpot Tasks. Task subject carries the assignment name, due date carries the scheduled date, and owner resolves by dispatcher email. This keeps internal operational tasks separate from billable work while maintaining the assignment context and assignment-to-worker linkage within HubSpot's native task management interface.

MobileWorker routes have no direct HubSpot equivalent. We create a Route_Assignment__c custom object linked to Contact (worker) via a lookup. Each route becomes a record with start location, status, and assignment count. This preserves the route-to-worker relationship in HubSpot's object model, allowing your team to query route assignments per worker and build reports on route efficiency using the custom object's fields.

Companies in MobileWorker map 1:1 to HubSpot Accounts. Company name, domain, industry, employee count, and annual revenue map to standard Account fields. Parent-company relationships map via Account hierarchy. This direct mapping preserves your organizational structure in HubSpot, enabling parent-child reporting and hierarchical views of customer accounts that reflect your real-world corporate structure.

Worker lat/long coordinates and location-capture timestamps have no native HubSpot equivalent. We create Worker_Latitude__c, Worker_Longitude__c, and Location_Capture_Time__c custom fields on Contact. Map visualization requires a third-party integration post-migration. The coordinate data remains queryable for filtering workers by geographic region, but displaying this data on maps requires integrating apps like GeoPager or MapMyCustomers that consume these custom field values.

Dispatchers in MobileWorker are matched to HubSpot users by email address. Unmatched dispatchers are flagged before migration — your team either invites them to HubSpot or assigns their workers to a fallback owner. This prevents orphaned assignments and ensures every migrated Deal has a valid HubSpot user as owner, maintaining accountability for field operations within the CRM.

MobileWorker's job status is freeform text that varies by implementation (New, In Progress, On Hold, Completed, Cancelled, etc.). We inventory all unique status values during discovery and create a custom pick-list field (Job_Status__c) mapping each value to a HubSpot deal stage or custom status.

Files attached to workers, assignments, or routes re-upload to HubSpot Files and link to the parent record (Contact or Deal). File size limits and inline image handling follow HubSpot's standard upload constraints. This preserves attachments in their native format while maintaining the relationship to the corresponding worker, assignment, or route record for complete audit trails and document retrieval within HubSpot.