Migrate from Plexus Software to Microsoft Dynamics 365 Sales

Plexus Customer maps directly to Dynamics 365 Account. Plexus stores customer name, address, billing contact, and account-level notes. We preserve the original Plexus customer ID in Source_System_ID__c for traceability and delta-run de-duplication against the Plexus export. The Source_System_ID__c field also enables downstream integration layers to reference the Plexus origin when syncing with other line‑of‑business systems, ensuring data lineage is maintained across the enterprise.

Plexus Contact maps to Dynamics 365 Contact. Plexus stores first name, last name, email, phone, mobile, job title, and role per contact. Dynamics 365 requires a parent AccountId; contacts without a primary customer are attached to a default 'Unassigned' account record or flagged for manual assignment before migration.

Plexus Employees have no direct Dynamics 365 equivalent. Active Plexus employees with CRM-relevant roles (account manager, sales contact) map to Dynamics 365 SystemUser records for owner assignment. Plexus skill tags, certifications, and labor rates migrate as custom fields on the User record. Inactive employees or field-only staff become Contacts with an Employee_Source__c flag.

Plexus Work Order is the central operational record — it contains job description, assigned employee, schedule window, time entries, expenses, and status. We map it to Dynamics 365 Opportunity, using custom fields (WorkOrder_Number__c, WorkOrder_Status__c, WorkOrder_ScheduledDate__c, ActualStart__c, ActualEnd__c) to preserve Plexus-specific properties. The Opportunity Stage maps from Plexus work-order status (Scheduled → In Progress → Completed → Invoiced) to a custom Sales Process.

Plexus Quote contains line items, pricing, and approval status. We map it to Dynamics 365 Opportunity with Product Line Items representing Plexus quote lines. Plexus Quote Number preserves as Quote_Number__c. If the Plexus quote was converted to a Work Order, that relationship is captured as Opportunity_Linked_WorkOrder__c on the destination opportunity.

Plexus Schedule stores employee assignments per work order, capacity views, and dispatch notifications. These do not map to any native Dynamics 365 entity. We create a custom Plexus_Schedule__c table in Dataverse with fields for ScheduleId, WorkOrderId, EmployeeId, ScheduledStart, ScheduledEnd, Status, and DispatchNote. Dynamics 365 admins can view this table in a Power App or canvas app built post-migration.

Plexus Time Entry records clock-in, clock-out, overtime, GPS location, and billable/non-billable flags per employee per work order. We create a custom Plexus_TimeEntry__c table in Dataverse with fields for TimeEntryId, WorkOrderId, EmployeeId, ClockIn, ClockOut, HoursWorked, OvertimeHours, Billable__c, GPS_Location__c, and Cost. Dynamics admins can surface this in Power BI for job costing.

Plexus Expenses capture per-work-order costs including parts, travel, and third-party charges with reimbursement status. Small expenses (under $500) that belong to a specific work order migrate as Opportunity custom fields (Expense_Amount__c). Larger or recurring expenses create a custom Plexus_Expense__c table linked to the opportunity by WorkOrder_Number__c.

Plexus Customer Price Catalogs apply customer-specific pricing rules per product or service. Dynamics 365 uses Price Lists attached to Opportunities. We map Plexus customer-specific price adjustments to Dynamics 365 Price List Item records keyed by AccountId, preserving the override rate as custom field Customer_Price_Rate__c on the Price List Item.

Plexus Employee Skill Tags (HVAC, Electrical, Plumbing, CDL, etc.) have no Dynamics 365 equivalent. We create a multi-select custom pick-list field Skills__c on the SystemUser record. Skill-to-assignment matching logic requires rebuild in Power Automate or a custom Power App post-migration.