Migrate your Plexus Software data

Jobs are the top-level work container in Plexus, containing multiple Tasks. We migrate Jobs with their primary fields and link them to associated Work Orders, Employees, and Customers in the destination.

Work Orders hold labor costs, time summaries, and associations to specific employees. We preserve the Work Order-to-Employee linkage and job costing data during migration.

Employee records include skill profiles used for scheduling matching. We migrate skill data as custom fields in the destination since not all FSM platforms support native skill-based scheduling.

Time entries carry timestamps, GPS location data, and billable/non-billable flags. Plexus Time Rules (overtime and double-time policies) must be mapped to the destination's pay规则 engine since rule definitions are proprietary.

Expenses include unplanned costs tied to Work Orders for job costing. We migrate expense records with their Work Order associations and flag whether they should become billable line items in the destination.

Quotes and approved estimates are migrated as Orders in most destination systems. We preserve the approval status and customer-linked pricing from Customer Price Catalogs.

Special pricing rules tied to specific customers require value-mapping to the destination's pricing engine. We extract the customer-to-price-rule mapping as a reference table.

Schedule blocks, soft reservations, and capacity snapshots represent future-dated scheduling data. We migrate open blocks as pending tasks or calendar events, noting that soft reservations without assigned employees may not have a direct destination equivalent.

Tasks within Jobs carry skill requirements used for scheduling suggestions. We preserve task-to-skill linkages so the destination's scheduler can re-run matching logic.

Custom, color-coded Schedule Statuses are Plexus-specific. We map each status to the destination's nearest equivalent workflow state and flag unmapped statuses for manual review.

Job costing ties labor wages, third-party costs, and prevailing-wage rules to specific Jobs. We migrate the costing totals and flag prevailing-wage records since not all destination platforms support that schema.

GPS coordinates logged at clock-in and clock-out are Plexus-native telemetry stored in the Time Entry record. We do not migrate raw GPS data to the destination as it is location-specific and rarely required for billing or scheduling continuity.