Migrate from MotionOps to Twenty CRM

MotionOps Clients map directly to Twenty Companies. Company name, address, phone, and domain migrate as-is. Industry, employee count, and annual revenue do not exist as standard Twenty fields — they are created as custom fields in Settings → Data Model before import.

MotionOps Contacts map to Twenty People with direct field mapping for first name, last name, email, phone, and job title. People are linked to their parent Company via the companyId relation field. MotionOps contacts without an assigned client are imported as standalone People records.

Work orders in MotionOps carry job status, assigned technician, service address, job type, and line items. These map to Twenty Opportunities where Opportunity.name = Work Order title, Amount = total job value, and stage reflects job status. Job-specific fields (technician, job type, service address) become custom fields on the Opportunity.

MotionOps proposals have proposal number, status, line items, and total amount. Twenty has no native proposal object. We create a Proposal custom object in Twenty with fields for proposal_number, status, total_amount, and linked Opportunity. Your team then decides how to surface proposals in Twenty's UI using its SDK.

MotionOps invoices include invoice number, amount, status, due date, and line items. Twenty has no native billing entity. We create an Invoice custom object with these fields, linked to the originating Company or Opportunity. Invoice PDF files are preserved as attachments.

MotionOps payment records include payment amount, date, method, and linked invoice. These map to a Payment custom object in Twenty linked to the Invoice custom object via a relation field. Payment history migrates as read-only records with original amounts and dates preserved.

MotionOps technicians and staff members map to Twenty Workspace Members. Owner resolution happens by email match — the technician's email is matched against Twenty workspace members invited in Settings → Members. Unmatched technicians are flagged before migration and can be invited before the run.

MotionOps scheduling data (assigned date, technician, job, location, status) migrates to Twenty Tasks. Task.title = schedule description, dueDate = scheduled date, and assignee = matched technician. Service address and job type are stored as custom fields on the Task. Tasks are linked to the corresponding Opportunity (work order) via a relation field.

MotionOps notes on any record (client, contact, work order) map directly to Twenty Notes. Note.body carries the full original text. Notes are linked to the parent record (People, Company, or Opportunity) via Twenty's association model. Original timestamps and author information are preserved.

MotionOps custom fields on any object map to Twenty custom fields. Field type is inferred from MotionOps type metadata: text → TEXT, number → NUMBER, date → DATE, select → SELECT, multi-select → MULTI_SELECT. Custom fields must be created in Twenty's Settings → Data Model before import. We provide a custom field creation plan as part of the migration package.

File attachments on MotionOps records (proposals, work orders, invoices) are downloaded and re-uploaded to Twenty. Each file is attached to its parent record (Proposal, Opportunity, Invoice). File size limits on Twenty's storage apply; large files are flagged for manual handling if needed.

MotionOps automations, sequences, and follow-up rules do not have a direct equivalent in Twenty. They cannot be migrated mechanically. FlitStack exports the full automation definitions (trigger, conditions, actions) as a JSON reference document that your Twenty admin can use to rebuild workflows in Twenty's Workflow Builder or using the v2.0 SDK framework.