Migrate from Pega Sales Automation to HighLevel

Pega Accounts map to GoHighLevel Companies. Industry classification, annual revenue, phone, website, address, and custom properties migrate as Company custom fields. We extract the account dependency graph from Pega's import guide to confirm Company is the first anchor entity loaded, with no parent dependencies.

Pega Contacts map to GoHighLevel Contacts with the Account-Contact foreign key resolved to a GoHighLevel Company lookup. Name, email, phone, title, and address fields migrate directly. Contact disposition codes and Pega-specific status fields become custom Contact fields in GoHighLevel.

Pega Lead records (unconverted prospects with disposition codes) merge into GoHighLevel Contacts. We preserve the original Pega Lead status and any lead score as custom fields. GoHighLevel does not have a separate Lead object, so all unqualified prospects land in Contacts with a lead_source field set to 'Pega Import' and a custom disposition field carrying the original code.

Pega Opportunities map to GoHighLevel Opportunities within Pipelines. Stage name, amount, close date, probability, and forecast category migrate. Stage history from Pega's extended properties becomes a JSON or multi-value custom field in GoHighLevel since GoHighLevel tracks stage movement at the deal level rather than as a historical log.

Pega Activities tie to parent entities (Opportunity, Contact, Account) by foreign key. We load activities after parent records are committed to GoHighLevel. Calls map to Tasks with subtype; emails map to Tasks or Gmail integration records; meetings map to Calendar Events with attendee links. Activity timestamps are preserved in GoHighLevel's ActivityDate fields.

Pega Products map to GoHighLevel Products with SKU, description, and price. We preserve quantity and discount fields on the Opportunity-Product junction as GoHighLevel Opportunity Line Items attached to the corresponding Opportunity.

Pega Sales Teams define record-level sharing. GoHighLevel uses a permission-based team model where team membership controls access to Contacts, Companies, and Opportunities. We map Pega team assignment records to GoHighLevel Team records and assign the migration user to the appropriate team during import.

Pega Territory assignments segment Accounts and users by geography or business unit. GoHighLevel has no native Territory object, so we map territory assignments to a custom Contact/Company field (e.g., Territory__c) or use Tags for segmentation. The customer chooses during scoping.

Pega Campaigns group Leads and Activities for coordinated outreach. GoHighLevel supports Campaigns in its CRM module and also uses Tags for campaign-like segmentation. We map campaign membership and campaign status to GoHighLevel Campaign records or Tag Groups based on the customer's intended use.

Pega custom properties on any base entity are enumerated entity by entity through the Pega API or Ruleset exports. Each custom field is hand-mapped to a GoHighLevel custom field, matching Pega data types (Text, Integer, DateTime, Boolean) to GoHighLevel field types. GoHighLevel's custom field UI in the CRM module handles Text, Number, Date, Phone, and Picklist types.

Pega Cases wrap multiple entity types under its BPM engine with lifecycle states, assignments, and SLA timers. GoHighLevel has no native Case object equivalent to Pega's Work Object. We map Cases to Opportunities if the customer uses cases for deal-tracking, or we pre-create a GoHighLevel Custom Object to hold case-level data including status, assignee, and SLA fields. The customer selects the strategy during discovery.