Migrate your HighLevel data

Contacts are the primary record type in HighLevel, with standard fields for name, email, phone, address, and lifecycle stage. The platform exposes a bulk CSV export with async processing and 30-day file retention. We map all standard Contact fields and custom properties during migration.

Companies in HighLevel are separate records that can be linked to Contacts, enabling B2B data models. The CSV export for Companies includes all standard fields and supports multi-select bulk downloads. We preserve Company-to-Contact linkage assignments during transfers.

Opportunities track deals in customizable Pipelines with user-defined Stages and dollar amounts. Each Opportunity links to a Contact and optionally a Company. We migrate Opportunity records with their Stage, value, and pipeline association intact.

Custom Objects are fully configurable via the API and can establish relationships to standard objects like Contacts. Migration requires us to introspect the custom object's field schema, map data types between source and destination, and rebuild relationships. Field type differences (choices, multi-select, required flags) require explicit handling.

Workflows are trigger-action sequences that automate tasks like sending emails, SMS, or updating fields. They are a core HighLevel feature but have no direct equivalent in most destination CRMs. We document the full Workflow chain including triggers, conditions, and action sequences, then recommend manual recreation or approximation in the destination platform.

Tags are applied to Contacts (and optionally other objects) for segmentation and Workflow triggers. We export and import tags as a flat list per Contact, preserving all tag assignments during migration.

Pipelines organize Opportunities into Stages that reflect a sales process. HighLevel allows multiple pipelines per sub-account. We map Pipeline and Stage names and order exactly, preserving which Opportunity belongs to which Pipeline.

Forms capture lead data and trigger automations; Landing Pages host funnels and capture pages. These are content artifacts rather than data records. We export Form field mappings and Landing Page structure metadata, but the visual design must be rebuilt manually in the destination platform.

HighLevel's scheduling module creates Appointments linked to Contacts and Calendars. Appointment records (date, time, contact, status) are migrated. Calendar configuration and booking link settings are documented for manual reconfiguration in the destination system.

Tasks in HighLevel are linked to Contacts and assigned to Users, with due dates and completion statuses. We export the full task list including assignment, status, and due date, preserving the relationship to the parent Contact record.

Campaigns group email and SMS broadcasts under a shared name. Campaign metadata (name, description, associated contacts) is migrated, but campaign performance metrics and email/SMS content require field mapping depending on the destination platform's campaign structure.

User records in HighLevel include name, email, role, and avatar. When migrating to a destination CRM, we map User email addresses to Owner/Assignee fields and flag any unmapped users for manual setup. Roles and permissions are not transferable across platforms.

HighLevel's agency model uses sub-accounts to isolate client data within one parent agency account. Migrations involving sub-accounts require us to identify which sub-account(s) hold the relevant data, as each sub-account has its own Contacts, Pipelines, and Workflows. Enterprise accounts can have white-label mobile apps and custom configurations per sub-account.

Attachments linked to Contacts or Opportunities can be exported via HighLevel's file management. Large attachments may require chunked migration with retry logic. We flag attachments exceeding 25MB for manual transfer handling.