Migrate from MobileWorker to Twenty CRM

MobileWorker stores technician profiles as named users tied to an ArcGIS organizational account. These map directly to Twenty's People object. Custom fields capture MobileWorker's worker-specific attributes (certifications, vehicle ID, dispatch zone) that have no standard equivalent in Twenty. Owner assignment resolves by email match against Twenty workspace members.

MobileWorker's core record is a work assignment with status, priority, due date, assigned worker, and location. Twenty's standard Opportunity tracks sales deals, not field jobs. We create a custom Opportunity sub-type or use Tasks for short-cycle assignments, preserving status (assigned, in-progress, completed), priority pick-list, and the original assignment ID as Source_System_ID__c. Routing data lives in custom fields.

MobileWorker's location records often attach to a business address. These map to Twenty's Companies object with standard fields (name, domain, industry, employee count). The company's physical address populates Twenty's address fields, and the primary contact on the assignment links to a Person record via companyId.

A MobileWorker assignment includes a work-site address and lat/long coordinates. The address migrates to Twenty's Company address fields. Geospatial coordinates (latitude, longitude, accuracy, timestamp) have no native Twenty field type — we create custom number fields (Site_Latitude__c, Site_Longitude__c, Location_Accuracy__c) for reference. Geofence radius migrates as a custom number field.

Each status change on a MobileWorker assignment generates a timestamped audit entry. We migrate these as Twenty Tasks with Type='Field Update', preserving the original timestamp, worker name, old status, and new status. This maintains the full assignment lifecycle for reporting continuity in Twenty.

Photos and documents attached to MobileWorker assignments (before/after images, signature captures) are downloaded and re-uploaded as Twenty Notes linked to the relevant Opportunity or Task record. File size limits apply — files over the platform threshold are flagged for manual retrieval. Inline images in notes are extracted and re-hosted.

MobileWorker allows custom attribute forms attached to workers — certifications, vehicle plates, skill tags, dispatch preferences. Each attribute becomes a custom field on Twenty's People object. Pick-list values (e.g., certification type) map value-by-value to Twenty select fields. We create all custom fields in Twenty before the migration run.

Assignment-level custom attributes (work type, materials used, service code, client PO number) map to custom fields on the target Opportunity or Task object in Twenty. Number fields, text fields, and select fields are created in Settings → Data Model before import. Required-field constraints are honoured during mapping validation.

MobileWorker's dispatch groups (team-based routing) map to a custom pick-list field on Twenty's People object (Dispatch_Team__c) and are cross-referenced against Twenty workspace members. If Twenty members exist with matching emails, the worker record links directly; otherwise the dispatch team is stored as a reference field for manual assignment.

MobileWorker owner IDs resolve by email match against Twenty workspace members. Unmatched owners are flagged before migration — the team either invites them to Twenty first or assigns their records to a fallback member. No record lands in Twenty without a resolved owner reference. MobileWorker's role-based permissions (dispatcher vs field worker) do not migrate.

Free-text notes and comments attached to MobileWorker assignments migrate as Twenty Notes linked to the target Opportunity or Task record. Original timestamps and author names are preserved. Rich-text formatting is converted to Twenty's supported format — complex HTML notes are flagged for manual review.