---
title: "Migrate to HighLevel: CRM Migration Guide & Service"
description: "Migrating to HighLevel? Import limits, the full migration checklist and every source FlitStack AI moves into HighLevel, with history and rollback."
url: "https://flitstack.ai/migrations/crm/highlevel"
---

# Migrate to HighLevel

GoHighLevel is an agency-native all-in-one CRM whose Sub-account architecture, Snapshot model, and rebuild-everything-as-Workflows reality reward teams that plan the location hierarchy and A2P 10DLC registration before the first contact is imported.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into HighLevel from 850+ CRMs, including Marketing Star, Follow Up Boss, Dubsado, Mailchimp. Every field is mapped to HighLevel's objects, history and associations come across, the HighLevel setup is configured alongside, and the whole migration stays reversible in one click.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See every source →](https://flitstack.ai/migrations/crm/highlevel#sources-list)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

From Any source ![](https://flitstack.ai/platforms-trim/marketing-star.webp) ![](https://flitstack.ai/platforms-trim/follow-up-boss.webp) ![](https://flitstack.ai/platforms-trim/dubsado.webp)

Destination HighLevel ![](https://flitstack.ai/platforms-trim/highlevel.webp)

Marketing Star Follow Up Boss Dubsado Mailchimp ActiveCampaign

850+ sources mapped into HighLevel

## Systems we move into HighLevel

The CRMs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

[![](https://flitstack.ai/platforms-trim/marketing-star.webp) Marketing Star to HighLevel](https://flitstack.ai/migrations/crm/marketing-star/to/highlevel) [Follow Up Boss to HighLevel](https://flitstack.ai/migrations/crm/follow-up-boss/to/highlevel) [Dubsado to HighLevel](https://flitstack.ai/migrations/crm/dubsado/to/highlevel) [Mailchimp to HighLevel](https://flitstack.ai/migrations/crm/mailchimp/to/highlevel) [![](https://flitstack.ai/platforms-trim/activecampaign.webp) ActiveCampaign to HighLevel](https://flitstack.ai/migrations/crm/activecampaign/to/highlevel) [HubSpot to HighLevel](https://flitstack.ai/migrations/crm/hubspot/to/highlevel) [Cloze to HighLevel](https://flitstack.ai/migrations/crm/cloze/to/highlevel) [Pipedrive to HighLevel](https://flitstack.ai/migrations/crm/pipedrive/to/highlevel)

## What HighLevel supports, and where its import tools stop

- Agencies choose HighLevel to consolidate CRM, email, SMS, scheduling, and funnels into one subscription, eliminating monthly bills for five to ten separate SaaS tools they previously stitched together.
- The flat-rate pricing model bills per sub-account rather than per contact, so growing a contact database from 1,000 to 100,000 records does not trigger a billing surprise—a common pain point avoided by migrating customers.
- White-label and sub-account capabilities let agencies resell HighLevel access to their own clients, turning a software cost center into a recurring revenue stream that justifies the subscription.
- The platform ships a 14-day free trial with no credit card required, giving teams a low-friction entry point to validate fit before committing to the $97/month Starter tier.

**Bulk API** Bearer token (JWT)

**Rate limits** 200,000 API requests per day and 100 API requests per 10 seconds per sub-account

| Object                        | Support | Note                                                                                                                                                                                                                                                                                                                                                                          |
| ----------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Contacts                      | full    | 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                     | full    | 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                 | full    | 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                | mapped  | 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 (Automations)       | mapped  | 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                          | full    | 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 and Pipeline Stages | full    | 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 and Landing Pages       | mapped  | 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.                                                                           |
| Appointments and Calendars    | mapped  | 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                         | full    | 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                     | mapped  | 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.                                                                                                |
| Users and Assignees           | mapped  | 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.                                                                                                         |
| Sub-Accounts                  | mapped  | 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 and Files         | mapped  | 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.                                                                                                                                           |

## The HighLevel migration guide

## Why teams migrate to GoHighLevel

*The four shapes a GoHighLevel migration takes, and what makes the platform easier — or harder — than the category average.*

HighLevel, Inc. (commonly branded GoHighLevel or GHL) is a Dallas, Texas-based all-in-one operating system aimed at marketing agencies and their SMB clients, with stated reach of 1M+ businesses on platform[1](https://flitstack.ai/migrations/crm/highlevel#source-1). The product bundles CRM, funnels, websites, email, SMS/voice via LC Phone, Workflows, Calendars and a white-label SaaS-resale mode under a single Agency / Sub-account hierarchy.

The typical GoHighLevel customer is a digital agency reselling the platform to dozens or hundreds of small-business clients under its own brand, or an SMB on the receiving end of that resale — gyms, dental practices, real-estate teams, home services.

Compared with HubSpot or Salesforce, GoHighLevel positions on bundled marketing-plus-CRM at a flat monthly fee starting at $97/mo Starter, $297/mo Unlimited, $497/mo SaaS Pro; compared with ActiveCampaign or Keap, it positions on Funnels, Websites and Phone System being native rather than integrated.

The shapes of migration that actually land on GoHighLevel tend to fall into four patterns. First, stack consolidation: a business replacing Pipedrive plus Mailchimp plus Calendly plus ClickFunnels with a single GHL Sub-account. Second, agency replatforming, where an agency moves its entire client book off ActiveCampaign, Keap or HubSpot and stands up one Sub-account per client.

Third, HubSpot or Salesforce exits driven by total cost of ownership — practitioners report leaving HubSpot at sub-$2M ARR to escape contact-tier pricing and per-seat fees[27](https://flitstack.ai/migrations/crm/highlevel#source-27). Fourth, vendor exits from ClickFunnels, Skool, ConvertKit or Keap, where the source is decommissioned in favour of GHL's bundled offering.

What makes migrating to GoHighLevel easier than the category average is the CSV import wizard — separate guided flows for Contacts, Opportunities, Companies and Custom Objects, with auto-mapping, preview, dedupe-by-unique-field controls, and a Bulk Actions monitor that lets you pause, resume or cancel a running import[31](https://flitstack.ai/migrations/crm/highlevel#source-31) [8](https://flitstack.ai/migrations/crm/highlevel#source-8).

What makes it harder than the average is the Agency / Sub-account / Location hierarchy — every Contact lives inside exactly one Sub-account (also called a Location), so cross-client data sharing is structural, not a setting; and the Custom Objects cap of 10 per Location with a 1,000 records-per-association limit that bites real-world many-to-many use cases[10](https://flitstack.ai/migrations/crm/highlevel#source-10) [14](https://flitstack.ai/migrations/crm/highlevel#source-14).

On top of those structural limits, the A2P 10DLC SMS registration requirement must be completed before LC Phone can send a single text — Brand plus Campaign approval takes 1-3 weeks of carrier vetting.

Automations, Funnels, Websites, Workflows and lead-scoring rules do not import — they are rebuilt inside GHL from documentation. Teams that scope for that rebuild work up front finish on time; teams that assume parity do not.

> Workflows are the rebuild tax of every GoHighLevel migration. Budget for it before you sign.

## The GoHighLevel data model you need to map into

*Objects, custom fields, associations, and the unique-field upsert keys you'll wire on every record — the destination schema decoded.*

GoHighLevel's CRM is built around a compact set of standard objects scoped to a single Sub-account (Location), plus Custom Objects, Custom Fields, Custom Values, and Associations that connect records across object types[2](https://flitstack.ai/migrations/crm/highlevel#source-2). The three core standard objects — Contacts, Opportunities, Companies — can be renamed to match your team's terminology, but the underlying data keys stay constant[2](https://flitstack.ai/migrations/crm/highlevel#source-2).

Before mapping a field on the source side, you need to know which destination object the row belongs on, what Sub-account it lands in, what fields are required, and which value will serve as its unique-field match key. The table below summarises the objects you will touch.

| Object                                 | What it stores                                       | Required                                                        | Tier                                                                                           |
| -------------------------------------- | ---------------------------------------------------- | --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Contacts                               | Individual people — leads, customers, members        | One of: First Name, Last Name, Email, Phone                     | All plans                                                                                      |
| Opportunities                          | Deals / pipeline records linked to a Contact         | Name, Pipeline, Stage, Contact                                  | All plans                                                                                      |
| Companies                              | Organisations linked to Contacts and Opportunities   | Name (or domain via dedupe rule)                                | All plans                                                                                      |
| Pipelines & Stages                     | Stage configuration for Opportunities                | Pipeline name, ordered Stage list                               | All plans; create before import                                                                |
| Custom Objects                         | Customer-defined record types (Pets, Cars, Policies) | Schema first; primary display field per object                  | All plans, max 10 per Location[10](https://flitstack.ai/migrations/crm/highlevel#source-10)    |
| Notes & Tasks                          | Free-text annotations and follow-ups on Contacts     | Body / title, owner, due date for Tasks                         | All plans; Rich Text limited                                                                   |
| Appointments                           | Calendar bookings tied to Contacts                   | Calendar, Contact, start/end timestamps                         | All plans; calendars created first                                                             |
| Conversations (SMS, email, call, chat) | Inbound and outbound message history                 | Contact, channel, direction, body, timestamp; A2P 10DLC for SMS | All plans; usage-billed                                                                        |
| Transactions & Orders                  | Historical payment and order records                 | Contact, amount, currency, status, source                       | All plans via Payments CSV import[33](https://flitstack.ai/migrations/crm/highlevel#source-33) |
| Custom Values                          | Sub-account-wide key/value merge variables           | Name (auto-generates the merge key)                             | All plans                                                                                      |

Contacts use Email and/or Phone as the dedupe key, controlled by the Sub-account-level Allow Duplicate Contact setting and respected by both the UI import and the Contacts upsert path[21](https://flitstack.ai/migrations/crm/highlevel#source-21). Upsert honours the configured priority: if Email matches one record and Phone another, the platform updates the match on the first field in the configured order and ignores the second to prevent merging two distinct records[21](https://flitstack.ai/migrations/crm/highlevel#source-21).

Opportunities and Companies do not have a single natural unique key, so the practical pattern is to either let GHL assign Record IDs and store them back in the source after first import, or to create a custom field of type Single Line Text with Unique Field enabled and use it as your external ID.

Unique Fields can be flagged on a Custom Object field at creation — downgrading is permitted but irreversible — and the limit is 10 unique fields per object, enforced across UI, Workflows and Forms[11](https://flitstack.ai/migrations/crm/highlevel#source-11).

Custom field types in GoHighLevel are constrained but well-defined. Plan your mapping spreadsheet against the catalogue below.

| Field type                             | Limit                                                                                         | Notes                                                                                                                   |
| -------------------------------------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Single Line Text / Multi Line Text     | Standard text storage                                                                         | Unique-field eligible on Custom Objects (Single Line only)[11](https://flitstack.ai/migrations/crm/highlevel#source-11) |
| Number / Phone                         | Numeric / E.164 phone                                                                         | Both eligible for Unique Field flag[11](https://flitstack.ai/migrations/crm/highlevel#source-11)                        |
| Email                                  | Email address validation                                                                      | Validated on form/import entry                                                                                          |
| Date Picker                            | Date-only                                                                                     | Stored without timezone; UTC midnight by convention                                                                     |
| Dropdown (single)                      | Single-select picklist                                                                        | Pre-create exact values; map by display label, not ID[40](https://flitstack.ai/migrations/crm/highlevel#source-40)      |
| Dropdown (multiple) / Checkbox Group   | 50+ options, no practical cap[39](https://flitstack.ai/migrations/crm/highlevel#source-39)    | Multi-select; semicolon-delimited on CSV import                                                                         |
| Radio Select / URL                     | Standard input types                                                                          | Field-object scope cannot be changed after creation[39](https://flitstack.ai/migrations/crm/highlevel#source-39)        |
| File Upload (Custom Field on Contacts) | Per-record file storage                                                                       | Cannot bulk-load via CSV; upload via the UI one-by-one[62](https://flitstack.ai/migrations/crm/highlevel#source-62)     |
| Custom Objects per Location            | 10 per Location across all plans[10](https://flitstack.ai/migrations/crm/highlevel#source-10) | Plus 10 unique fields per Custom Object[11](https://flitstack.ai/migrations/crm/highlevel#source-11)                    |
| Custom Values (Sub-account)            | Key/value merge variables, foldered                                                           | Auto-generates `custom_values.<key>` merge token[32](https://flitstack.ai/migrations/crm/highlevel#source-32)           |

Relationships are modelled as Associations with optional Association Labels — a Contact labelled Buyer on an Opportunity, or a Pet (Custom Object) labelled Owned By a Contact[9](https://flitstack.ai/migrations/crm/highlevel#source-9) [14](https://flitstack.ai/migrations/crm/highlevel#source-14). Supported relationship types include One-to-One, One-to-N (N ≤ 1,000), One-to-Many and Many-to-Many, with limits visually enforced in the UI[9](https://flitstack.ai/migrations/crm/highlevel#source-9).

**1,000 / 10** Per-association cap / Custom Objects per Location Each Custom Object association is capped at 1,000 linked records, and each Location maxes out at 10 Custom Objects total — limits that catch wholesale, multi-property and family-tree use cases the moment the data set scales[10](https://flitstack.ai/migrations/crm/highlevel#source-10) [14](https://flitstack.ai/migrations/crm/highlevel#source-14).

Standard objects (Contacts, Opportunities, Companies) and Custom Objects all participate in Associations the same way, including cross-object Workflow actions like Add Associated Records to Workflow and Find Object Record by Record ID, External ID or field filter[14](https://flitstack.ai/migrations/crm/highlevel#source-14). There is no native cascade-delete from a parent to its associated children — you build that behaviour into a Workflow if your source platform relied on it.

## Pre-migration prep — the work before you touch GoHighLevel

*What must be true on the source, the destination, and across the team before the first row hits the GHL import wizard.*

The single best predictor of a clean GoHighLevel migration is how much work you do on the source side before the first import button is pressed. Practitioners running CRM consolidations report that the bulk of post-go-live cleanup traces directly to a dirty source export — duplicate emails, mixed-case domains, unresolved owners, picklist values that do not exist on the destination.

> Treat the source export as raw material. Normalise it once, outside GoHighLevel, and the import becomes a non-event.

That means email lowercased, phone normalised to E.164, dropdown values converted to exact GHL picklist labels, dates in a consistent format, owners resolved to GoHighLevel user emails, and historical activity restructured into Notes — since GHL has no first-class historical-activity import beyond Notes and Transactions.

### Source-side prep

- Audit and dedup the source database before export. GHL's native merge tool keeps Master record data and permanently discards the Child contact's conflicting fields, so resolving duplicates upstream is safer than relying on post-import merges[42](https://flitstack.ai/migrations/crm/highlevel#source-42) [45](https://flitstack.ai/migrations/crm/highlevel#source-45).
- Normalise emails to lowercase and phones to E.164 before export — practitioners report 5% exact-email duplicate rates and 10-25% fuzzy-match false positives on B2B contact lists, both of which break GHL's email/phone dedupe priority logic.
- Convert source dropdown values to the exact GHL picklist labels for every dropdown field. GHL maps by display label, and an unknown value is imported as blank with no row-level error.
- Stamp a stable external ID on every record — UUID or the source primary key — and store it in a GHL Single Line Text field flagged Unique for re-runs and reconciliation[11](https://flitstack.ai/migrations/crm/highlevel#source-11).
- Decide what is in scope for historical activities. Calls, emails and meetings older than \~12-24 months are usually best represented as a single summary Note per contact rather than one Note per row.

### Destination-side prep

- Create a Sandbox account from the Marketplace Developer Portal under Testing → Create App Test Account before touching production. Sandbox accounts are isolated and throttled — the right place to dry-run the import flow before it touches the live Sub-account[12](https://flitstack.ai/migrations/crm/highlevel#source-12).
- Provision Users at the Agency level, set permission levels, and assign each User to the Sub-accounts they need. Owner assignment during CSV import requires a valid HighLevel user email — unresolved rows land unowned and silently break owner-based Workflows[40](https://flitstack.ai/migrations/crm/highlevel#source-40).
- Pre-create every Custom Field on the right object with the right type — field-to-object scope cannot be changed after creation[39](https://flitstack.ai/migrations/crm/highlevel#source-39). Naming a custom field with the substring `score` triggers automatic numeric-scoring in Forms, Surveys and Quizzes, which is often unexpected[38](https://flitstack.ai/migrations/crm/highlevel#source-38).
- Build Pipelines and Stages before importing Opportunities — GHL rejects rows whose Stage does not exist on the named Pipeline. If consolidating multiple source pipelines, keep them separate for 90+ days post-go-live, then merge once reporting has stabilised.
- Define Custom Objects, primary fields, unique fields, and Associations before importing any records — Custom Object bulk import requires the schema to exist with all fields created[35](https://flitstack.ai/migrations/crm/highlevel#source-35).
- Register A2P 10DLC for SMS through Settings → Phone Numbers → Trust Center the moment the Sub-account is created. Brand plus Campaign registration plus carrier vetting typically takes 1-3 weeks; LC Phone cannot send any SMS until 10DLC is approved.

### People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — 24-72 hours for a single Sub-account, 1-2 weeks for an Agency moving 50+ client Sub-accounts — and communicate it to every department touching the source. Train Sub-account Admins on Contacts, Opportunities, Conversations and Workflow basics before go-live, not after.

A small-business migration runs one to three business days; an agency rollout across dozens of Sub-accounts with Snapshots runs two to six weeks.

## Import mechanisms: UI wizard, CSV, and Snapshots

*Multiple paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall.*

GoHighLevel exposes several load paths and the right one depends on dataset size, object mix, Sub-account count, and whether the migration needs to be repeatable. The UI Import Wizard covers most one-shot migrations under a few hundred thousand records. Snapshots clone configuration (not records) across Sub-accounts. Third-party tools sit on top.

### UI Import Wizard

The native CSV importer lives at Contacts → Bulk Actions → Import Contacts, with separate object-specific flows for Opportunities, Companies and Custom Object records reached from the corresponding object index page[51](https://flitstack.ai/migrations/crm/highlevel#source-51) [8](https://flitstack.ai/migrations/crm/highlevel#source-8) [35](https://flitstack.ai/migrations/crm/highlevel#source-35).

Each wizard is a multi-step flow: upload file → choose mode (Create only, Update only, Create + Update) → map CSV columns to GHL fields with preview data → review and start the import[8](https://flitstack.ai/migrations/crm/highlevel#source-8) [35](https://flitstack.ai/migrations/crm/highlevel#source-35). Once running, the import is monitored under Bulk Actions, where you can pause, resume or cancel[35](https://flitstack.ai/migrations/crm/highlevel#source-35).

Limits are tight relative to other CRMs. The format is CSV only — Excel `.xlsx` and Google Sheets are rejected by the Companies and Custom Object importers[8](https://flitstack.ai/migrations/crm/highlevel#source-8) [35](https://flitstack.ai/migrations/crm/highlevel#source-35). Only Sub-account Admin users can run imports[51](https://flitstack.ai/migrations/crm/highlevel#source-51). The CSV must be a single sheet, must have required fields populated, must use one Primary Column, and dropdown values must match the GHL field options exactly. File size caps sit at 100 MB on paid tiers, 50 MB on lower tiers[44](https://flitstack.ai/migrations/crm/highlevel#source-44).

### Snapshots

Snapshots are GoHighLevel's template-clone mechanism — they capture configuration (Custom Fields, Pipelines, Workflows, Funnels, Email/SMS templates, Calendars, Triggers, Custom Values) from a source Sub-account and apply it to one or more destinations in a single load[43](https://flitstack.ai/migrations/crm/highlevel#source-43). Snapshots do not move records — they only move structure, so they are the wrong tool for a data migration but the right tool when an agency is standing up 25 client Sub-accounts that should share the same Workflows.

Snapshot push-updates can be reverted at the bulk-action level, but there is no native rollback for the original snapshot apply[49](https://flitstack.ai/migrations/crm/highlevel#source-49).

### Third-party staging tools

ETL and iPaaS vendors — Make.com, Zapier, n8n, Workato — are used either for reverse-ETL through a warehouse, or for one-shot transformation that handles dedup, picklist remapping and owner-email resolution before the cleaned file hits the UI wizard. Marketplace apps like Import Custom Fields fill the multi-object bulk gap[55](https://flitstack.ai/migrations/crm/highlevel#source-55).

Under 10,000 records on standard objects → UI Wizard. 10,000–100,000 → UI Wizard in batched CSVs. Cloning configuration across Sub-accounts → Snapshots.

## Mapping your data into GoHighLevel

*The longest section — because field mapping is where almost every migration that fails actually breaks.*

Mapping is where every migration earns its scars. The schema decisions in your mapping spreadsheet determine whether reports work on day two, Workflows fire correctly on day five, and your sales team trusts the data on day thirty.

Work object by object in GHL's dependency order: Companies first, then Contacts, then Opportunities (which require an existing Contact), then Custom Object records, then Notes/Tasks/Appointments, then Transactions and Orders.

### Contacts

| Source                    | Destination                                      | Note                                                                                                                                    |
| ------------------------- | ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
| email                     | email (unique-field-eligible)                    | Lowercase before import; honours Allow Duplicate Contact setting on upsert[21](https://flitstack.ai/migrations/crm/highlevel#source-21) |
| first\_name / last\_name  | firstName / lastName                             | GHL accepts either via Contact ID; one of name/email/phone required[51](https://flitstack.ai/migrations/crm/highlevel#source-51)        |
| phone                     | phone                                            | Normalise to E.164 before import; phone is also a dedupe key candidate                                                                  |
| company\_name             | companyName field OR Company-object association  | Decide upfront — flat text field vs full Company record                                                                                 |
| owner / assigned\_to      | Assigned User                                    | Map by HighLevel user email; missing email → unowned row[40](https://flitstack.ai/migrations/crm/highlevel#source-40)                   |
| lifecycle / stage         | Tag OR custom Dropdown field                     | GHL has no native lifecycle property; Tags or a custom dropdown are the patterns                                                        |
| lead source / utm\_source | source (system field) OR custom Single Line Text | `source` is settable on Contacts via CSV                                                                                                |
| created\_at               | Custom Date field (e.g. legacy\_created\_at)     | GHL `dateAdded` is system-managed and stamped to import day                                                                             |
| tags                      | tags (array)                                     | Comma-delimited on CSV import; create-on-the-fly is allowed                                                                             |

### Opportunities and pipelines

Recreate every Pipeline and every Stage in GoHighLevel before importing Opportunities. Each Opportunity row requires Pipeline name (or ID), Stage name (or ID), Opportunity name, monetary Value, and a Contact reference (by Contact ID, email or phone). Rows that target a non-existent Stage on the named Pipeline are rejected during the CSV preview step.

Opportunity stage history is not preserved by the import — only the current Stage lands. If you need stage-transition history for reporting, export the source transition timestamps and store them in custom Date fields like `stage_entered_at_<stage>`.

| Source                         | Destination                             | Note                                                                                         |
| ------------------------------ | --------------------------------------- | -------------------------------------------------------------------------------------------- |
| deal\_name / opportunity\_name | name                                    | Required                                                                                     |
| stage / pipeline\_stage        | Stage (must exist on named Pipeline)    | Pre-create Pipelines and Stages[40](https://flitstack.ai/migrations/crm/highlevel#source-40) |
| amount / value                 | monetaryValue                           | Number; strip currency symbols before import                                                 |
| close\_date                    | Custom Date field (e.g. close\_date)    | No native closeDate on GHL Opportunities — store in custom field                             |
| owner                          | assignedTo                              | Map by user email; controls Opportunity dashboards                                           |
| primary\_contact               | Contact reference (required)            | By Contact ID, email or phone; rows without a Contact are rejected                           |
| account / company              | Company association                     | Set via the Associations step or a follow-up update import                                   |
| source\_record\_id             | Custom Single Line Text, flagged Unique | Your reconciliation key for re-runs and rollback                                             |

### Companies

Companies are imported via CRM → Import / Export → Bulk Import Companies, CSV only, with the same three modes — Create, Update, Create + Update[8](https://flitstack.ai/migrations/crm/highlevel#source-8). Map `company_name` to GHL's primary field and choose your unique field (typically a custom `domain` Single Line Text flagged Unique, or a `source_company_id` external ID).

Decide on the Update Empty Values behaviour — by default, the import will not overwrite existing non-blank values with incoming blanks, which protects partially-enriched records from being wiped by an incomplete refresh[8](https://flitstack.ai/migrations/crm/highlevel#source-8).

### Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Migrate only the fields used by an active Workflow, Form, or Report in the last 12 months. Excess fields slow the field picker, weaken Smart List performance, and waste storage.

For dropdown fields whose source values do not match the destination, either extend the destination dropdown with the missing values, collapse adjacent values during transform, or introduce a parallel Single Line Text field that holds the legacy value verbatim.

Source formula or calculated fields do not import — GHL has no formula-field type. Pre-compute the value in the export step and store it in a Number or Single Line Text custom field. Salesforce Record Types have no GHL equivalent — segment via Tags or a custom Dropdown instead.

### Historical activities — calls, emails, notes, tasks

GoHighLevel has no first-class historical-Activity import equivalent to HubSpot's Activity Date field. Practitioners load historical call/email/meeting records as Notes on the corresponding Contact with the original timestamp prepended in the body (e.g. `[2024-03-12 10:42 - Inbound Call - 12m]`), accepting the Note's `createdAt` will be stamped to import day[61](https://flitstack.ai/migrations/crm/highlevel#source-61). Future-dated meetings with operational meaning are recreated as Appointments on the appropriate Calendar.

Email threads rarely round-trip cleanly — GHL's Conversations module is purpose-built for new threads, with no public bulk-import path for Conversations history. Store the last 12 months of email subject lines and metadata as Notes, and link to a static archive (S3, Google Drive) for the full body if audit retention is required.

### Files and attachments

Attachments cannot be bulk-loaded from CSV. The supported per-record path is a File Upload custom field on the Contact, populated by uploading the file via the UI one record at a time[62](https://flitstack.ai/migrations/crm/highlevel#source-62). For SMS attachments or email attachments above 20 MB, GHL auto-moves the file to the Media Library and inserts a media-library link rather than attaching the binary inline[60](https://flitstack.ai/migrations/crm/highlevel#source-60).

Per-file size caps for documents (PDF, Word, Excel, PowerPoint, CSV, ZIP) sit at 100 MB on paid tiers and 50 MB on lower tiers, applied uniformly to Media Library uploads[44](https://flitstack.ai/migrations/crm/highlevel#source-44). For large attachment estates (hundreds of GB across thousands of contacts), the pattern most teams adopt is: keep originals in S3 or Google Drive, store a deep link in a custom URL field, and only inline-upload the most-referenced subset.

### Audit trail, ownership and original timestamps

GoHighLevel system properties — `dateAdded` on Contacts, Opportunity `createdAt`, Custom Object record `createdAt` and `updatedAt` — are platform-managed and cannot be overridden during CSV import. Rows that arrive on May 1 are stamped May 1 even if the source record was created in 2019.

To preserve the original audit trail, create custom Date fields like `legacy_created_at`, `legacy_updated_at`, and a `legacy_created_by` Single Line Text holding the source user email on every object before import, and populate them from the source export.

Owner assignment only works if the Owner column resolves to a valid HighLevel User email at import time; unresolved rows land unowned with no row-level error[40](https://flitstack.ai/migrations/crm/highlevel#source-40). Audit Logs are retained for 60 days at the Sub-account level under Settings → Audit Logs — long enough to investigate post-import discrepancies but not a permanent compliance archive[92](https://flitstack.ai/migrations/crm/highlevel#source-92).

### CRM-specific: workflows, A2P 10DLC, lead scoring, calendar sync

Workflows do not import from any source platform — every Automation, Campaign, Sequence, Drip, or Salesforce Flow is rebuilt by hand in GHL's visual Workflow builder. This is the single largest line item in any GHL migration. Audit the source's automations filtered by last-triggered-in-90-days, document each as a flowchart, then rebuild under Automation → Workflows.

A2P 10DLC SMS registration must be completed before LC Phone can send any text message to US numbers. Submit Brand Registration with EIN, business address and contact, then Campaign Registration with sample message templates and opt-in flow; carrier vetting and approval takes 1-3 weeks. Build this lead time into the cutover plan or your sales team will go live without SMS.

Lead scoring is not a first-class GHL object. Build a numeric custom field `lead_score` plus a Workflow that increments it on trigger events (form fill, email open, page view). Historical scores land in `legacy_lead_score` and the new field accrues forward.

Email and Google/Outlook Calendar sync is set up per-User under Calendars → Settings → Connections after Users are provisioned and before go-live — but do not enable two-way sync during the import window or the connector will backfill duplicate Appointments against the same Contacts you are loading[140](https://flitstack.ai/migrations/crm/highlevel#source-140) [148](https://flitstack.ai/migrations/crm/highlevel#source-148).

## The pitfalls that derail GoHighLevel migrations

*Nine specific failure modes — ranked by impact, each tied to the exact GoHighLevel mechanism that breaks.*

**high A2P 10DLC SMS registration left to the last week**

LC Phone cannot send a single SMS to a US number until A2P 10DLC Brand and Campaign registration are approved by carriers — a process that takes 1-3 weeks and requires EIN, business address, sample message templates and opt-in evidence. Teams that schedule cutover two weeks out and submit 10DLC the week before discover at go-live that their sales team has been migrated to a phone system that cannot text anyone. Submit 10DLC the same week the Sub-account is created.

**high Custom Object association cap of 1,000 records**

Each GoHighLevel Custom Object association — Contact ↔ Custom Object, Custom Object ↔ Custom Object — is capped at 1,000 linked records per association, which practitioners report making the feature unusable when a Contact has 1,000+ associated Properties, Vehicles, Policies or Family Members[14](https://flitstack.ai/migrations/crm/highlevel#source-14). Once you cross the ceiling, additional associations silently fail. Detect this in the source export, restructure relationships, or split the parent record before import.

**high Custom Object limit of 10 per Location**

Every Location (Sub-account) maxes out at 10 Custom Objects across all plans, raised in October 2025 from a previous lower cap[10](https://flitstack.ai/migrations/crm/highlevel#source-10). Agencies running verticals like insurance (Policies, Claims, Beneficiaries, Carriers…), real estate (Properties, Listings, Showings, Offers, Inspections…) or healthcare quickly hit the ceiling. Audit the source schema against the 10-object budget before signing the migration scope — if you need 15 Custom Objects, GoHighLevel is the wrong destination platform and finding that out before cutover is cheap.

**high Workflow rebuild scope underestimated by 5-10x**

No source platform's Automations, Sequences, Campaigns, Flows or Process Builders import to GoHighLevel. Every active automation is rebuilt by hand in the visual Workflow builder, including triggers, actions, conditional branches, wait steps, and SMS/email templates. Teams that quote a Salesforce-to-GHL migration based on contact count alone miss that 200 Flows is several weeks of rebuild work per Sub-account. Inventory active automations (filter source by last-triggered-in-90-days) and quote separately on Workflow rebuild[72](https://flitstack.ai/migrations/crm/highlevel#source-72).

**high createdAt and dateAdded cannot be overridden**

GoHighLevel's system timestamps — Contact `dateAdded`, Opportunity `createdAt`, Custom Object `createdAt` and `updatedAt`, Note `createdAt`, Appointment `createdAt` — are platform-managed and ignored if you send them during import. Teams discover this on day two when Smart Lists filtered by Date Added return everything stamped to import day[96](https://flitstack.ai/migrations/crm/highlevel#source-96). Create `legacy_created_at` and `legacy_updated_at` custom Date fields on every object, populate them from the source export, and rewrite all historical-period Smart Lists to use the legacy fields.

**medium Contact merge permanently discards Child record fields**

GoHighLevel's deduplication merge tool keeps the Master record's data and permanently discards conflicting values from the Child record unless you manually pick fields during the review step. The merge is irreversible — there is no undo[45](https://flitstack.ai/migrations/crm/highlevel#source-45) [147](https://flitstack.ai/migrations/crm/highlevel#source-147). Teams running post-import merges on a few hundred duplicates without per-field review lose data they did not realise was on the Child record. Always dedup upstream where you can inspect both rows, or use field-level conflict selection on every merge.

**medium CSV-only imports reject Excel and Google Sheets**

The Companies and Custom Object bulk import wizards accept CSV (.csv) only — Excel `.xlsx` and Google Sheets are rejected at the upload step[8](https://flitstack.ai/migrations/crm/highlevel#source-8) [35](https://flitstack.ai/migrations/crm/highlevel#source-35). Teams handing the migration to a non-technical Sub-account Admin who exports from Excel discover this at upload and lose a day to format conversion. The Google-Sheet MIME type is supported in the Media Library[44](https://flitstack.ai/migrations/crm/highlevel#source-44) but not in the import wizard. Document the CSV requirement in the runbook.

**medium GDPR data residency — no EU hosting option**

GoHighLevel is hosted on US infrastructure with EU-U.S. Data Privacy Framework certification and SCCs for cross-border transfers, but there is no EU data-residency option — all customer data sits in US data centres regardless of where the agency or end-customer is based[120](https://flitstack.ai/migrations/crm/highlevel#source-120) [122](https://flitstack.ai/migrations/crm/highlevel#source-122). EU agencies under strict residency requirements (German BDSG, French CNIL, Italian Garante guidance) need to evaluate this before migrating, and the long-running self-host request thread remains under review with no committed delivery[122](https://flitstack.ai/migrations/crm/highlevel#source-122).

**low HIPAA add-on is one-way and costs $297/mo**

HighLevel accounts are not HIPAA-compliant by default. The HIPAA Compliance package is an account-wide add-on at US$297 per month enabling ePHI encryption, BAA signing, audit logging and MFA enforcement[129](https://flitstack.ai/migrations/crm/highlevel#source-129). Once enabled it applies to every Location and cannot be disabled — there is no downgrade path. Healthcare-adjacent agencies need to budget the line item and confirm it is enabled before any PHI lands on the platform, because adding it later does not retroactively secure historical data.

## Validation and cutover

*What to verify after the import job, in what order — and how to fail safely when something is wrong.*

Validation is the bridge between the import finishing and users being allowed in. The pattern that works on GoHighLevel migrations is three-stage: a test load of 10 percent of records with stakeholder spot-checks, the full load with real-time Bulk Actions monitoring, and a 30-day post-migration data-quality audit. The most reliable signal is having Sub-account Admins verify their own records — they know what right looks like better than any reconciliation script.

Build a reconciliation spreadsheet that compares source and destination on each count below. Anything outside a 0.5 percent variance gets investigated before users get login access.

- Total Contacts imported vs source — minus deliberately excluded rows (role-based emails, unsubscribed lists, opted-out contacts).
- Total Companies imported vs source — checking that domain-based or name-based dedupe did not over-merge distinct organisations.
- Total Opportunities per Pipeline per Stage vs source, plus sum of `monetaryValue` per Pipeline — a non-trivial dollar variance usually signals a stage-mapping error or a currency-precision drop.
- Total Notes per Contact vs source — a date-bucketed histogram comparison confirms historical-activity-as-Notes round-tripped.
- Custom Object record counts per object vs source — and association counts per Contact / per Custom Object record to confirm no parent crossed the 1,000-association cap[14](https://flitstack.ai/migrations/crm/highlevel#source-14).
- Owner distribution — group by `assignedTo` and confirm no record landed unowned that should not have[40](https://flitstack.ai/migrations/crm/highlevel#source-40).
- Unique-field integrity — count distinct emails on Contacts, distinct domains on Companies, distinct external IDs on Opportunities; any duplicates indicate the dedup transform missed cases.
- Tag distribution — confirm Tags created during import match the source's expected segmentation taxonomy.

On top of reconciliation, run a manual spot-check: pick 30 random Contacts across Sub-accounts and verify each field against the source UI. Pick five high-value Opportunities and trace the full association graph — primary Contact, Company, Custom Object children, Notes, Appointments. If a non-trivial discrepancy shows up in three or more, halt the load, fix the root cause, and re-import affected rows by external ID.

GoHighLevel ships Restore Deleted Contacts at Contacts → Restore, which centralises records deleted within the retention window so you can recover them without re-importing[100](https://flitstack.ai/migrations/crm/highlevel#source-100). This is a safety net for accidental bulk-delete but it is not a bulk-rollback for an import gone wrong — there is no native undo the last import button.

The real rollback strategy remains: export everything from the source to S3 before the import starts, stamp every imported row with an `import_batch_id` custom field, and if catastrophe strikes, run Bulk Actions → Delete filtered by that batch ID and re-import from the cleaned source. Third-party backup tools like HighGuard.cloud add daily snapshots with one-click restore, but they are an add-on rather than a default.

Cutover sequencing: (1) source goes read-only; (2) final delta export captures changes during the test-import window; (3) delta is imported; (4) reconciliation runs; (5) two-way calendar sync is enabled per User after validation passes[148](https://flitstack.ai/migrations/crm/highlevel#source-148); (6) Users get login access and a 48-hour hyper-care window with the migration lead on call; (7) source decommission is scheduled for 30 to 90 days out, never the same day.

## Migration partners and tools

*Certified Admins, Developer Partners, iPaaS vendors, specialist migration shops — what each is good for and how to choose.*

HighLevel's official ecosystem splits into two directories: the Certified Admin Directory of practitioners who install and operate GHL Sub-accounts for end-clients, and the Developer Partner Program of vetted shops that build custom integrations and ship Marketplace apps[110](https://flitstack.ai/migrations/crm/highlevel#source-110). Certified Admins fit one-shot migrations; Developer Partners fit ongoing iPaaS-style work against a warehouse, ERP or vertical SaaS.

Specialist shops with explicit migration practices include HashStudioz, ClonePartner, The Funnels Guys, GetAutomized, AutomateToGrow and Expert Level — each runs fixed-scope packages alongside ongoing retainer services. HighLevel Virtual offers white-label staffed-team packages starting at $439/month for 40 hours, which some agencies use to run their entire client-migration backlog.

On the iPaaS side, Make.com, Zapier, n8n, Workato and Pabbly Connect all carry GoHighLevel connectors. Their role is the staging layer into a warehouse, the field-conversion layer that maps dropdowns to GHL picklists, and post-migration the ongoing-sync layer. Marketplace apps like Import Custom Fields by Innexum fill the gap left by GHL not shipping a native multi-object bulk loader[55](https://flitstack.ai/migrations/crm/highlevel#source-55).

Managed-migration cost ranges vary widely. A clean Pipedrive-to-GHL or ActiveCampaign-to-GHL move of under 25,000 contacts with no Custom Objects, no historical activity preservation and one Sub-account often lands in the $2,000–$8,000 range with a setup fee plus per-object pricing.

A Salesforce-to-GHL or HubSpot-to-GHL project with Opportunity history, multiple Pipelines, Custom Objects, Workflow rebuilds and an Agency-wide rollout across 25 client Sub-accounts typically runs $25,000–$120,000, with the upper end driven by Sub-account count, Workflow rebuild scope and A2P 10DLC submissions across all client brands.

For teams that want to outsource the migration end-to-end, FlitStack specialises in GoHighLevel migrations and handles the Agency-versus-Sub-account architecture decisions, field mapping, dropdown-value conversion, Custom Object schema design within the 10-per-Location cap, Workflow rebuild scoping, and A2P 10DLC Brand and Campaign submission described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on record count, Sub-account count and source platform, with separate line items for Custom Objects, Workflow rebuild scope and historical-activity-as-Notes depth so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Certified Admin, a Developer Partner for the integration work, an iPaaS-first approach, or a specialist migration vendor. \[Explore FlitStack →]\(/contact)

In this guide

## HighLevel migration checklist

An exhaustive, phased task list for moving CRM data into GoHighLevel's Agency / Sub-account / Location hierarchy with workflows, A2P 10DLC SMS, and Custom Objects rebuilt from scratch. Typical timeline: 4–12 weeks.

0\. Decide & Plan 9 tasks

- **Document the in-scope object list explicitly.** Confirm which standard objects (Contacts, Opportunities, Companies) and which Custom Objects are in scope; GoHighLevel caps Custom Objects at 10 per Location, so prune ruthlessly.*If skipped: Mid-migration discovery that a tenth Custom Object pushes scope past the per-Location cap forces a destructive rethink of the data model.*
- **Decide the Agency / Sub-account / Location hierarchy up front.** Map each operating unit, brand, or tenant in the source to a specific Sub-account/Location in GoHighLevel; this hierarchy controls billing and isolation.*If skipped: Choosing the wrong granularity forces a rebuild later because Workflows, Custom Fields, and Snapshots are scoped to a single Location.*
- **Define the historical-data scope in writing.** Pick a cut-off date for contacts, opportunities, notes, calls, and emails; decide whether closed-lost opportunities and stale contacts come over at all.*If skipped: An open-ended historical scope balloons the validation effort by an order of magnitude.*
- **Decide on the HIPAA add-on before any ePHI moves.** GoHighLevel's HIPAA add-on is US$297/month, applies account-wide once enabled, and cannot be disabled; if any Sub-account handles ePHI, enable it before importing.*If skipped: Loading ePHI into a non-HIPAA account creates a documented compliance breach the moment the import job runs.*
- **Confirm data-residency constraints with legal.** GoHighLevel is hosted on US infrastructure with no EU data residency option; capture sign-off under EU-US Data Privacy Framework or document a blocker.*If skipped: EU-based contacts loaded without a documented transfer mechanism expose the business to GDPR enforcement after go-live.*
- **Identify the single accountable migration owner (DRI).** Name one person responsible for go/no-go decisions, sign-off on each phase exit, and post-cutover triage.
- **Document the success criteria for cutover.** Write down what specifically must be true to declare the migration complete: object counts within tolerance, pipeline value reconciled, all Workflows triggering, no failed Bulk Action errors.*If skipped: Without explicit exit criteria, cutover slips indefinitely while small issues block sign-off.*
- **Set the cutover window and source-system freeze date.** Pick a low-traffic window (often a weekend) and announce the exact UTC start/end times to everyone with write access to the source system.
- **List explicitly out-of-scope items.** Capture what is not coming over (legacy custom apps, deprecated reports, archived calls before X date) so it cannot reappear as scope creep later.

1\. Pre-Migration Prep 24 tasks

- **Run a deduplication scan on source contacts using email as the match key.** Normalize all email addresses to lowercase first; case variants are invisible to dedup tools until the email column is normalized.*If skipped: Duplicates carried into GoHighLevel trigger merge logic that permanently loses Child-record field values during conflict resolution.*
- **Run a second dedup pass on phone number using E.164 format as the match key.** Strip formatting, prepend country code, and re-scan; GoHighLevel's Allow Duplicate Contact setting can key on email and phone together.*If skipped: Phone-keyed duplicates surface only after the upsert step silently merges or skips records mid-import.*
- **Standardize country codes against GoHighLevel's accepted country list.** GoHighLevel publishes an explicit accepted-countries list for contact upserts; values outside the list fail the import row.*If skipped: Non-conforming country values fail individual rows without aborting the job, leaving silent partial imports.*
- **Standardize phone numbers to E.164 across the source.** Phone fields that are not E.164 fail the CSV import row-by-row with formatting errors.
- **Resolve all records with missing required fields.** GoHighLevel imports require at least one of name, email, or phone on Contacts; rows missing all three are rejected.
- **Export current record counts per object as the migration baseline.** Save counts for Contacts, Opportunities, Companies, Pipelines, Notes, Calls, Tasks, Appointments, and each Custom Object.*If skipped: Without a baseline, post-migration reconciliation cannot prove completeness.*
- **Audit picklist / dropdown values in the source for inconsistencies.** Catalog every distinct value per picklist field; collapse synonyms ("Closed-Won" vs "Won") into a single canonical value before mapping.*If skipped: Unmapped picklist variants become free-text junk in GoHighLevel's Dropdown fields and break Workflow trigger conditions.*
- **Flag any custom field name in the source that contains the word "score".** GoHighLevel hardcodes any custom field whose name contains "score" as a numeric scoring element across Forms, Surveys, and Quizzes; rename before importing if the field is not actually numeric.*If skipped: Text data loaded into an auto-detected scoring field is rejected or coerced silently.*
- **Identify any source field that exceeds GoHighLevel's destination character limits.** Note long-text fields that may need truncation or split-into-Notes treatment in Phase 3.
- **Provision the production Sub-account/Location and a parallel Sandbox account.** Use GoHighLevel's Sandbox/Test Account option so the test environment is isolated from production data.*If skipped: Skipping a Sandbox forces every test load to run against production and pollute production data.*
- **Provision all destination users with the correct Sub-account role.** Create Admin users for the migration team specifically; only Admin role can run Bulk Imports.*If skipped: Non-admin users cannot execute imports, blocking cutover until permissions are corrected.*
- **Configure the Sub-account timezone, currency, and business hours.** Settings → Business Profile; these affect timestamp interpretation on every imported record.*If skipped: A wrong timezone shifts every imported appointment and activity by hours and silently breaks Workflow timing.*
- **Create every Custom Field on Contacts before importing any contact data.** Settings → Custom Fields → Contacts; GoHighLevel supports Short Text, Long Text, Dropdown (single/multi), Date Picker, Phone, Email, Radio, Checkbox Group, URL, and Number.*If skipped: Importing into a Custom Field that does not yet exist silently drops the column on every row.*
- **Create every Custom Field on Opportunities before importing pipeline data.** Contact and Opportunity Custom Fields are separate object scopes and cannot be converted between objects after creation.*If skipped: Discovering a misplaced field after the import means recreating it and re-running the load.*
- **Create each Custom Object with its full field set and unique-field flags.** Mark unique fields at creation time (up to 10 per Custom Object); downgrading a unique field to non-unique is irreversible.*If skipped: Missing the unique-field flag at creation lets duplicates accumulate that cannot be retroactively blocked.*
- **Create hidden Custom Fields to hold source primary keys.** Add fields like \`source\_contact\_id\`, \`source\_opportunity\_id\`, \`source\_company\_id\` as the reconciliation crosswalk for validation and rollback.*If skipped: Without preserved source IDs, you cannot reconcile records or roll back a bad load.*
- **Create all Pipelines and Pipeline Stages before importing Opportunities.** Each Opportunity row's stage value must match an existing stage by exact name or ID.*If skipped: Rows with unmatched stage names fail the CSV import and require re-mapping and re-upload.*
- **Decide and create the Tag taxonomy.** Map source labels (Lifecycle Stage, Lead Status, Record Type) to Tags up front; Tags are flat and reused across the Sub-account.
- **Configure the Allow Duplicate Contact setting before any contact load.** Settings → Business Profile → Duplicate Contact behavior; pick the field priority (email first, phone second, or both) that matches your dedup decision.*If skipped: The upsert step obeys this setting; a wrong configuration silently merges or duplicates records.*
- **Pause all destination Workflows, triggers, and integrations.** Disable every Workflow that fires on contact create, opportunity create, or tag-add; otherwise the import triggers notification storms.*If skipped: Active Workflows on import fire SMS, email, and outbound actions on every imported row, generating spam and burning A2P quota.*
- **Register A2P 10DLC brand and campaigns before any phone number is provisioned.** LC Phone SMS requires A2P 10DLC registration for US numbers; provisioning ahead of registration blocks outbound SMS for days.*If skipped: Unregistered campaigns are blocked by carrier filters, killing the entire SMS channel after cutover.*
- **Announce the source-system freeze window to all users with write access.** State the exact freeze time, what "read-only" means, and where to log issues during the window.
- **Schedule a destination-platform training session per role.** Sales, marketing, and admin teams each need a different walkthrough; record sessions for asynchronous viewing.
- **Designate first-responder owners for the first 48 hours post-cutover.** Name a primary and backup for each functional area (Contacts, Opportunities, Conversations, Workflows).

2\. Source Export 14 tasks

- **Export Contacts with every standard and custom field.** Include source primary key, email, phone, all custom fields, owner, created date, last modified date, and Tags/labels.*If skipped: A missed column at export time forces a second freeze window later to extract the missing data.*
- **Export Opportunities with full field set and pipeline-stage IDs.** Include the source pipeline ID, stage ID, monetary value, currency, close date, and the contact/account foreign keys.
- **Export Companies/Accounts with primary keys and parent-child relationships.** Capture industry, size, address, owner, and contact-to-company association rows.
- **Export every Custom Object record with its associated foreign keys.** Include the association labels you intend to recreate in GoHighLevel (e.g., Buyer, Account Owner, Assigned Dealer).
- **Export Notes as a separate file keyed to source contact ID.** Capture note body, author, created date, and the contact/opportunity it attaches to.*If skipped: Notes that share a file with Contacts lose their author and timestamp once flattened.*
- **Export Tasks and Appointments as a separate file.** Include due date, owner, completion status, and the contact/opportunity association.
- **Export call history with recordings and transcriptions if available.** Capture call direction, duration, recording URL, transcription text, disposition, and associated contact.
- **Export email history (subject, body, direction, timestamps).** Email threading does not survive most migrations; export per-message metadata so threads can be reconstructed as Notes if needed.*If skipped: Lost email history blinds reps to prior conversations and degrades trust in the new system on day one.*
- **Export the user list with roles, emails, and the source-to-destination owner crosswalk.** Owner IDs must map by ID, not by display name; capture both.*If skipped: Mapping by display name causes silent owner reassignment when two users share a first name.*
- **Export pipeline definitions and stage order from the source.** Capture stage name, position, and probability so Pipelines can be recreated identically before Opportunities load.
- **Export attachment file inventory: which files attach to which records.** Capture file name, MIME type, byte size, source URL, and the record ID it attaches to; binaries themselves are downloaded separately.
- **Download all attachment binaries to a staging location.** GoHighLevel CSV uploads cap file size at 100MB on standard plans and 50MB on lower tiers; flag any source attachment that exceeds the cap.*If skipped: Binaries discovered missing after cutover are usually unrecoverable from a frozen or decommissioned source.*
- **Screenshot or document every source automation, sequence, and workflow.** Workflows do not migrate to GoHighLevel and must be rebuilt by hand; capture triggers, actions, branches, wait steps, and merge fields.*If skipped: Automations rebuilt from memory weeks later miss edge-case branches that drove revenue or retention.*
- **Record the UTC timestamp of every export run.** This anchors the cutover delta calculation in Phase 5.

3\. Transform & Map 29 tasks

- **Build a master mapping spreadsheet, one row per source field.** Columns: source object, source field, source type, GoHighLevel object, GoHighLevel field, GoHighLevel type, nullability, transformation rule, required-on-import flag.*If skipped: Without a single source of truth, mappings drift between transforms and validations, producing data that passes import but fails reconciliation.*
- **Pick the upsert key per object explicitly.** Contacts typically use email; Opportunities and Custom Objects should use a unique source primary key stored in a Custom Field.
- **Map every picklist value, source → GoHighLevel Dropdown value.** Use exact string matching, including case; "Closed-Won" and "Closed Won" are different values on import.*If skipped: Mismatched picklist values import as empty cells and break Smart List filters and Workflow conditions.*
- **Decide handling for every source field with no GoHighLevel equivalent.** Choose per field: drop, concatenate into Notes, store in a new Custom Field, or convert to a Tag.
- **Map source Record Types or sub-types to Tags or a Dropdown Custom Field.** GoHighLevel has no Record Type concept; pick the consolidation strategy in advance.
- **Convert source Formula fields to pre-computed values.** GoHighLevel has no formula field; calculate the value in the transform step and store it in a text or number Custom Field.*If skipped: Formulas that auto-update in the source freeze at the migration date in GoHighLevel; reps must know the value is a snapshot.*
- **Replace source Lookup/Master-Detail fields with GoHighLevel Associations.** Map foreign-key references to Association labels between Contacts, Companies, Opportunities, and Custom Objects.
- **Convert all date and datetime fields to ISO-8601 with timezone.** GoHighLevel's CSV import parser expects unambiguous date formats; DD/MM/YYYY and MM/DD/YYYY are common silent-corruption traps.*If skipped: Date ambiguity flips month and day on half the rows and corrupts every downstream report.*
- **Re-encode all text files as UTF-8 without BOM.** Source exports from older systems often arrive as Windows-1252 or UTF-8 with BOM; the BOM breaks CSV header detection.*If skipped: Non-UTF-8 text corrupts accented characters and emoji silently, surfacing as data-quality complaints weeks later.*
- **Escape commas, quotes, and newlines inside text fields.** Per RFC 4180, wrap fields containing commas, double quotes, or line breaks in double quotes and escape internal double quotes by doubling them.*If skipped: Unescaped quotes shift every column to the right starting at the offending row, silently misaligning hundreds of records.*
- **Normalize currency values to GoHighLevel's expected decimal precision.** Strip currency symbols and thousand separators; standardize to a single decimal separator.
- **Truncate long-text fields that exceed destination field caps.** For fields flagged in Phase 1, decide per field: truncate with ellipsis, split into Notes, or skip the row.
- **Split or remove zero-width and control characters.** Tab characters, vertical tabs, and zero-width spaces break CSV parsing in subtle ways.
- **Produce one final CSV per object in the exact column order the import wizard expects.** GoHighLevel's Bulk Import wizard pre-maps columns by header name on the first row; consistent headers eliminate manual mapping per file.
- **Confirm every output CSV is under 100MB.** Bulk Import accepts only \`.csv\`, not \`.xlsx\` or Google Sheets; split larger files into 100MB chunks with consistent headers.*If skipped: A file over the limit is rejected at upload time, eating into the cutover window for resharding.*
- **Decide and document the historical-timestamp strategy.** GoHighLevel's import does not let you override the system Created Date; capture the original via a dedicated \`source\_created\_at\` Custom Field on every record.*If skipped: Without a preserved original timestamp, every imported record looks like it was created on cutover day, destroying historical reporting.*
- **Decide and document the record-ownership strategy.** Choose: map by source-user-ID crosswalk, fall back to a single "Data Migration" user for unmatched owners, or leave ownership unset.*If skipped: Owners assigned by display name silently swap when two source users share a first or last name.*
- **Decide the file-attachment strategy.** Choose: re-upload binaries into the Media Library and link via a file-upload Custom Field, or preserve external storage links in a URL Custom Field.
- **Design the Associations to mirror the source's join tables.** Choose Association labels and cardinality (1:1, 1:N where N ≤ 1000, Many-to-Many) per relationship before any load.*If skipped: The 1,000-record Association cap on Custom Objects can silently truncate large parent records mid-import.*
- **Build the Sub-account and Location hierarchy in the destination Agency.** Create each Sub-account; configure billing and brand settings per Location since Workflows, Pipelines, and Custom Fields are Location-scoped.*If skipped: Loading data into the wrong Location forces a full re-export and re-import because GoHighLevel cannot move records across Locations.*
- **Recreate every Pipeline and Pipeline Stage from the source.** Stage names must match exactly what your transformed Opportunity CSV references.
- **Distinguish Custom Values from Custom Fields and create each in its correct home.** Custom Values are Sub-account-wide key/value pairs (used in templates and Workflows); Custom Fields belong to a specific object and store per-record data. Confusing the two is a top-three cause of broken templates.*If skipped: A reference like \`{{custom\_values.x}}\` rendered against a Custom Field returns blank in every email and SMS.*
- **Document every Workflow that needs to be rebuilt manually.** Workflows do not import from any source platform — they must be rebuilt in GoHighLevel's Automation builder one trigger, action, and branch at a time.*If skipped: Skipping documentation here means rebuilt Workflows lose conditional branches that drove revenue in the source system.*
- **Rebuild Workflow triggers explicitly: Contact Created, Tag Added, Opportunity Stage Changed, Form Submitted.** Each trigger has a different scope; map each source automation trigger to a specific GoHighLevel trigger type before building.
- **Prepare Snapshot templates for any configuration that ships to multiple Sub-accounts.** Snapshots clone Pipelines, Workflows, Custom Fields, Forms, Funnels, and other configuration — but not contact, opportunity, or conversation data.*If skipped: Teams expecting Snapshots to move data discover at cutover that contacts must be CSV-imported into each Sub-account separately.*
- **Register A2P 10DLC brand and campaigns and verify approval status.** Brand verification can take days; campaign approval is per use case (Marketing, Account Notification, Customer Care). Do not import contacts you plan to text before campaigns are Approved.*If skipped: Sending SMS via an unregistered or pending campaign is filtered by carriers and damages sender reputation.*
- **Decide and rebuild lead scoring from scratch.** GoHighLevel has no native lead-score migration; rebuild as a numeric Custom Field driven by Workflow add/subtract actions, and remember the "score" naming gotcha from Phase 1.
- **Re-derive Lifecycle / Lead Status as a Dropdown Custom Field or Tag.** Source enumeration fields often ship with internal names that differ from display labels; map against internal names, not labels.*If skipped: Mapping against display labels silently mismatches when the source has renamed labels but kept old internal values.*
- **Decide how email/calendar sync is re-established per user.** Two-way Google or Outlook calendar sync must be reconnected per user from inside that user's profile; the "login as" feature cannot connect a Google account.*If skipped: Reps locked out of self-service calendar reconnection cannot book meetings on day one.*

4\. Sandbox Test Migration 12 tasks

- **Load a representative 1–5% sample of Contacts into the Sandbox via CSV.** Use the Bulk Import wizard at Contacts → Import; pick records that exercise every Custom Field, every picklist value, and known edge cases.
- **Load a matching sample of Opportunities, Companies, and Custom Objects.** Load in dependency order: Companies first, then Contacts, then Opportunities, then Custom Object records, then Associations.*If skipped: Loading children before parents leaves Associations unresolved and forces a re-run.*
- **Verify a sample of 10 Sandbox Contacts field-by-field against the source.** Open each record and compare every Custom Field, Tag, and Association.*If skipped: Field-level corruption only surfaces under manual inspection; counts-only validation passes while values are wrong.*
- **Test edge cases explicitly: long strings, emoji, non-Latin characters, commas in fields.** These are the failure modes that pass small-batch testing but fail at production scale.
- **Confirm date and timezone arrival is correct on at least 5 Appointment records.** Cross-check the displayed time in the destination Sub-account against the source after accounting for the configured timezone.*If skipped: Off-by-one-day or off-by-hours timestamp errors look fine in spot-checks but corrupt every meeting reminder.*
- **Verify Associations between Contacts, Companies, Opportunities, and Custom Objects.** Open a parent record and confirm related records appear with the correct Association label and cardinality.
- **Time each Sandbox load and extrapolate to production volume.** If a 5% Contact load takes N minutes, the 100% load will take at least 20N plus throttling pauses; confirm the cutover window is realistic.
- **Test attachment upload end-to-end on a representative file.** Upload via Media Library, verify the link renders in the contact's File Upload Custom Field, and confirm the file is accessible.
- **Rebuild one Workflow in the Sandbox and trigger it with a Sandbox contact.** Confirm trigger fires, actions execute in order, and merge fields render correctly.*If skipped: A Workflow that builds cleanly but fails to trigger is the highest-impact bug to find after cutover.*
- **Have a domain expert from the using-team spot-check 20 Sandbox records.** Sales or marketing leads catch business-meaning errors (wrong stage interpretation, wrong owner) that the migration team cannot.
- **Document and resolve every Sandbox issue before declaring Phase 4 complete.** Capture each issue in a tracked list with root cause, fix, and re-test outcome.
- **Get written sign-off on the Sandbox test results before moving to cutover.** Sponsor sign-off is the explicit gate between Phase 4 and Phase 5.

5\. Production Cutover 13 tasks

- **Confirm the source-system freeze is active and no writes occurred in the last hour.** Check source audit logs to verify no record was created or updated during the freeze window.*If skipped: Writes during freeze produce a silent delta the export does not capture, leaving records orphaned in the source.*
- **Take a final full export of every in-scope object from the source.** This is the delta capture between the Phase 2 baseline export and cutover; record the exact UTC timestamp.
- **Confirm every destination Workflow, trigger, and integration is paused.** Final pre-load check: nothing fires on contact create, tag add, or opportunity stage change.*If skipped: A single active Workflow can send thousands of unintended SMS or emails during the import.*
- **Load Users first (or confirm user crosswalk is complete).** Owner references in downstream loads resolve to user IDs that must already exist.
- **Load Companies before Contacts.** Use the dedicated Companies Bulk Import wizard at CRM → Import / Export → Companies; only CSV is accepted.
- **Load Contacts via the Contacts Bulk Import wizard.** Pick Create / Update / Create + Update mode explicitly; use external ID as the upsert key to make re-runs idempotent.*If skipped: Using email as the upsert key when duplicates exist silently merges two source records into one destination record.*
- **Load Opportunities after Contacts.** Opportunity rows must reference an existing Contact by primary or secondary key and an existing Pipeline Stage by name.
- **Load Custom Object records.** Use Bulk Actions → Custom Objects bulk import; pick Create, Update, or Create + Update; configure unique-field dedupe behavior per the mapping spreadsheet.
- **Load Associations between objects.** Build each Association under Settings → Objects → Associations with the predetermined label and cardinality.*If skipped: Exceeding the 1,000-record Association cap on a single parent silently truncates the relationship list.*
- **Load Notes, Tasks, Appointments, and historical activity records.** Stamp \`source\_created\_at\` on every record; system-managed Created Date will read as cutover day.
- **Capture Bulk Action job IDs, row counts, and error logs at every step.** Each Bulk Import surfaces a job ID and an error log; export both for the migration audit trail.*If skipped: Missing job IDs make rollback impossible — Restore Deleted Contacts is the only safety net and it has a retention window.*
- **Cross-check destination row counts against source row counts after every load.** If counts diverge, diagnose before continuing — do not push through with a partial load.
- **Re-enable Workflows, integrations, and triggers only after all loads complete.** Restart in dependency order: low-traffic Workflows first to confirm clean firing, then high-volume ones.*If skipped: Re-enabling all Workflows at once can flood A2P 10DLC quota and degrade deliverability for the first day.*

6\. Validate 19 tasks

- **Compare total Contact count: source vs. destination.** Investigate any delta; expected delta should match the documented dedup removals from Phase 1.*If skipped: An unexplained gap means rows failed silently; chasing the cause two weeks later is far harder.*
- **Compare total Opportunity count and aggregate pipeline value per stage.** Pipeline $ totals are the cleanest CRM reconciliation check — they roll up Opportunities, currency, and stage assignment in one number.*If skipped: A monetary delta caught after sign-off triggers a forensic dig through individual rows that should have been caught here.*
- **Compare Custom Object record counts per object.** Each Custom Object has its own count; check individually.
- **Compare Note, Task, Appointment, and Call counts per object.** Activity records are the easiest to under-count because they ship as separate files.
- **Verify 25–50 randomly sampled Contacts field-by-field against the source.** Spot-check every Custom Field value, Tag list, and Association on each sampled record.
- **Verify 25 randomly sampled Opportunities for stage, owner, value, and contact association.** Stage and owner are the most common silent errors after a CSV import.
- **Verify Contact-to-Company associations on a sample of 20 records.** Open the Company record and confirm associated Contacts list correctly with the right Association labels.
- **Verify Opportunity-to-Contact associations on a sample of 20 deals.** Open the Opportunity and confirm the primary contact is set; verify any additional associated contacts via the Associations tab.
- **Verify Custom Object associations across object types.** Test at least one association per Custom Object that you migrated; confirm cardinality is enforced (1:1, 1:N, Many-to-Many).
- **Verify Notes, Tasks, and Appointments attach to the correct parent records.** Open 10 random Contacts and 10 random Opportunities and confirm their activity timeline matches the source.
- **Verify attachment files render and download correctly.** Open the Media Library link or File Upload Custom Field on 10 records.
- **Verify \`source\_created\_at\` Custom Field is populated on every imported record.** Filter Smart Lists by missing \`source\_created\_at\` to find rows where the timestamp dropped.*If skipped: Missing original timestamps silently destroy historical aging reports forever.*
- **Confirm the GoHighLevel Audit Log captured the import activity.** Settings → Audit Logs; entries are retained for 60 days, so export to long-term storage during validation.*If skipped: Audit-log retention is 60 days; after that the import evidence is unrecoverable from inside the platform.*
- **If HIPAA is enabled, confirm the BAA is countersigned and audit logging is active.** Compliance posture before any ePHI is queried in the new system.
- **Confirm A2P 10DLC brand and campaigns are Approved (not Pending) before enabling Workflows.** Check LC Phone settings; campaign status must read Approved.
- **Walk 3–5 power users through their day-one workflows.** Confirm Smart List filters return expected records, Pipelines look correct, and Conversations show the migrated history.
- **Have UAT users trigger a real test Workflow end-to-end.** Submit a test form, advance a test Opportunity stage, and confirm the rebuilt Workflow fires correctly.
- **Document every UAT issue with severity and owner.** Triage: blocker, major, or cosmetic; each blocker must close before sign-off.
- **Capture written sign-off from the migration sponsor.** Sponsor sign-off is the explicit gate between Phase 6 and Phase 7; no end users get login access until this signature exists.*If skipped: Skipping the formal sign-off step makes it impossible to identify when post-cutover bugs are migration-caused vs. user-caused.*

7\. Post-Migration Cleanup 11 tasks

- **Communicate go-live to all end users with login instructions and a help contact.** Include the Sub-account URL, password-reset path, and the first-responder contact for the first 48 hours.
- **Run role-segmented training sessions on GoHighLevel basics.** Sales reps need Pipelines and Conversations; admins need Workflow builder and Smart Lists; managers need Reporting and Dashboards.
- **Set the source system to read-only and announce the read-only date.** Revoke write permissions globally; the date triggers the 90-day decommission countdown.
- **Rebuild Reports and Dashboards in GoHighLevel from scratch.** Source dashboards do not migrate; use the Dashboard builder to recreate the top 5–10 reports the team relies on.*If skipped: Reports rebuilt only after they're needed delay actionable decisions for weeks.*
- **Finish rebuilding remaining Workflows beyond the cutover-critical set.** Triage by usage volume; the top 20% by trigger frequency typically cover 80% of automation value.
- **Re-establish integrations: email/calendar sync, payment gateways, outbound notifications, BI tools.** Two-way calendar sync requires each user to re-connect their own Google/Outlook account; the "login as" feature cannot do this.*If skipped: Users assuming calendar sync "just works" miss meetings until they reconnect their accounts.*
- **Schedule a 30-day post-migration retrospective.** Capture what worked, what failed, and what would be done differently next time.
- **Set and document the source-system decommission date.** Typically 90 days after cutover, after the GoHighLevel Restore Deleted Contacts window and the 60-day Audit Log retention have both elapsed.
- **Archive source-system exports to long-term storage.** Keep the Phase 2 and Phase 5 exports in cold storage in case of forensic need; encrypt at rest.*If skipped: Source data discarded too early leaves no recovery path for disputes that surface months later.*
- **Export the Bulk Action job logs and Audit Log entries before retention windows close.** Audit Logs retain 60 days inside GoHighLevel; the migration evidence must live elsewhere for compliance.
- **Close the migration project formally.** Final status report, lessons learned, project closure.

Questions, answered

## Migrating to HighLevel: questions

How long does migration to GoHighLevel take?

A small-business migration with under 5,000 contacts, one Pipeline and no Custom Objects runs one to three business days end-to-end. A mid-market or agency project with multiple Sub-accounts, Opportunity history, Custom Objects, Workflow rebuilds and A2P 10DLC submissions runs two to six weeks of elapsed time including preparation and validation.

Can I migrate from HubSpot to GoHighLevel?

Yes — HubSpot to GoHighLevel is one of the most common cost-driven moves. Contacts, Companies and Deals map cleanly to Contacts, Companies and Opportunities, but HubSpot Workflows, Sequences, Lead Scoring and Custom Object schemas do not transfer and need to be rebuilt in GHL Workflows from documentation.

Can I migrate from ActiveCampaign or Keap to GoHighLevel?

Yes, and both are common GHL migration sources. ActiveCampaign Contacts and Deals map to GHL Contacts and Opportunities; Keap contacts, companies and pipelines map similarly. Visual Automations from ActiveCampaign and Campaigns from Keap do not import and need to be rebuilt as GHL Workflows from screenshots and notes.

Does GoHighLevel preserve original timestamps on import?

No. Contact \`dateAdded\`, Opportunity \`createdAt\`, Custom Object \`createdAt\`, Note \`createdAt\` and Appointment \`createdAt\` are platform-managed and stamped to import day. Create custom Date fields like \`legacy\_created\_at\` on every object before import and populate them from the source export to preserve the original audit trail for reporting.

Can I migrate Custom Objects to GoHighLevel?

Yes, but each Location is capped at 10 Custom Objects across all plans and each association is capped at 1,000 linked records. Define each Custom Object schema, primary field, unique fields and associations to standard objects before importing records. Bulk CSV import is supported via the Custom Objects Bulk Actions flow.

What happens to deal history and pipeline stages during migration?

Recreate every Pipeline and Stage in GoHighLevel before importing Opportunities — rows targeting non-existent stages are rejected. Opportunity stage-transition history is not preserved by the import; only the current Stage lands. If you need historical transition timestamps for reporting, export them from the source and store them in custom Date fields.

Is there an undo or rollback for GoHighLevel imports?

Partially. Contacts → Restore lets super admins recover recently deleted records within the retention window, and the Bulk Actions log lets you cancel a running import. There is no native one-click undo for a completed import — stamp every imported row with an \`import\_batch\_id\` custom field and bulk-delete by that ID instead.

## Sources

1. [GoHighLevel — official site](https://www.gohighlevel.com/)
2. [Rename standard objects in your CRM — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000006674-how-to-rename-standard-objects-in-your-crm)
3. [Bulk import Companies using a CSV file — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000007403-how-to-bulk-import-companies-using-a-csv-file)
4. [Association limits — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000005346-association-limits)
5. [Custom Objects in all plans + higher limit — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000006631-custom-objects-in-all-plans-higher-limit)
6. [Unique field support for Custom Objects — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000006668-custom-objects-unique-fields-support)
7. [GHL Marketplace Sandbox Accounts: setup and usage](https://marketplace.gohighlevel.com/docs/sandbox-account)
8. [Raise Custom Object Association Limit — Current 1,000 Limit (HighLevel Ideas)](https://ideas.gohighlevel.com/custom-objects/p/raise-custom-object-association-limit-current-1-000-limit-makes-feature-unusable)
9. [Upsert Contact — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/upsert-contact)
10. [HighLevel platform limits — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/highlevel-platform-limits)
11. [HighLevel authentication & integration — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/highlevel-auth)
12. [Importing Contacts and Opportunities via CSV — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000003905-importing-contacts-and-opportunities-via-csv)
13. [Custom Values settings — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000004705-custom-values-settings)
14. [Import Transactions and Orders using CSV — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000005544-import-transactions-and-orders-using-csv-files)
15. [Bulk import Custom Object records (CSV) — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000007407-bulk-import-custom-object-records-csv-with-bulk-actions)
16. [Quick add & edit custom fields in Forms & Surveys](https://help.gohighlevel.com/support/solutions/articles/155000003223-how-to-quickly-add-and-edit-custom-fields-in-forms-and-surveys)
17. [How to create and use Custom Fields within HighLevel](https://help.gohighlevel.com/support/solutions/articles/48001161579-how-to-use-custom-fields)
18. [Troubleshooting bulk imports via CSV — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/48001223155-troubleshooting-bulk-imports-via-csv)
19. [Manage and merge duplicate Contacts in HighLevel](https://help.gohighlevel.com/support/solutions/articles/155000006647-contacts-manage-and-merge-duplicates)
20. [ActiveCampaign to HighLevel migration guide](https://help.gohighlevel.com/support/solutions/articles/155000003296-activecampaign-to-highlevel-migration-guide-)
21. [Complete guide to Media Storage — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000002707-complete-guide-to-media-storage-)
22. [How to merge duplicate Contacts in HighLevel](https://help.gohighlevel.com/support/solutions/articles/48001202210-how-to-merge-duplicate-contacts-in-highlevel)
23. [Revert snapshot update (HighLevel Ideas)](https://ideas.gohighlevel.com/snapshots/p/revert-snapshot-update-like-you-have-with-bulk-actions)
24. [CSV file format for importing objects — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000005143-csv-file-format-for-importing-objects)
25. [Bulk import Custom Objects (HighLevel Ideas)](https://ideas.gohighlevel.com/bulk-actions/p/bulk-import-custom-objects)
26. [Attachments made easy in Conversations — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000001323-attachments-made-easy-in-conversations)
27. [Workflow Action: Add to Notes — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000003143-workflow-action-add-to-notes)
28. [Adding files to Contacts using a custom field](https://help.gohighlevel.com/support/solutions/articles/48001171922-adding-files-to-contacts-using-a-custom-field)
29. [Salesforce to HighLevel migration guide — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/155000004305-salesforce-to-highlevel-migration-guide-)
30. [Audit Logs in HighLevel — track changes & user activity](https://help.gohighlevel.com/support/solutions/articles/155000006667-audit-logs)
31. [Comment created\_at timestamps overwritten during import — analogous pattern (Beads issue #735)](https://github.com/steveyegge/beads/issues/735)
32. [Restore deleted contacts or undo bulk deletes — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/48001211386-restore-deleted-contacts-or-undo-bulk-deletes)
33. [HighLevel Partner Program — Certified Admins & Developer Partners](https://partners.gohighlevel.com/)
34. [HighLevel — Data Privacy & Security](https://www.gohighlevel.com/privacy-and-security)
35. [Self-hosting option for GoHighLevel to support GDPR / data residency (HighLevel Ideas)](https://ideas.gohighlevel.com/hipaa-compliance/p/feature-request-self-hosting-option-for-go-high-level-eg-via-aws-or-azure-to-sup)
36. [HIPAA compliance with HighLevel — Support Portal](https://help.gohighlevel.com/support/solutions/articles/48000983084-hipaa-compliance-with-highlevel)
37. [Re-integrate Google Calendar for a User — HighLevel Support](https://help.gohighlevel.com/support/solutions/articles/48001181302-how-to-re-integrate-google-calendar-for-a-user)
38. [How to merge duplicate Contacts in HighLevel — Support Portal](https://help.gohighlevel.com/support/solutions/articles/48001202210-how-to-merge-duplicate-contacts-in-highlevel)
39. [How to enable two-way Calendar sync in GoHighLevel (Google & Outlook)](https://www.youtube.com/watch?v=RIdS8T3yTpw)

Get a quote

## Moving to HighLevel?

Tell us where your data lives today and roughly how much there is. We scope the migration and the HighLevel setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
