Migrate from MobileWorker to Salesforce Sales Cloud

MobileWorker identities are ArcGIS Online named users — they have email addresses and display names but no Contact record in a CRM. We extract user emails from the ArcGIS portal API, match them to existing Salesforce Users by email, and create Salesforce Contact records for any ArcGIS users who lack a Salesforce counterpart. Unmatched users are flagged before migration so your admin can provision Salesforce licenses or assign a fallback owner.

ArcGIS Workflow Manager jobs map directly to Salesforce Cases — both track status, assigned worker, priority, due date, and description. We map Job status values to Salesforce Case Status pick-list (New, Working, Escalated, Closed), Worker assigned via email-to-User resolution, and Job priority to Case Priority. Original job-created and job-completed timestamps are preserved in custom datetime fields since Salesforce's CreatedDate reflects migration time.

If your MobileWorker deployment uses ArcGIS Workforce (the dispatch app built on Workflow Manager), assignments map to Salesforce Field Service WorkOrder objects. WorkOrder is a separate object from Case and requires the Field Service Lightning license. We create WorkOrder records with Subject, ServiceAddress (from ArcGIS feature location), and associated Contact resolved by email match. Each WorkOrder gets a link back to the originating Case for audit traceability.

ArcGIS feature layers storing field-collected data (inspections, surveys, asset observations) do not have a standard Salesforce equivalent. We create a custom Field_Inspection__c object with a foreign key to the related Account or Asset. Feature attributes map to custom fields on Field_Inspection__c. Spatial geometry (point/location) maps to a Geolocation compound field (Location__latitude__s, Location__longitude__s) for display in Salesforce Maps.

ArcGIS stores feature locations as coordinate pairs in WGS84 or a projected coordinate system. We extract the centroid coordinate and write it to a Salesforce Geolocation custom field on the related Account (for service addresses) or Asset (for equipment locations). If the feature has an associated street address, we also populate the standard BillingAddress/BillingLatitude/BillingLongitude fields on Account.

MobileWorker routes stored as ArcGIS route layers are decomposed into a custom Route__c object and a Route_Stop__c junction object. Each stop in the route links to the related WorkOrder or Case. Route metadata (total distance, estimated duration, sequence order) is preserved in custom fields. Display in Salesforce Maps requires the Maps for Salesforce app or a third-party mapping integration.

If MobileWorker manages physical assets (meters, poles, valves) via ArcGIS feature layers, these map to Salesforce Asset objects. The Asset Name maps from the feature's display name or ID field. Related Account is resolved from a spatial join (feature location intersecting an Account's service territory) or from a foreign key stored in the ArcGIS feature attribute table. Asset status from ArcGIS maps to Salesforce Asset Status pick-list.

ArcGIS Workforce and Field Maps log worker location points as track features in a geodatabase. These are stored as a time-stamped point feature class with no standard Salesforce equivalent. We create Worker_Location__c records with Location__latitude__s, Location__longitude__s, and Timestamp__c for each tracked point, linked to the related Salesforce User. Location history is preserved for audit purposes but Salesforce does not natively display live worker tracks — this requires a custom LWC or third-party field service app.

Photos and attachments captured in ArcGIS Field Maps and attached to work assignments are exported from ArcGIS REST API as binary blobs. We re-upload them to Salesforce as Salesforce Files (ContentDocument/ContentVersion) and link them to the related Case, WorkOrder, or Field_Inspection__c record. File size limits apply: Salesforce Files default to 25MB per file; larger files require Salesforce CRM Content or External Data Integration.

ArcGIS offline map areas and tile packages are platform-specific caching artifacts with no Salesforce equivalent. These do not migrate. We document the offline area boundaries (bounding box coordinates) as a custom field on the Route__c object so your GIS team can recreate the offline maps in ArcGIS Field Maps post-migration. Salesforce's offline capability is managed separately through the Field Service Lightning mobile app.