Migrate from Mobile Worker to Twenty CRM

Mobile Worker worker records map directly to Twenty CRM People. The worker's name, email, phone, and job title become the People record's standard fields. Worker status (active/inactive) migrates as a custom select field since Twenty lacks a native worker-status concept. Original hire date migrates as a custom datetime field for continuity.

Mobile Worker's employer/agency field maps to a People.companyId lookup. If the Mobile Worker deployment stores an agency name as free text, we create a Company record in Twenty first and then link the People record. Multi-employer assignments require a custom relation field in Twenty since the standard schema supports one company per contact.

Mobile Worker client or account records map to Twenty CRM Companies. Company name, address, and industry pick-list values map directly. Client contact names stored on the Mobile Worker client record become People records with a companyId linking back to the Twenty Company.

Mobile Worker work orders map to Twenty CRM Opportunities. Work order name becomes Opportunity name; work order value or estimated cost maps to Opportunity amount. The work order's current stage (Dispatched, In Progress, Completed) maps to a Twenty Opportunity stage pick-list — we create stages matching the source terminology. Service category on the work order becomes a custom select field.

Each Mobile Worker stage value (e.g., 'Assigned', 'En Route', 'On Site', 'Completed', 'Invoiced') maps to a corresponding Twenty Opportunity stage. Probability weights and forecast categories are re-applied on the Twenty side based on your input. Stage-entry timestamps are preserved as custom datetime fields on the Opportunity record.

Mobile Worker tasks and job assignments map to Twenty CRM Tasks. Task title, description, due date, and assignee all translate directly. Completed-at timestamps migrate as a custom datetime field since Twenty's native Task model tracks completion as a boolean. Task status (pending, completed) maps to the Task's status field.

Mobile Worker time punches log hours against work orders. We map each time entry to a Task record with custom fields for clock-in time, clock-out time, total hours, and the linked work order. Overtime flags from the source migrate as a custom select. Multiple punches on the same day aggregate into a single Task record per work order per day.

Mobile Worker platforms often store certification badges, license numbers, and skill tags on worker profiles. Twenty has no native equivalent — we create a custom multi-select field (Worker_Certifications__c) on People. Each unique certification from the source becomes a pick-list value so reporting by certification is possible in Twenty.

Mobile Worker stores service-area tags, coverage zones, or GPS coordinates for workers and clients. These migrate to custom fields on the People (for worker service radius) and Company (for client location) records. If the source stores latitude/longitude, we store as separate custom number fields in Twenty.

Photos and documents attached to work orders in Mobile Worker re-upload as Twenty Notes attached to the corresponding Opportunity record. File size limits from Twenty's storage backend apply. Inline images in notes are downloaded and re-hosted in Twenty's storage. We preserve the original filename and upload timestamp.

If the Mobile Worker deployment uses custom objects (e.g., Equipment, Vehicle, SafetyCheck), these map 1:1 to Twenty CRM custom objects. Custom object names are preserved as-is. Custom object relationships that use N:N associations in Mobile Worker require junction objects in Twenty — we surface this in the migration plan and advise on the appropriate relation type.