Migrate from crmConnect to HighLevel

crmConnect contact records map to GoHighLevel Contact objects with standard field names (First Name, Last Name, Email, Phone). We sequence multi-file CSV exports, deduplicate across files using email as the dedupe key, and validate total record count against source totals before import. Custom contact properties require field discovery during the export phase; we map them to GoHighLevel Contact custom fields of the matching type (text, number, date, dropdown). GoHighLevel's contact record does not include a native birthday field — we create a custom field for it if the source data contains birthday data.

crmConnect does not have a distinct Company object — company data is typically stored as fields within the Contact record or as separate contact entries per organization. We extract organization-level data and create GoHighLevel Company records, then re-link the associated Contact records to the new Company via GoHighLevel's Company field on the Contact object. This is a structural change from crmConnect's co-located model and is the first step in the GoHighLevel import sequence.

crmConnect Professional supports one pipeline with up to 5 opportunities; the pipeline stage names and transition rules export from the UI. We create GoHighLevel Pipelines with the same stage names and probabilities, mapping the crmConnect dealstage values to GoHighLevel stage values. If crmConnect has multiple pipeline configurations (even if capped), we map each to a separate GoHighLevel Pipeline. Stage probabilities are rounded to the nearest integer percentage compatible with GoHighLevel's 0-100 scale.

crmConnect Opportunities (deals) link to Contacts and Pipelines. We preserve deal amounts, stage assignments, owner links, and expected close dates. Custom opportunity fields discovered during export are mapped to GoHighLevel Opportunity custom fields. The GoHighLevel Opportunity object is linked to the Contact and Pipeline created in the prior mapping steps via the Contact lookup and Pipeline lookup on the Opportunity record.

crmConnect calendar records (event times, attendees, linked contact associations) export from the UI as structured data. We create GoHighLevel Calendar entries with event details and reconnect booking links by re-configuring the calendar integration with the same Google or Outlook credentials in GoHighLevel. Standard tier crmConnect is limited to 1 calendar — we flag this during scoping if the source account uses multiple calendars.

crmConnect stores membership portals, course enrollments, and student records as separate record types. We export membership status, enrollment dates, and student data as structured records and map them to GoHighLevel custom objects. GoHighLevel's Membership tool provides a course-area structure, but if the source membership includes custom enrollment logic, we configure custom objects in GoHighLevel to preserve the enrollment data and link members to Contact records for use in workflows.

Contact tagging and list segmentation export from crmConnect as tag-to-contact mappings. We preserve tag names as GoHighLevel Tags and restore tag associations on each Contact during import. Segments that represent list membership are preserved as Contact Tags (one tag per segment membership) for use in GoHighLevel's Smart Lists and workflow filters.

Custom forms and surveys link to contacts and pipelines in crmConnect. We export form field definitions and response data separately. Form field types are mapped to GoHighLevel's Form field schema (text, email, phone, dropdown, checkbox, date). Form submissions are imported as Contact records with the source form name stored as a custom field for segmentation. The visual form builder pages do not migrate — we document the form structure for manual recreation in GoHighLevel's form builder.

Email campaign templates and send history export from crmConnect as text and metadata. We preserve template copy, subject lines, and contact association lists. GoHighLevel's email template builder is used to recreate the templates. Automation sequences tied to email sends (e.g., drip sequences, follow-up triggers) do not migrate as workflows — we document the sequence logic for rebuild in GoHighLevel's workflow builder. Email deliverability should be tested post-migration because GoHighLevel uses Mailgun shared infrastructure.