Migrate from Plexus Software to HighLevel

Plexus customers are business entities (companies) that also carry individual contact details. FlitStack splits this into a HighLevel Company record for the business name and address, and a HighLevel Contact record for the primary individual. The Plexus customer ID is stored as a custom field on both for traceability.

Plexus contact records (individuals linked to a customer account) map directly to HighLevel contacts. Email, phone, first name, and last name transfer as-is. If Plexus stores the contact on multiple customers, the primary customer link becomes the primary Company association in HighLevel.

All Plexus leads not yet converted to customers are imported as HighLevel contacts, preserving name, email, phone, and any custom fields. A custom field called Plexus_Lead_Status__c stores the original Plexus lead stage (e.g., New, Contacted, Qualified) so the sales team can filter and prioritize follow‑up actions in HighLevel without losing the original pipeline context.

Plexus quotes and estimates do not have a direct HighLevel equivalent. FlitStack maps them to HighLevel opportunities in a dedicated Quotes pipeline, using the Plexus quote total as the opportunity value, the Plexus quote date as a custom field, and the Plexus quote number as a reference field. Line items become opportunity custom fields or opportunity products if they match a HighLevel product catalog entry.

Plexus orders that have been approved or fulfilled map to HighLevel opportunities with a Closed Won stage. The order total and order date are stored as custom fields on the opportunity. If the order contains multiple line items, FlitStack bundles them into an opportunity product list or a custom JSON field depending on volume and structure.

Plexus work orders track job details, assigned employees, scheduling windows, and status. HighLevel has no native work-order object. FlitStack migrates work-order data as structured JSON stored in a custom opportunity field called Work_Order_Data__c. This preserves all job details and can be parsed by a HighLevel workflow for job-status notifications.

Plexus custom properties (industry-specific fields like 'License Type', 'Trade Specialty', or 'Job Type') map to HighLevel contact custom fields if they describe the client, or opportunity custom fields if they describe the deal. FlitStack creates the custom fields in HighLevel before migration and maps each Plexus property value at migration time. JSON-typed custom properties are stored as text strings and flagged for workflow-level extraction.

Plexus time entries record labor against work orders for job costing. HighLevel has no native time-tracking module. FlitStack migrates time-entry summaries (total hours, total labor cost per work order) as a custom opportunity field called Time_Summary__c. Labor detail is preserved in structured JSON format that a HighLevel workflow can surface in client-facing job-status communications.

Plexus expenses track out-of-pocket costs against jobs that may be passed to clients. FlitStack migrates expense summaries as a custom opportunity field called Expense_Summary__c in JSON format. The original expense line items (vendor, amount, description) are preserved and can be referenced in HighLevel invoicing workflows rebuilt by the client's team.

Plexus file attachments on customers, contacts, or work orders re-upload to HighLevel's file storage linked to the corresponding contact or opportunity record. Files are re-hosted on HighLevel's storage during migration. Size limits are respected; files exceeding HighLevel's attachment limits are flagged and provided as a downloadable archive.

Plexus user accounts (dispatchers, sales reps, technicians) map to HighLevel users by email address match. Unmatched Plexus users are flagged before migration so the team can either invite them to HighLevel or assign their records to a fallback user. Owner attribution on migrated opportunities reflects the matched HighLevel user.