Migrate from Aidoo Mobile to Twenty CRM

Aidoo Mobile customer and contact records migrate as Twenty People records. The email, phone, name, and address fields map directly. The company association in Aidoo Mobile (which company a customer belongs to) maps to Twenty's companyId relation field on the People record. Owner/technician assignments in Aidoo Mobile require email-based user matching against Twenty workspace members before the relation can be resolved.

Aidoo Mobile company records migrate as Twenty Company records. Company name, industry, website, employee count, and annual revenue map to the corresponding Twenty Company fields. Parent-child company hierarchies in Aidoo Mobile map to Twenty's parentCompanyId relation field. If Aidoo Mobile stores multiple contacts per company, all associated People records link to the same Company record via companyId.

Aidoo Mobile work orders are the central FSM object and map to Twenty Opportunities as the CRM-side equivalent. Job name becomes Opportunity name. Job status (Pending, In Progress, Completed, Cancelled) maps to Twenty's opportunityStage field with value-by-value mapping to Twenty pipeline stages the admin creates. Job amount or estimated cost maps to the Opportunity amount field. The Aidoo Mobile work order ID is preserved as a custom field (originalWorkOrderId__c) for traceability.

Aidoo Mobile service types (e.g., HVAC Repair, Installation, Preventive Maintenance) have no direct equivalent in Twenty's standard Opportunity model. FlitStack AI creates a ServiceType__c custom select field on the Opportunity object in Twenty's Data Model before migration, mapping each Aidoo Mobile service type value to the corresponding pick-list option. Original service type values are preserved verbatim.

Aidoo Mobile technician assignments do not map to a native Twenty user relation because the technician pool may not overlap with Twenty CRM users. FlitStack creates an AssignedTechnician__c text field on Opportunity and stores the technician name or email. If the technician is also a Twenty workspace member, FlitStack creates a relation to the workspace user record by email match. Unmatched technicians are flagged for admin resolution before migration.

Aidoo Mobile service location and GPS coordinates translate to three custom fields on the Opportunity: ServiceLocation__c (full address text), Latitude__c (decimal number), and Longitude__c (decimal number). These are stored as custom fields because Twenty's native address model is tied to the Company object, and FSM service locations frequently differ from the customer's billing address.

Aidoo Mobile equipment and asset records migrate as a Twenty custom object named Asset__c. The object is created in Twenty's Settings → Data Model before import. Asset records link back to the related Company (customer) record via a companyId relation field. Asset serial number, model, install date, and last service date migrate as custom fields on the Asset__c object.

Aidoo Mobile job notes and service comments migrate as Twenty Note records. Each note is linked to the corresponding Opportunity record (the Twenty representation of the work order) via the noteTargetId relation. Original note timestamps and author information are preserved on the Note record. Notes with attachments in Aidoo Mobile trigger a file re-upload step to Twenty Files.

Aidoo Mobile dispatch scheduling events translate to Twenty Task records linked to the Opportunity. The scheduled date and time become the Task dueDate and dueDateTime fields. Task status maps from the dispatch status (Scheduled → Open, Dispatched → In Progress, Completed → Completed). Assigned technician maps to the Twenty workspace member via email resolution.

Aidoo Mobile file attachments on work orders or customer records are downloaded and re-uploaded to Twenty's file storage. Each file is linked to the target record (Opportunity or People) via the attachments relation. File size limits for the Twenty cloud instance apply; files exceeding the limit are flagged for manual download guidance. Inline images embedded in Aidoo Mobile notes are extracted and re-hosted as separate files.

Any Aidoo Mobile custom objects beyond the standard FSM schema (e.g., Permits, Inspections, or SafetyChecklists) map 1:1 to Twenty custom objects. The custom object name, field definitions, and data types are preserved. Custom-object-to-standard-object relationships (e.g., an Inspection linked to a Work Order) require junction objects in Twenty — FlitStack creates these as part of the migration plan when N:N relationships are detected.