Troubleshoot GoHighLevel and HubSpot migrations

Use this page when a move from GoHighLevel or HubSpot doesn't go as expected. Find what you see, follow the fix, and contact support if it's still stuck. It's for the workspace admin running the migration. For the full walkthrough, see move from GoHighLevel or HubSpot.

I can't find Migrations, or it says concierge beta

You see: Connected migrations are in concierge beta.

Why: guided migrations are being turned on workspace by workspace.

Fix: contact support to ask about access. Meanwhile, under Import records from any CRM export, you can upload contacts, companies, or leads from a CSV or Excel file.

You can reach migrations from Settings → Migrations or Integrations → Browse apps by selecting HubSpot or HighLevel and then Open migration.

The buttons are greyed out

You see: You can explore the migration options and review evidence. A workspace admin must connect, run, undo, or finalize connected migrations.

Fix: ask a workspace Admin or Owner to run these steps.

My token won't connect

Why: the token is from the wrong account, is missing permissions, or (for GoHighLevel) doesn't match the Location ID.

Fix:

1. GoHighLevel: make sure the token and Location ID come from the same sub-account, and that you used the sub-account ID, not your agency ID. Use a Private Integration token, not an older API key.
2. HubSpot: paste a private app access token, not an API key or a password.
3. Paste only the token, with no extra spaces.
4. Open Need help connecting…? on the page and check the permissions listed there.
5. Create a new token if you're not sure the old one is right.

An area says Unavailable with this token

You see: Unavailable with this token. Excluded when you save the plan.

Why: your token doesn't have read access to that area, or your plan in the old system doesn't include it.

Fix: add the read permission to your token in the old system, then scan again. Or leave that area out of this migration.

The scan stopped or seems stuck

You see: The source scan stopped, or Scanning source account for a long time.

Fix:

1. Large accounts take a while. You can leave the page and come back.
2. If it stopped, select Retry scan. It picks up safely.
3. If it keeps stopping, check your token is still valid in the old system.
4. To stop, select Cancel scan safely.

Preflight shows blockers

You see: red messages under Preflight findings, and Start migration isn't available.

Fix:

1. Read each blocker. Many point to missing token permissions or a plan setting.
2. For a record you don't need, select Skip source record in Migration findings.
3. If you mapped items to existing Spacebrain assets with Map existing asset, enter a destination for every one.
4. Select Save and run preflight again.

If you see This plan has unsaved changes. Save it and run preflight again before starting the migration., save first.

The migration failed or I cancelled it

Fix:

1. Read the error message on the progress card.
2. Fix the cause, for example by renewing an expired token.
3. Select Resume from checkpoint. It continues from where it stopped.

If you'd rather reverse what was imported, select Undo partial migration.

I closed the page during the migration

Nothing is lost. The migration keeps running on Spacebrain's side. Reopen Settings → Migrations and choose it from the migration list.

If you see Live updates paused after one hour or Live updates are temporarily unavailable, the migration is still running. Refresh the page to see the latest counts.

The totals don't match my old system

Why: some records were skipped on purpose, matched to existing records, or had problems.

Fix:

1. In the progress table, compare Created, Updated, Linked, Skipped, and Failed.
2. Check your Existing-record policy. Skip existing records leaves matches alone, so they don't count as created.
3. Check your Historical activity range. Last 24 months leaves out older history.
4. Open Migration findings and filter by Blockers and Warnings.
5. Select Download CSV report to compare record by record.

I see duplicate records

Why: records in the old system had no shared email, phone, or company domain with your existing Spacebrain records, so they couldn't be matched.

Fix: don't delete anything yet. Compare the duplicates' owners, deals, and activity. Merge them in the CRM after you finish checking the migration.

Finalize migration is greyed out

Why: required items in the Cutover checklist aren't done.

Fix: complete each required item. If one doesn't apply to you, select Waive with reason and explain why. Then select Finalize migration.

Undo failed or isn't available

• Undo failed: select Retry undo.
• You see This migration no longer has an undo window. The seven-day undo window has passed, or the migration was finalized long enough ago. Contact support if you need help reversing specific records.
• Records your team changed after the import are protected and aren't undone.

Contact support

Open Help & support and select Contact, or see contact support. Include:

• Workspace name.
• Source (GoHighLevel or HubSpot) and the account name shown on the migration.
• The migration's status and progress percentage.
• The exact error or blocker text.
• The time it failed, with time zone.
• The phase and counts from the progress table, or the CSV report.

Never send your access token. Revoke it in the old system if you think it was shared.

Next step

Finish the move with move from GoHighLevel or HubSpot.