Migrate from Star CRM to HighLevel

Star CRM Contact records map directly to GoHighLevel Contact records. Standard fields (name, email, phone, address) migrate 1:1. We perform live API discovery against Star CRM during scoping to enumerate actual field names since no public schema documentation exists, then map each observed field to the corresponding GoHighLevel Contact field by name and type. Custom contact properties are flagged, documented, and recreated as GoHighLevel Contact Custom Fields before import.

Star CRM Company records map to GoHighLevel Contact records with business information fields (company name, address, domain). The company record is imported first so that child Contact records can reference it via the business name match or a custom company ID field. In GoHighLevel, business data lives on the Contact record rather than a separate Account object, so we flatten the company structure into the primary Contact and optionally create a secondary Contact record for the business entity if the customer requires a separate business profile.

Star CRM Deals map to GoHighLevel Opportunities. The deal stage maps to a GoHighLevel Pipeline stage, deal value maps to Opportunity Value, and the associated contact links via GoHighLevel's opportunity-to-contact relationship. We configure the GoHighLevel pipeline (name, stages, stage order) before importing any Deals so that stage assignment is valid at insert time.

Each Star CRM pipeline and its stage values map to a GoHighLevel Pipeline with corresponding stage names. Probability weights on stages migrate as GoHighLevel does not enforce specific probability percentages but we document the original probabilities for the customer's reporting reference. Stage-specific actions (like automated tasks or notifications) are not migrated; we document them for the customer to rebuild in GoHighLevel's workflow builder.

Star CRM Activities (calls, emails, meetings, notes) linked to Contacts or Deals migrate as GoHighLevel Activity Log entries. Date, duration, subject, and content transfer. GoHighLevel stores activities on the Contact timeline; we link each migrated activity to the correct Contact by matching on the Star CRM contact ID preserved in a custom field during import. Activities linked to Deals attach to the related Opportunity via GoHighLevel's opportunity activity association.

Where Star CRM distinguishes Lead records from Contact records, Leads migrate to GoHighLevel Contacts with a custom field star_lead_source__c preserving the original lead source value. If Star CRM uses a separate lead status field, that value is stored in a custom field for segmentation and reporting in GoHighLevel. GoHighLevel does not have a separate Lead object at the Starter tier; all prospects live as Contacts with pipeline-based stage tracking.

Star CRM Users (owner assignment on Deals and Activities) map to GoHighLevel Users by email address. We extract every distinct owner referenced on migrating records, match by email against the destination GoHighLevel workspace's User list, and hold any unmatched owners in a reconciliation queue for the customer's admin to provision before record import resumes.

Tags on Star CRM Contacts or Deals migrate to GoHighLevel Tags applied to the corresponding Contact or Opportunity record. Multi-select tags are preserved as individual tag labels. GoHighLevel Tags are simple string labels and do not support hierarchical taxonomy, so complex tag structures in Star CRM are flattened to a flat tag list.