Migrate from MobiWork to Twenty CRM

Both MobiWork Customers and Prospects map to Twenty's People object. FlitStack AI tags the source record type (Customer vs. Prospect) as a custom pick-list field (MobiWork_Source_Type__c) on the Twenty People record. All standard contact fields — name, email, phone, address — migrate directly. Phone numbers, job titles, and company associations preserve original values.

MobiWork stores company data alongside customers. We extract the company name and contact details into Twenty's Companies object first (required before People can associate via companyId). Industry, employee count, annual revenue, and address fields map directly. Parent-child company hierarchies in MobiWork map to Twenty's standard Company.parentId relationship.

MobiWork work orders don't have a direct Twenty CRM equivalent — Twenty has Opportunities but no native work order entity. We map Work Order to Opportunity with custom fields: Work_Order_Number__c (text), Work_Order_Status__c (select), Work_Order_Priority__c (select), Scheduled_Date__c (date), Completed_Date__c (date), Technician_ID__c (text), Estimated_Hours__c (number), Job_Address__c (text). The Opportunity Name becomes the Work Order number; Amount is set to zero or a labor estimate if provided.

MobiWork Work Orders are linked to the Customer and optionally the associated Company. In Twenty, the Opportunity is linked to the corresponding People record (the customer contact) and the Company record via standard Opportunity relationship fields. This preserves the full customer and account context for each job.

MobiWork Quotes map to Twenty Opportunities representing estimated or proposed deals. The Quote's estimated amount becomes the Opportunity amount. Quote status (Draft, Sent, Accepted, Lost) maps to a custom pick-list field Quote_Status__c on the Opportunity. Quote items are stored as a custom text field (Line_Items__c) since Twenty has no native quote-line structure.

MobiWork Schedules represent technician assignments and time windows for work orders. These map to Twenty Tasks. The Task title is set to the Work Order number or a descriptive string. The assigned technician resolves to a Twenty user by email match. Scheduled_Date__c and Time_Window__c from the schedule are stored as custom fields on the Task since Twenty Tasks use a single due date. Schedule status (Assigned, En Route, Completed) maps to Task status.

MobiWork Invoices have no native equivalent in Twenty CRM. We create a custom Invoice object via Twenty's /metadata API before migration. Custom fields include: Invoice_Number__c (text), Total__c (currency), Status__c (select), Issue_Date__c (date), Due_Date__c (date), Tax_Amount__c (currency), Work_Order_ID__c (text, linking back to the related Opportunity custom field). The invoice is associated to the People record of the billed customer.

MobiWork Payment records capture transaction data for paid invoices. These migrate to a custom Payment object in Twenty. Custom fields include: Payment_ID__c (text), Amount__c (currency), Payment_Date__c (date), Payment_Method__c (select — maps values to Twenty select options), Transaction_Ref__c (text), Invoice_ID__c (text, linking to the related custom Invoice record). This preserves a complete financial trail in Twenty.

MobiWork allows custom fields per entity. Twenty supports full custom objects created via its metadata API. FlitStack audits all MobiWork custom fields and creates matching custom fields (or custom objects for complex N:N relationships) in Twenty before importing data. Field type mapping is type-aware: text stays text, numbers stay numbers, pick-lists become select fields with value-by-value mapping.

MobiWork stores Owner IDs and Technician IDs on records. These are internal identifiers without direct mapping to Twenty. FlitStack resolves each MobiWork owner/technician by email — if a matching user exists in Twenty, OwnerId maps to that user's ID; if not, the record is assigned to a fallback owner and a flag is raised. Users must be invited to Twenty before migration so this resolution can succeed.

MobiWork electronic forms store images and signatures attached to work orders. FlitStack downloads all attachments from MobiWork, re-uploads them to Twenty Files, and attaches them to the corresponding migrated record (Work Order as Opportunity or custom object). Signature images attach to the People record of the customer who signed. File size limits from Twenty's storage configuration are applied.

MobiWork's built-in integrations with QuickBooks Desktop, Sage One, Stripe, Clearent, and MailChimp have no direct Twenty CRM equivalent. FlitStack documents each active integration and its purpose, delivers a rebuild plan referencing the integration's trigger events and data flows, and flags the integration as a manual-rebuild item in the migration report. This ensures nothing is lost in the data migration even though the integrations themselves cannot be transferred.