GoHighLevelCRM migrationHubSpotKeapautomationUnited States

GoHighLevel Migration Checklist: Move Any CRM Without Losing Data

A step by step GoHighLevel migration checklist for HubSpot, Keap, Salesforce, ClickFunnels or spreadsheets: data, workflows, phones, A2P and cutover.

Laptop showing charts and data on a desk

A GoHighLevel migration has five stages: take inventory of what you have, map every field, import contacts and then opportunities, rebuild your automations by hand, and move phones, texting and email before a planned cutover. Data is the easy part. The things that break are custom fields that were never created, workflows nobody documented, and phone numbers that stop texting on launch day.

This is the checklist we follow on every move into GoHighLevel, whatever the source: HubSpot, Keap, Salesforce, ClickFunnels, ActiveCampaign or a spreadsheet. Platform specific notes are in our guides for HubSpot, Keap, ClickFunnels and ActiveCampaign.

1. Take inventory before you export anything

Write down what exists in the old system, with counts. You will use this list to prove nothing went missing.

  • Contacts, companies and any duplicates you already know about
  • Custom fields (name, type, and whether anyone still uses them)
  • Tags, lists and segments
  • Pipelines, stages and open deals, with their values
  • Notes, tasks and activity history you actually need
  • Active automations, sequences and campaigns
  • Forms, landing pages and funnels that feed the CRM
  • Phone numbers, texting providers and email sending domains
  • Integrations: calendars, payment tools, Zapier or webhooks

Decide what not to bring. A migration is the cheapest moment to drop dead fields, stale tags and contacts who bounced years ago. If your list needs real cleanup first, our CRM data cleanup service handles it at scale.

2. Map every field

Build a simple mapping sheet: old field name, new GoHighLevel field, field type, and a note on any transformation (date formats, phone formats, picklist values).

  • Standard fields first: first name, last name, email, phone, address, company
  • Create custom fields in GoHighLevel before you import. HighLevel’s import guide notes that data for fields that do not exist yet has nowhere to go until you create them.
  • Format phone numbers with country codes so texting works later
  • Turn old lists and segments into tags, because tags drive most GoHighLevel automation
  • Match picklist values exactly, including capitalization

3. Import contacts the safe way

GoHighLevel imports contacts from CSV files only, not Excel or Google Sheets files, so export your sheet as .csv first.

  • Check the file size limit in your own importer. HighLevel’s help pages disagree: current articles say 30 MB, an older walkthrough says 50 MB, and an older troubleshooting article mentions 20 MB or 10,000 rows. We split large lists into files of about 10,000 rows, which works under every version.
  • Tag every batch with a unique import tag, such as import_2026_11_batch1. There is no undo button, and the tag lets you find and remove a bad batch in one step.
  • Choose how duplicates are handled (match on email, phone or both) before you start
  • Import a test file of 20 contacts first and check every mapped field on a real record
  • Compare the final count against your inventory

Coming from HubSpot? HighLevel now has a built in HubSpot importer that connects to your account and brings over contacts, deals, properties, pipelines, stages, notes and tasks. HighLevel lists limits: recurring tasks are not supported and imported emails are read only. It is still worth checking the results against your inventory.

4. Rebuild pipelines, then import opportunities

  • Create each pipeline and its stages in GoHighLevel first
  • Import contacts before opportunities, because every opportunity belongs to a contact
  • Use pipeline and stage names in your file that match GoHighLevel exactly. A mismatch is a common reason opportunity imports fail.
  • Bring over values and owners for open deals. Decide whether closed deals need to come across or can stay in an archive export.

HighLevel’s opportunity import guide lists the required columns.

5. Carry over notes and history you will use

Notes and activity history are the hardest data to move, and most platforms do not export them in a clean file.

  • Decide what history the team actually opens. Often it is the last 12 to 24 months of notes on open customers.
  • Use a native importer or API where one exists (HubSpot’s importer covers notes and tasks)
  • For everything else, keep a full export archived somewhere safe and searchable

6. Rebuild workflows by hand

No CRM can import automations from another platform. Workflows, sequences and campaigns have to be rebuilt in GoHighLevel, and that is usually where most of the project time goes.

  • List every live automation with its trigger, steps and goal
  • Retire the ones nobody can explain
  • Rebuild the rest using GoHighLevel triggers, tags and pipeline stages
  • Add a stop condition to every messaging workflow so a contact who replies or books stops getting messages
  • Keep the old automations paused, not deleted, until cutover

If you want this done for you, GoHighLevel workflow automation is a fixed price service.

7. Move phone numbers and fix texting

Phones are the part most likely to break on launch day, so start early.

  • Porting takes weeks. HighLevel’s porting article gives a typical 2 to 4 week timeline for bringing a US number from another carrier, and you need a bill or account record from your current provider. International numbers do not use the standard in app port flow.
  • Keep the number live with the old carrier until the port completes, and do not cancel that service early
  • For US texting from local numbers, register an A2P 10DLC brand and campaign. Carriers filter unregistered traffic, and approvals take time. Our A2P 10DLC walkthrough and fix for rejected campaigns cover the details.
  • Bring consent records over as tags or fields so you only text people who opted in

8. Set up email and domains

  • Add a dedicated sending domain or subdomain and authenticate it with SPF, DKIM and DMARC
  • Warm up sending gradually instead of blasting the full list on day one
  • Move or rebuild forms, funnels and booking pages, then update every link on your website and ads
  • Reconnect calendars, payment tools and other integrations

If emails start landing in spam, see GoHighLevel email deliverability.

9. Test before you switch

  • Submit every form and confirm the contact, tags and pipeline stage are right
  • Book a test appointment and check the reminders
  • Call and text the business number from at least two carriers
  • Trigger each rebuilt workflow with a test contact
  • Check user permissions and notifications for every team member

10. Cut over on a planned day

  • Pick a quiet day and tell the team in advance
  • Do a final delta import of anything created in the old system since the main import
  • Switch forms, numbers and integrations to GoHighLevel
  • Turn off old automations so contacts do not get messages from both systems

11. After launch

  • Watch new leads, texts and bookings closely for the first two weeks
  • Compare record counts against your inventory again
  • Keep read only access to the old system for at least 30 days, then cancel it
  • Train the team on the daily views they will use: conversations, opportunities and calendars

How long does it take?

For a single business with a normal amount of data, we deliver migrations in about 14 days: inventory and mapping, a parallel build, an audit of every record, a short parallel run and the cutover. Phone porting can take longer than the rest of the project, which is why it starts on day one. Large databases, many pipelines or complex automations add time.

DIY or hire help?

You can run this checklist yourself if your data is small and clean and you have few automations. Hire help when you have years of history, several pipelines, active texting, or a team that cannot afford a broken week. Our GoHighLevel migration service starts at $497 with a fixed price agreed before work begins, and we also handle CRM migrations between other platforms. Not sure where your current setup leaks leads? Start with a free lead response audit.

FAQ

How long does a GoHighLevel migration take?

About 14 days for a typical single business, from inventory to cutover. Porting a phone number into GoHighLevel can take 2 to 4 weeks on its own, so start it first.

Can I import notes and activity history into GoHighLevel?

From HubSpot, yes: HighLevel’s HubSpot importer brings over notes and tasks, with some limits. From most other platforms, notes need an API based migration or stay in an archived export.

Do my automations transfer to GoHighLevel?

No. Workflows, sequences and campaigns cannot be imported from another CRM. They have to be rebuilt in GoHighLevel, which is a good time to drop the ones nobody uses.

What file format does GoHighLevel accept for imports?

CSV only. HighLevel’s help pages list different size limits, so check your importer and split large files into batches of about 10,000 rows.

Will my phone number keep working during the migration?

Yes, if you keep it active with your current carrier until the port is complete. Do not cancel the old service until the number is live in GoHighLevel.

Ready to move?

Book a 20 minute discovery call. Bring your current CRM. Leave with a fixed price and a delivery date.