Migrate from SoulCRM to HighLevel

SoulCRM Companies map to GoHighLevel Company records on the Contact profile. The GoHighLevel Contact record holds the company name as a field and optionally links to a Company record for hierarchical organization. We import Company records first so that the Contact-to-Company link is resolved at import time. SoulCRM's company-level custom fields (GST identifier, regional category) require recreation as GoHighLevel contact custom fields since GoHighLevel does not have a separate Company custom field schema by default.

SoulCRM Contacts migrate directly to GoHighLevel Contacts. Standard fields (name, phone, email, address, interaction history) map to their GoHighLevel equivalents. SoulCRM contact-level custom fields for India-specific data (GST number, regional segment) are preserved as custom fields on the GoHighLevel Contact object for manual field creation. We run deduping on email address during import to prevent duplicate Contact records.

SoulCRM Leads map to GoHighLevel Contacts without a separate Lead object. GoHighLevel does not separate unqualified prospects into a distinct Lead object by default; all pre-sale records live as Contacts. We import SoulCRM Leads as GoHighLevel Contacts and preserve the original Lead status in a custom field (original_lead_status__c) for reporting continuity. If the customer requires a separate Lead tracking workflow, we document the GoHighLevel Workflow trigger configuration for admin setup post-migration.

SoulCRM Deals map to GoHighLevel Opportunities. The Deal stage maps to a GoHighLevel Opportunity stage that we configure before import. Deal amount, probability, owner, and expected close date transfer directly. SoulCRM pipeline names map to GoHighLevel pipeline names that we set up as separate Opportunity pipelines in GoHighLevel's pipeline editor. Closed-won and closed-lost reasons migrate as custom fields on the Opportunity.

SoulCRM pipeline stages map to GoHighLevel Opportunity stages under a corresponding pipeline. We configure stage names, probabilities, and display order in GoHighLevel before any Deal records are imported. Each stage's probability percentage migrates to the GoHighLevel stage probability field, rounded to the nearest integer allowed by the platform.

SoulCRM email, call, and task activities migrate to GoHighLevel Activity records linked to the corresponding Contact or Opportunity. Call duration and disposition migrate to GoHighLevel activity custom fields. Activity timestamps are preserved as the GoHighLevel activity date to maintain the historical timeline. Email body content format may require normalization depending on the richness of the original HTML.

SoulCRM Marketing Campaigns (with name, type, start/end dates, and budget) map to GoHighLevel Campaigns. Campaign membership links to Contacts require a separate association import as Campaign Members after the Contact base import completes. We import campaigns first to establish campaign IDs, then import membership records linking each Contact to its campaign.

SoulCRM custom fields for India-specific data (GST registration numbers, regional segments, industry classifications) are supported across modules. We audit each active custom field during discovery, document the field type and current values, and instruct the customer's admin to recreate equivalent custom fields in GoHighLevel before the data import phase. Deprecated custom fields with zero records are excluded from migration to avoid cluttering the GoHighLevel schema.