Skip to main content

​
Two migration paths

The Migrate tab (/dashboard/help-center/migrate) supports two import methods:
MethodWhen to use
URL crawlImporting from any public help center or docs site (Intercom, HelpScout, ReadMe, GitBook, custom-built).
Intercom APIImporting directly from your Intercom workspace using a token. Faster and more accurate than crawling.
Both methods use background jobs so you can kick off a migration and return when it’s done.

​
URL crawl migration

​
How it works

1

Detect structure

Halo crawls the source URL, detects the platform (Intercom, HelpScout, etc.), and identifies collections and article counts.
2

Review the plan

The detected structure is shown. Review the platform, collection list, and article counts. Confirm or cancel.
3

Migrate

Halo extracts each article in parallel with progress tracking — pages analyzed, pages extracted, pages built.
4

Articles are ingested

Migrated articles appear as Drafts in your help center, organized into collections that mirror the source. They’re auto-ingested into your AI’s knowledge base.

​
Settings

  • ignore_api_docs — when on, skips API reference content (often noisy and not user-facing)

​
What gets imported

For each article:
  • Title and description
  • Body content (HTML, sanitized)
  • Collection (preserved from source)
  • Images (uploaded to Halo’s storage)
  • Embedded videos (preserved)
What doesn’t get imported:
  • Author attribution (you’ll need to set authors manually if you want them)
  • Custom CSS or layout
  • Comments and reactions from the source
  • Translation metadata (you can re-link translations after migration)

​
Progress tracking

The Migrate tab shows live progress:
  • pages_analyzed — discovered URLs
  • pages_extracted — content fetched
  • pages_built — articles created in Halo
  • current_step — high-level status
  • Errors with detail per failed page
You can leave the page and come back — the migration runs in the background.

​
Intercom API migration

​
How it works

For Intercom workspaces, the API method is faster and more accurate than crawling:
1

Generate a token

In Intercom, generate a Personal access token with read scopes for help center articles.
2

Connect

On the Migrate tab, choose Intercom API, paste the token, select your region (us, eu, au).
3

Detect structure

Halo lists your Intercom collections and article counts.
4

Migrate

Articles are imported via the Intercom API — preserves structure, images, and metadata more reliably than crawling.
After migration, you can disconnect the Intercom API token if you don’t need ongoing sync. (The Intercom integration at Integrations > Intercom is separate — that handles contacts/conversations, not help center articles.)

​
After migration

Migrated articles arrive as Drafts, giving you a chance to review before publishing:
  • Spot-check a few articles for formatting
  • Update authors and SEO fields
  • Fix any broken images or links
  • Restructure collections if needed
  • Bulk publish when ready
Articles are ingested into your AI’s knowledge base only when published with include_in_training on.

​
Tips

Run migration with the help center in preview mode (not live yet). Review and clean up before publishing publicly.
The crawler handles HelpScout, ReadMe, GitBook, Zendesk, Document360, and most custom-built help centers.
Halo doesn’t keep the source in sync after migration. If you keep updating the source, those changes won’t flow into Halo. Most teams treat migration as a one-time cutover.
Some pages may fail to extract (auth-protected, dynamic content). Halo lists them with reasons so you can manually port the content.

​
Where to go next

Articles

Edit migrated articles and add SEO.

Domains & Publishing

Go live with a custom domain.