Migrate from Workpex to HighLevel

Workpex Leads map directly to GoHighLevel Contacts. All standard lead fields (name, phone, email, address, lead status, source, assigned user) migrate as Contact fields. The Workpex lead status value maps to GoHighLevel's Contact status field. We preserve any lead score or qualification fields as custom fields on the Contact object. Because GoHighLevel does not have a separate Lead object, all Workpex Leads land as Contacts with their original status and source preserved for segmentation.

Workpex Contacts map to GoHighLevel Contacts. The Contact-to-Lead association from Workpex is preserved by mapping both to the same GoHighLevel Contact record. Standard fields (name, phone, email, address) migrate directly. Any custom fields discovered during the pre-migration audit map to GoHighLevel custom contact fields. The original Workpex Contact ID is stored in a custom field for audit trail purposes.

Workpex Company records map to GoHighLevel Locations. The Workpex company name, domain, address, and phone fields map to the corresponding Location fields. In GoHighLevel's multi-location model, a primary Location is created first and assigned as the owning location for all migrated Contacts and Opportunities. If Workpex uses a nested company structure, we flatten it to a single Location level per GoHighLevel's schema.

Workpex Deals map to GoHighLevel Opportunities. The deal name, amount, closing date, and associated Contact/Company relationships migrate. Pipeline stage mapping is handled via the Pipeline Stage object mapping (see below). If Workpex Deals have custom fields, they migrate as custom Opportunity fields in GoHighLevel. We resolve the Contact lookup and the Location lookup at migration time before inserting Opportunity records.

Workpex pipeline stage names and ordering migrate to GoHighLevel Pipeline stages. We create the GoHighLevel Pipeline with matching stage names and probabilities before importing any Deal/Opportunity records. Any deprecated or custom stages from Workpex are flagged during scoping and mapped to equivalent GoHighLevel stage values. Stage ordering is preserved from Workpex's sequence.

Workpex Tasks migrate to GoHighLevel Tasks. Task subject, description, due date, assigned user, and open/closed status transfer directly. The task-assignee mapping is resolved by matching Workpex owner email to GoHighLevel user email. Completed task status maps to the GoHighLevel completed state. Overdue task logic is preserved as a custom date field if the destination does not compute it natively.

Workpex Follow-up Reminders tied to Leads and Contacts map to GoHighLevel Tasks with the reminder date set as the task due date and the reminder description as the task name. Because GoHighLevel does not have a native Reminder object, Reminders are converted to time-bounded Tasks with a custom Reminder_Source__c field set to 'Workpex_Reminder' to distinguish them from standard Tasks. Stagnant or overdue Reminders are migrated with their original status flag preserved.

Workpex call metadata (call duration, direction, timestamp, disposition, recording URL if available) migrates to GoHighLevel Calls. The call record is linked to the associated Contact in GoHighLevel. Call recordings are flagged as file attachments with a note that playback format compatibility must be verified post-migration. If the recording format is unsupported by GoHighLevel's media player, we recommend storing recordings in a linked cloud storage location with the URL preserved in a custom field.

Workpex Users and Owners map to GoHighLevel Users. We match by email address during migration. Any Workpex User without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import resumes. User role and permission set mapping is out of scope for data migration; we document the Workpex role structure for the admin to configure post-migration.

Workpex custom fields on Leads, Contacts, and Deals are discovered during the pre-migration audit and mapped to GoHighLevel custom fields on the equivalent object. Field data type mapping follows GoHighLevel's supported types (text, number, date, picklist, multi-select, phone, email, URL). Any custom fields with incompatible data types (e.g., Workpex stores a value in a format GoHighLevel cannot represent) are flagged in the audit report for manual review before import.