Migrate from Plexus Software to Pipedrive

Plexus customer contact records (name, email, phone, mobile, job title) map directly to Pipedrive Person. The customer's service address becomes a custom field or address fields on the Person record. If the Plexus customer is a business entity rather than an individual, both Person and Organization records are created.

When Plexus stores a company-level record (as opposed to an individual contact), that maps to Pipedrive Organization. Organization name, domain/website, industry, employee count, and billing address transfer as direct fields. Parent/child company hierarchies in Plexus map to the Organization's parent_org_id field in Pipedrive.

Plexus work orders are the primary migration target. Each work order becomes a Pipedrive Deal. The Deal title uses the work order name or number. Work order status (Scheduled, In Progress, Completed, Invoiced) maps to Pipedrive stage values via value mapping — we create a stage per Plexus status so the funnel reflects the original job lifecycle.

Plexus work order line items (labor hours, materials, equipment) have no native Pipedrive equivalent. We preserve line-item detail as custom fields on the Deal (e.g., Line_Items_JSON__c or split into Labor_Hours__c, Materials_Cost__c, Equipment_Fee__c). The total work order value becomes the Deal's value.

Plexus quotes and estimates map to Pipedrive Deals in a Draft or Proposal stage. Quote totals become the Deal value. If the quote was approved and converted to a work order, the Deal stage is advanced accordingly — we track this transition in a Quote_Converted_to_WO__c custom field.

Plexus schedule blocks (assigned employees, start/end time, schedule status) cannot replicate in Pipedrive's model. We create Pipedrive Activities (tasks) linked to the Deal representing each scheduled shift, and preserve schedule metadata — crew size, assigned employee IDs, status color code — in custom fields on the Deal or Activity for reference.

Plexus time entries (employee, hours logged, billable/non-billable flag, GPS location, overtime/double-time rule applied) map to Pipedrive Activities with type='Task'. Billable hours and job-costing amounts are stored in custom number fields on the Activity or as custom fields on the related Deal. Overtime rule metadata is preserved as a text field for payroll reconciliation reference.

Plexus expenses (amount, category, reimbursable flag, attribution to work order) are preserved as Pipedrive Notes on the linked Deal with expense amount and category stored in custom fields. Reimbursable status is captured as a boolean custom field. No dedicated expense object exists in Pipedrive — the Note + field pattern provides auditable reference without data loss.

Plexus customer-specific pricing rules have no Pipedrive equivalent — Pipedrive Products use a single base price per product. We export the price catalog as structured reference data (custom text fields on the Organization or Deal) so your team can rebuild pricing logic in Pipedrive using Products, custom pricing rules, or a third-party pricing tool.

Plexus employees (technicians, dispatchers, office staff) do not map to Pipedrive Users 1:1 because Pipedrive licenses are for CRM users, not field crews. Employee IDs and names are preserved in custom fields on Deals and Activities for attribution. Plexus owners or assigned technicians are resolved by email match to Pipedrive Users where applicable.

Any Plexus custom property not covered by standard field mapping is created as a Pipedrive custom field on the relevant entity (Person, Organization, Deal, or Activity). Custom field type is matched to Plexus data type — text to varchar, number to int/double, date to date, pick-list to varchar or set. Field key names are assigned by Pipedrive at creation time.

Plexus file attachments on work orders, customers, or quotes are re-uploaded to the linked Pipedrive Deal or Activity. File size limits follow Pipedrive's per-file constraints. Inline images in Plexus notes are extracted and rehosted as Activity attachments. The migration preserves original file names and timestamps for auditability.