Migrate from SalesTown CRM to HighLevel

SalesTown Contact records map to GoHighLevel Contacts 1:1, preserving name, phone, email, custom properties, and owner assignment. We map SalesTown owner email to GoHighLevel team member email for owner resolution. Custom properties without a direct GoHighLevel equivalent become custom fields in GoHighLevel, and we flag any that cannot be migrated due to field type incompatibility.

SalesTown Leads (the primary acquisition object collected via auto-capture and smart distribution rules) map to GoHighLevel Contacts and optionally to Opportunities depending on the customer's pipeline strategy. Leads that represent early-stage prospects map to GoHighLevel Contacts with a lead status tag; leads with active deal values map to GoHighLevel Opportunities linked to the Contact. We apply the split rule during scoping based on whether the Lead has an associated deal amount and pipeline stage.

SalesTown Company/Account records map to GoHighLevel Contact records with the company name preserved in the built-in company field on Contact. If the customer maintains complex multi-contact company relationships, we recommend creating a Company custom object in GoHighLevel and linking Contacts via a lookup relationship. SalesTown company fields with no documented schema are exported as available and mapped to GoHighLevel custom fields, with unmapped fields flagged for post-migration review.

SalesTown Deals with amount, stage, owner, and expected close date map to GoHighLevel Opportunities. The SalesTown pipeline and stage assignment determines which GoHighLevel pipeline and stage the Opportunity is placed in. We sequence Deal migration after Pipeline and Stage configuration in GoHighLevel to ensure stage associations are preserved. Deal owner resolution uses the same email-to-team-member lookup as Contact owner mapping.

SalesTown Pipelines with customizable stages map to GoHighLevel Pipelines, which we configure in GoHighLevel before any Deal records are imported. Pipeline names, stage order, and stage-specific win/loss flags are recreated explicitly. Pipelines with different stage counts between source and destination are mapped field-to-field rather than by position to avoid misalignment.

Each SalesTown Pipeline Stage maps to a GoHighLevel Pipeline Stage by explicit name and order mapping. Stage names, probabilities, and ordering are transferred, and stage probability values are rounded to GoHighLevel's allowed range. Stage-specific automation triggers (if any exist in SalesTown) are documented as part of the automation inventory rather than migrated as live rules.

SalesTown Activities (calls, emails, WhatsApp messages) map to GoHighLevel Contact timeline entries. WhatsApp activities carry message status flags that require value mapping because GoHighLevel stores WhatsApp messages as Conversation records rather than activity records. We reconstruct thread relationships using timestamp ordering and sender IDs to maintain conversation continuity in GoHighLevel, since flat CSV exports split threads into individual rows without parent-child associations.

SalesTown Users with name, email, and team assignment map to GoHighLevel Team Members. We resolve by email match and flag any SalesTown Users without a matching GoHighLevel account for the customer's admin to provision before record import. Email addresses must be unique in GoHighLevel to avoid duplicate team member creation.