# Help-center import that preserves structure and flags fixes

> Make the knowledge-base move feel safe by preserving the old structure on import and pointing out what still needs cleanup.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/help-center-import-that-preserves-structure-and-flags-fixes/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/4393790-switching-from-zendesk-to-intercom)
- GrowthDex source hub: [Intercom Help: Switching from Zendesk to Intercom](/sources/intercom-help-switching-from-zendesk-to-intercom-intercom-com/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: medium
- Channels: SEO, Support, Website
- Stages: migration, knowledge base, crawlability, switcher intent


## Why this can grow

Support leaders do not only fear data loss. They fear waking up to a broken help center with no map of what changed. A migration surface that keeps the existing article structure and marks review debt removes a lot of that anxiety. It also helps the buyer imagine publishing faster, because the move becomes a guided edit pass rather than a rebuild from zero.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where help-center import that preserves structure and flags fixes can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the SEO and Support channel.
3. Use the evidence from intercom.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Intercom says teams can migrate Zendesk help content in one click by entering the Help Center URL, and that the importer keeps the organizational structure while flagging content that needs review and advice on how to fix it.

## Adjacent tactics in the same lane

- [Help-center collection link cleanup after domain switch](/growth-ideas/help-center-collection-link-cleanup-after-domain-switch/) - 3 shared channels, 2 shared stages
- [Single indexed help center during knowledge sync](/growth-ideas/single-indexed-help-center-during-knowledge-sync/) - 2 shared channels, 3 shared stages
- [Same-workspace 301 map after help-center migration](/growth-ideas/same-workspace-301-map-after-help-center-migration/) - 3 shared channels, 1 shared stage
- [HTTP 301 redirect rules for deleted help articles](/growth-ideas/http-301-redirect-rules-for-deleted-help-articles/) - 3 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The switch page should finish the move](/blog/the-switch-page-should-finish-the-move/) - SaaS SEO, product-led growth, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.