Migrate from PipelineManager to HighLevel

Each PipelineManager Pipeline becomes a GoHighLevel Opportunity Pipeline. We create the Pipeline in GoHighLevel under Opportunities > Pipelines, then map each PipelineManager Stage to a GoHighLevel Stage value in the same ordinal position. Stage probability percentages migrate from PipelineManager to GoHighLevel's stage probability field. If the customer uses more than three Pipelines and is on GoHighLevel Starter, we flag the limit during scoping and recommend upgrading to Unlimited before migration.

PipelineManager Deals map directly to GoHighLevel Opportunities. The Pipeline and Stage assignment from PipelineManager determines the Opportunity Pipeline and Stage in GoHighLevel. Deal value (amount), close date, owner (via email match to GoHighLevel User), and any deal-level custom properties migrate to the Opportunity. Closed-Lost and Closed-Won statuses map to GoHighLevel Opportunity status values.

PipelineManager People records migrate as GoHighLevel Contacts. Name, email, phone, and address fields map directly. Any PipelineManager custom properties on People require pre-creation of GoHighLevel Custom Fields before import; we identify all custom properties during discovery and include the full list in our scope document for the customer to configure before migration begins.

PipelineManager Companies present a mapping choice in GoHighLevel. The simpler path stores the Company name on each related Contact using GoHighLevel's Locations feature or a Company Name custom field. The more complete path creates a GoHighLevel Custom Object for Companies with a lookup relationship to Contacts. We present both options during scoping and implement the customer's chosen strategy. The lookup relationship to Deals (Opportunities) is preserved by linking the Contact to the Opportunity as the primary contact.

PipelineManager Activity logs (calls, emails, notes, meetings) attached to Deals or People migrate as GoHighLevel Contact notes and activity entries. We preserve the original timestamp, activity type, and description. Activity is linked to the migrated Contact record. Large activity volumes (over 50,000 records) may require batch processing with parent-record lookup resolution.

PipelineManager file attachments migrate as GoHighLevel Contact or Opportunity attachments. We transfer files in their original format, preserving filenames. Attachments are linked to the migrated record (Contact or Opportunity) based on the original attachment's parent object in PipelineManager.

PipelineManager custom properties on People migrate to GoHighLevel Contact Custom Fields. The customer must create these custom fields in GoHighLevel before migration begins; we provide the complete list with field type recommendations during scoping. We do not create custom fields in GoHighLevel as part of standard migration scope.

PipelineManager custom properties on Deals migrate to GoHighLevel Opportunity Custom Fields. Same process as Contact custom fields: we inventory all deal-level custom properties during discovery and provide the field list for the customer to configure in GoHighLevel before data import.

PipelineManager Users (deal Owners) map to GoHighLevel Users by email address match. We extract all distinct owner email addresses from Deals, People, and Companies, match against GoHighLevel Users, and flag any PipelineManager Owners without a corresponding GoHighLevel User for the customer's admin to provision before migration. Inactive PipelineManager Owners migrate with the Owner assignment preserved for reassignment.