# History structure choice before support import

> Decide whether imported history should become conversations or tickets before scripting the migration so the buyer sees one coherent system instead of a messy hybrid.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/history-structure-choice-before-support-import/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/9396032-historical-data-migration-to-intercom)
- GrowthDex source hub: [Intercom Help](/sources/intercom-help-intercom-com/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: free
- Channels: Support, Product, Docs
- Stages: migration, support ops, data model, switcher intent


## Why this can grow

A migration starts feeling risky when the destination model is fuzzy. If one team thinks the old records are live support threads and another thinks they are structured back-office tickets, the switch inherits confusion before users even log in. Choosing one primary structure early keeps the scripts simpler, the validation cleaner, and the buyer's mental model more stable.

## 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. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. 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 history structure choice before support import can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Product 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's migration guide tells teams to choose whether Zendesk history should be created as conversations or tickets before writing import scripts, and warns that mixing structures adds complexity.

## Adjacent tactics in the same lane

- [Batch test migration on sample records first](/growth-ideas/batch-test-migration-on-sample-records-first/) - same source, 3 shared channels, 1 shared stage
- [Full transcript reply instead of message-by-message replay](/growth-ideas/full-transcript-reply-instead-of-message-by-message-replay/) - same source, 2 shared channels, 2 shared stages
- [Simplest-form history import for reporting continuity](/growth-ideas/simplest-form-history-import-for-reporting-continuity/) - same source, 2 shared channels, 2 shared stages
- [Automatic forwarding and domain auth before support cutover](/growth-ideas/automatic-forwarding-and-domain-auth-before-support-cutover/) - same source, 1 shared channel, 3 shared stages

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The switch feels safer when the cutover has a script](/blog/the-switch-feels-safer-when-the-cutover-has-a-script/) - support migration, switcher marketing, brand trust

## Advisory

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