Migrate from Plexus Software to Twenty CRM

Plexus employees (dispatchers, technicians, schedulers) map to Twenty Workspace Members for system access and People records for contact/assignment data. Skill profiles and capacity data store as custom fields on the People record. Email match resolves ownership during migration. Workspace Members must be created and accepted before Job and TimeEntry owner fields can resolve.

Plexus customer records (name, address, contact info, billing settings) map directly to Twenty Companies. Customer price catalog associations migrate as custom select fields on the Company record. Parent-child customer hierarchies map to the ParentId relation if supported in the Plexus export. Companies import first because they have no incoming foreign-key dependencies.

Plexus contact records (name, email, phone, job title) map directly to Twenty People. Multiple contacts per customer allowed — each links to the same Company via companyId. CreatedAt and updatedAt timestamps preserved as custom datetime fields since Twenty's system fields reflect migration time. Company must exist before contact import runs.

Plexus work orders require a custom WorkOrder object in Twenty since no standard CRM object handles field-service jobs. Fields include jobNumber (unique identifier), status, scheduledDate, assignedEmployeeId (relation to People), jobType, and siteAddress. Original job create date preserved as Original_Create_Date__c. Job status values require value-mapping to Twenty pick-list before import.

Plexus soft scheduling (capacity reservation without specific employee) and hard scheduling (assigned technicians) split into two Twenty constructs: scheduledDate on WorkOrder for the reservation date, and a custom ScheduleAssignment junction object linking WorkOrder to People for assigned-employee records. Skill-based dispatch logic must be rebuilt manually in Twenty's workflow builder.

Time sheets, billable hours, overtime rules, and timesheet approvals from Plexus map to a custom TimeEntry object in Twenty. Fields include entryDate, hoursWorked, isBillable (boolean), timeRule (overtime/double-time category), jobId (relation to WorkOrder), and employeeId (relation to People). GPS location data from Plexus mobile entry stored as a custom text field. Overtime enforcement logic does not migrate.

Plexus Expenses (unplanned costs, reimbursable purchases) map to a custom Expense object in Twenty. Fields include expenseDate, amount, description, category (select from Plexus categories), reimbursementStatus, and jobId relation. Customer-facing billable expenses link to WorkOrder for invoice matching. Expense categories require pick-list value creation in Twenty before import.

Plexus quotes and estimates require a custom Quote object. Line items serialize as a custom JSON field or split into QuoteLineItem child records (implemented as a second custom object). Quote total, status, validUntil, and customerId (relation to Companies) migrate directly. Custom pricing rules from Plexus Customer Price Catalogs stored as custom fields on the Quote.

Plexus job costing (labor cost per employee, third-party costs, prevailing-wage rules) merges into the WorkOrder and TimeEntry objects. Total labor cost calculates from TimeEntry hours multiplied by employee wage rate stored as a custom field on People. Third-party costs store as custom Expense records linked to WorkOrder.

Plexus file attachments on jobs (photos, signed documents, receipts) migrate as Twenty Notes attached to the corresponding WorkOrder or Expense record. Original filenames preserved. Inline images from notes downloaded and re-hosted in Twenty's file storage. File size limits apply per Twenty's upload constraints.

Plexus Skill-Based Employee Suggestions store as a custom multi-select field (Skills__c) on the People record. Skills are text values migrated as-is — scheduling rule logic based on skill-matching must be rebuilt manually in Twenty's workflow builder. Skill values must be normalized if Plexus uses inconsistent naming conventions.

Plexus workflows (dispatch notifications, schedule-change alerts, timesheet approval routing) have no Twenty CRM equivalent. We export Plexus workflow definitions as a reference document for manual rebuild in Twenty's workflow builder or via custom code. FlitStack migrates data only — workflow logic requires manual recreation by your admin team.