Say your HubSpot renewal is a few months off, and two of the seats you pay for sit empty. You are weighing GoHighLevel to put booking, texts and calls behind one login. Before migrating from HubSpot to GoHighLevel, you want to know what survives the move: your records, your phone number, and the record of who asked you to stop emailing them.
Checked against HubSpot's and HighLevel's published help pages on 2 October 2026. Both vendors change their products and pages, so check each linked page before you act.
TL;DR
Moving is worth asking about when you pay for seats nobody fills; where a sales team works in HubSpot every day, migrating is disruption you pay for twice. HighLevel's HubSpot Importer can bring across contacts, companies, deals, properties, pipelines, notes, tasks and emails; workflows, sequences, forms, pages and reports are not on its list. Treat opt-outs, consent and UK numbers as their own steps. HubSpot does not allow cancelling mid-term, so export and run both systems inside the term you have paid for.
When not to migrate
In the words of our CRM and automation page, moving from HubSpot to GoHighLevel is worth asking about when you are paying for seats nobody fills. Where a sales team works in HubSpot every day, migrating is disruption you pay for twice.
Empty seats may be a renewal question instead. HubSpot's cancellation page (updated 9 July 2026) says a downgrade at renewal can mean fewer seats or a lower tier, but "Mid-contract downgrades are not permitted". Leaving seats unused "will not automatically downgrade your account" (HubSpot, updated 9 September 2026).
Which platform fits is covered in our GoHighLevel buyer's guide.
What comes across, what you export, what you rebuild
Dates in brackets are each page's own last update. Sources for opt-outs and consent come further down.
| In HubSpot | Getting it out of HubSpot | Getting it into GoHighLevel | Plan for |
|---|---|---|---|
| Contacts and their properties | Record export with all properties and associations; links "expire after 30 days" (2 Apr 2026). Paid hubs also get a CRM backup, but "Associations and activity data aren't included" (4 Jun 2026) | HubSpot Importer, with notes and emails (10 Sep 2026); or a CSV import (18 Mar 2026) | Check a sample by hand |
| Companies | Record export | Importer, as new records | Notes cannot be linked to companies |
| Deals and pipelines | Record export | Importer, as opportunities with pipelines and stages | A deal with no contact cannot be imported |
| Custom properties | Property definitions export (11 Jun 2026) | Importer, mapped by key | Calculated fields arrive as single-line text |
| Tasks | Task export (13 Aug 2026) | Importer | Recurring tasks are not supported |
| Notes and logged emails | Per-contact export (2 Oct 2025); certain activity reports or the engagements API (2 Apr 2026) | Importer; emails arrive read-only | A CSV import takes one note per contact (24 Apr 2025) |
| Calls, meetings and chats | Reports or HubSpot's API (25 Sep 2026) | Not on the importer's list | Keep an archive |
| Files and attachments | ZIP export (3 Aug 2026) | The importer page says both "supported" and "aren't supported yet" | Export them; check attachments after import |
| Lists (segments) | Segment export (16 Sep 2026) | A CSV import can tag contacts and make a smart list | Rebuild the lists you use |
| Opt-outs | Contact export includes unsubscribes (same page as the calls row); opt-out-only addresses are not contacts | A CSV DND (Do Not Disturb) column sets DND on every channel | Apply the suppression record before anything sends |
| Legal basis and consent history | Legal-basis property, property history, form submissions | Custom fields you create | Archive the history export |
| Workflows | A spreadsheet of details and an image of each, with no history or performance data (same page as the calls row) | Not on the importer's list; the migration guide says to rebuild them (10 Sep 2026) | Rebuild and test |
| Sequences | No export on the pages we read | Not on the importer's list | Rebuild |
| Email designs | HTML or PDF of each email (22 Sep 2026) | Email AI import, which "can make mistakes" (1 Jun 2026) | Review every template |
| Pages and forms | Page HTML (28 Aug 2026); form submissions (16 Jun 2026) | Rebuilt in the page builder, per the migration guide | Forms "will lose their paid features" when the account is deactivated (same page as the calls row), so replace embedded ones |
| Reports and dashboards | CSV, Excel or image (12 Jun 2026) | Not on the importer's list | Rebuild the ones you use |
HighLevel's HubSpot Importer
HighLevel's importer page (updated 10 September 2026) says you can "connect HubSpot, choose what to bring over, and start the import from inside HighLevel". So the HubSpot exports in the table are your own copy, and the input only if you import by CSV. Beyond the limits in the table, it says "Some associations may not be imported due to platform limits". On files, it says both "File attachments are supported for Contacts and Opportunities" and, under troubleshooting, "File imports aren't supported yet". Export your files from HubSpot either way.
Before you start, it says to "Use a clean account when possible", turn on "Allow duplicates" (it says you can re-enable de-duplication after the import), and "test imports in a new or non-production location". Afterwards, a report lists errors and warnings. The page does not mention opt-outs or consent, so treat those as their own job.
If you import by CSV instead
Create custom fields and pipelines first. "Every Opportunity must be associated with a contact", and "Completed imports do not have a one-click undo option" (HighLevel, updated 17 September 2026). So tag each import, to find and delete it later. The format page (updated 25 February 2026) recommends E.164 phone numbers, which start with the country code. The date formats it lists are all month-first or year-first, so convert UK-style dates. HighLevel's pages give different file-size limits, so check the current one.
Carrying consent and opt-outs across
Who you may email, text or call is in our guide to PECR for B2B outreach. This section is about keeping the record.
What HubSpot holds on opt-outs and consent
- Unsubscribes. The "Unsubscribed from all email" and "Opted out of email" properties hold opt-outs (HubSpot, updated 22 September 2026).
- The address, not the contact. "Email subscription preferences are tied to an email address, rather than to a contact" (HubSpot, updated 18 June 2026).
- Opt-outs that are not contacts. Addresses from an opt-out import (updated 22 September 2026) are not "created as contacts". HubSpot says they appear "if you ever export bounced and unsubscribed contacts". We found no steps for that export, so ask HubSpot.
- Legal basis. The "Legal basis for processing contact's data" property holds HubSpot's own labels (HubSpot, updated 28 September 2026). It may be blank if data privacy settings (updated 11 September 2026) were never turned on.
- History. A property history export (updated 8 September 2026) can show who or what changed each value, for "up to 45 revisions" per contact property.
- Forms. If your forms asked for consent, export the submissions too.
HubSpot suggests you "may wish to delete" hard bounces and spam complaints (HubSpot, updated 21 September 2026). Our build standard is to export first.
Where opt-outs land in GoHighLevel
A DND column in a CSV applies DND "for all communication channels (SMS, Email, Calls, Voicemail, etc.)". For one channel, "you need to use a workflow and tags instead of the DND column" (HighLevel, updated 16 September 2026). Build that workflow before the import. HighLevel's DND page (updated 28 September 2026) suggests fields such as "Consent Source, Opt-in Timestamp", and shows who changed each DND setting.
Our build standard for the consent record
- The suppression record (every unsubscribe, opt-out-only address and hard bounce) goes in after the main import and before anything sends: a CSV import set to "Create and Update", with channel tags for the per-channel DND workflow rather than a DND column. HighLevel checks for existing records by contact ID, then email, then phone (HighLevel, updated 18 March 2026), so it updates the imported contacts.
- Each imported contact carries its source, its basis and the date that basis was recorded, or it waits in a review queue.
- While both systems run, only one sends marketing, and an opt-out in either is applied in both on the same day.
Email sending from the new platform
By default, emails show HighLevel's sending servers in the "sent via" headers (HighLevel, updated 17 April 2026). HighLevel says dedicated sending domains "apply only to accounts on the LC Email system", so check which email system your account uses first. HighLevel recommends "a unique subdomain not used for any other purpose". If the domain you connect already points to another email service, HighLevel says to "remove any existing MX or SPF records" from it first. Our build standard is a fresh subdomain, so nothing set up for HubSpot's sending has to be removed while both run.
Warm-up starts on its own for a new domain, with a daily limit of 1,000 emails in stage one, and HighLevel says to "Respect daily warmup limits to avoid future enforcement blocks" (HighLevel, updated 30 June 2026).
Moving UK phone numbers
First, find where each number lives. Porting a number into HubSpot "makes HubSpot the owner of that phone number" (HubSpot, updated 8 September 2026). A number still with your own provider only needs the GoHighLevel steps. HighLevel's moving-numbers guide (updated 4 September 2026) says whether a number is already hosted by Twilio or by another carrier "determines whether the numbers are migrated or ported", so tell HighLevel Support which carrier holds each number.
Out of HubSpot. For "a HubSpot number that you own in your account", you ask the new provider for a port-in, and it should send the request to "HubSpot’s call carrier, Twilio". It "can take up to five business days" for the carrier to share the PIN and account details. After the port, it "won’t be available for use in your HubSpot account".
Into GoHighLevel. HighLevel's standard flow "currently supports porting in numbers from the United States only" (HighLevel, updated 3 September 2026). For a UK number, you contact HighLevel Support. For a number from another carrier, Support "can submit Twilio's International Porting Form on your behalf". A HubSpot number sits with Twilio, so ask Support which route it takes. Your name and address "must match your carrier records exactly". "Carriers do not guarantee exact dates/times."
The UK rule on both platforms. Every UK long code (local, national, mobile and toll-free numbers, in HighLevel's words) needs an approved UK Regulatory Compliance (RC) bundle to send messages or make calls (HubSpot, updated 14 September 2026; HighLevel, updated 18 July 2024). HighLevel says a business not registered in the UK "should use UK Mobile or UK Toll Free numbers".
Keep the old service live. "Do not delete, release, disable, disconnect, or cancel a phone number with its current provider before a migration or port is confirmed complete" (HighLevel, updated 4 September 2026). Text history stays behind: porting "does not migrate historic logs/conversations". Export it first.
UK GDPR when the new platform is hosted in the US
This section summarises the published guidance of the Information Commission (the ICO) and the vendors' documents. WebAsk is not a law firm, and this is not legal advice.
You stay the controller. HighLevel's data processing addendum (last updated July 2026) says "HighLevel will act as a Processor" and the customer "will act as the Controller". The ICO says that "every time a controller uses a processor", there must be a written contract (ICO, under review). It must say the processor acts only on your "documented instructions (including when making an international transfer of personal data) unless it is required to do otherwise by UK law" (ICO, under review).
The data goes to the US. "Our product infrastructure resides in the United States", says HighLevel's security overview (updated 16 June 2026). Its addendum says HighLevel "is certified to" the UK Extension to the EU-U.S. Data Privacy Framework (DPF). The ICO says you must only rely on that if the US business "has an active status on the DPF list", has self-certified to the UK Extension, and covers the type of data you send (ICO). So check HighLevel's entry on the DPF list yourself. The ICO says you "should undertake periodic checks".
If you cannot rely on the UK Extension, the government's UK-US data bridge factsheet (published 21 September 2023) points to safeguards such as the International Data Transfer Agreement or the UK Addendum. If you rely on one, the ICO says "you must also ensure that you have completed a transfer risk assessment (TRA)". It also says UK organisations "should be mindful of the need to update privacy policies".
Special category data. The ICO says "You must take additional steps for certain types of special category data and criminal offence data", and its UK Extension page lists which types.
HighLevel's own overview sets the limit: "use of the HighLevel product alone does not make you GDPR compliant".
Timing the switch around HubSpot's renewal
HubSpot's General Terms and Product Specific Terms (last modified 16 September 2026), its downgrade page (updated 17 August 2026), and the cancellation and renewal pages linked above set the calendar.
| When | What HubSpot says |
|---|---|
| During the term | "Mid-contract cancellations are not permitted", and nor are downgrades. You are charged to the end of the term |
| Any time before the term ends, unless your Order Form says otherwise | Turn off auto-renewal. The subscription then ends on the renewal date, "regardless of when you turn off renewal" |
| At least 30 days before renewal | Notice of a fee increase at renewal, if one applies (some products have different notice terms) |
| At least five business days before renewal | Contact HubSpot by then about fewer seats or a lower tier |
| After the term | The account drops to HubSpot's free tools |
| 90 days after dropping to Starter or free | Workflows turned off and inaccessible at once, then deleted, once no Professional or Enterprise subscription is left. Sequences "permanently deleted", where Sales Hub or Service Hub was Professional or Enterprise |
| After the term | Smart CRM, free services, and hubs other than Marketing Hub and Revenue Hub: "we will not provide you with any access to Customer Data". Marketing Hub Professional or Enterprise (Marketing Contacts): a written request within 30 days |
Our build standard: export everything and run both systems inside the HubSpot term you have paid for. HighLevel's migration guide says to "consider running HubSpot and HighLevel in parallel". On our CRM page, the switch-over is staged, "with the old system live until the new one is checked against real records".
Turn off auto-renewal once you decide; HubSpot explains how to turn it back on before the cancellation date. HubSpot's data processing agreement (last modified 16 September 2026) says: "We strongly recommend retrieving your Customer Data prior to the end of your Subscription Term". Plan as if you lose access when the term ends.
A step-by-step migration checklist
- Write down why you are moving. If it is seats, ask HubSpot about a downgrade first.
- Find your renewal date and download your Order Form (updated 28 September 2026). Once you decide, turn off auto-renewal.
- List the workflows, sequences, forms, pages and reports you use, with an image of each workflow.
- Export unsubscribes and hard bounces, and ask HubSpot how to export opt-out-only addresses.
- Export legal-basis values, property history with source, and form submissions.
- Export all records, a backup if your tier has one, files, email HTML and page HTML.
- Open GoHighLevel in your name, read the addendum, check the DPF list, update your privacy notice.
- Create the consent fields. For a CSV import, also create custom fields and pipelines first.
- Import into a test location first, read the error report, then import into the live one.
- Import the suppression record as a Create and Update CSV, tagged by channel for the DND workflow, before anything sends.
- On LC Email, set up a sending subdomain and let warm-up start.
- Rebuild and test each workflow, form and template before switching it on.
- Export text history first. Submit the RC bundle and ask HighLevel Support to move each UK number. Keep the old line live.
- Run both systems inside the HubSpot term, with one sending marketing.
- Replace every embedded HubSpot form on your website.
- Take the final exports before the term ends, and keep them.
Where to start
- Decide whether to move. Start with the seats and the renewal date.
- Scope the move in writing. As our CRM and automation page puts it, "You get the scope and the go-live date in writing, not an estimate on a call."
- Talk it through. Get in touch with what you run in HubSpot now and what you want GoHighLevel to do.