Migrate from Plexus Software to Salesforce Sales Cloud

Plexus Customer records map to Salesforce Accounts — customer name, address, phone, website, industry, and billing address fields map directly. Plexus permits multiple contacts per customer; Salesforce uses a primary AccountId with additional Contact records for each individual, and each contact's AccountId links back to the parent Account.

Plexus contacts stored under a Customer map to Salesforce Contacts linked to the parent Account via AccountId. Job title, phone, email, and mobile phone migrate directly. Plexus does not have a separate Lead object — all contacts land in Contact records, not Lead.

Plexus work orders have no direct Salesforce equivalent — the closest standard object is Case. Work order number, type, description, status, and priority migrate to Case fields and custom Case fields. Case.Subject takes the work order name, Case.Description takes the full work order detail.

Salesforce has no native scheduling object. FlitStack creates a Plexus_Schedule__c custom object linked to the Case representing the work order, storing scheduled start and end datetime, assigned technician (via lookup to User), scheduling window type (hard vs. soft), and the capacity view snapshot date.

Plexus dispatch records contain route details, vehicle assignments, driver notes, and SMS/email notification status. Salesforce has no native dispatch object, so FlitStack creates a Plexus_Dispatch__c custom object linked to the Case, storing route identifier, dispatch_datetime, vehicle_id, notification_sent flag, priority level, and GPS coordinates when captured.

Active Plexus employees with login access map to Salesforce Users (by email match). Inactive employees, contractors, and archived workers map to Contacts in a Plexus archive Contact type so the employment history is preserved. Employment status, hire date, and Plexus employee_id live as custom fields on both.

Plexus skill-based employee suggestions rely on skill and certification records per employee. Salesforce has no native skill object. FlitStack creates Plexus_Skill__c linked to the User/Contact record, storing skill_name, certification_type, expiry_date, and skill_level. Skill-matching automation must be rebuilt in Salesforce Flow.

Plexus time entries record hours worked per work order per employee, with billable/non-billable flags, overtime rules, and GPS location. Salesforce has no native time tracking. FlitStack creates Plexus_Time_Entry__c linked to Case and User, storing entry_date, hours_worked, time_type, overtime_hours, and location coordinates.

Plexus quotes and estimates map to Salesforce Opportunities with a Plexus_Estimate__c checkbox set to true. Opportunity.Amount captures the Plexus estimate value. Job description and scope notes migrate to Opportunity.Description. Custom pricing rules from Plexus customer price catalogs require Salesforce CPQ rebuild.

Plexus orders that have been converted from quotes map to Opportunities with CloseDate and StageName indicating the invoiced state. Invoice line items and tax calculations do not map directly — they become OpportunityLineItem records if Salesforce CPQ is deployed, or custom order-line objects for simpler setups.

Plexus expenses track unplanned costs per work order — parts purchased, reimbursements, per-diem charges, and vendor invoices. Salesforce has no native expense object, so FlitStack creates Plexus_Expense__c linked to the Case (work order), storing expense_date, amount, category, description, reimbursement_status, currency, and vendor_name for full auditability.

Plexus capacity views show crew availability, outsourced labor, overtime usage, and utilization percentages per period and location. Salesforce has no native capacity planning object, so FlitStack creates Plexus_Capacity__c linked to User, storing date_range, available_hours, utilized_hours, overtime_hours, utilization_pct, and location identifier to preserve historical capacity data for reporting and future scheduling analysis.

Plexus customer price catalogs apply special pricing per customer automatically. Salesforce stores pricing in standard and custom Pricebook2 entries linked to Opportunities. FlitStack migrates catalog records as custom Plexus_Price_Catalog__c entries for reference — pricing logic must be rebuilt in Salesforce CPQ or custom price-book rules.

Plexus file attachments on work orders, quotes, and customer records are re-uploaded to Salesforce Files (ContentDocument/ContentVersion), preserving original file names, MIME types, file sizes, created dates, and the uploaded-by user. Salesforce's 25 MB per-file limit applies; files exceeding this threshold are flagged before migration so the team can split or compress them.

Plexus workflow rules for scheduling notifications, approval routing, and time-rule enforcement do not have a Salesforce equivalent. FlitStack exports Plexus workflow definitions as JSON documentation for a Salesforce admin to rebuild in Flow. This is always disclosed as a manual-rebuild item.