# Simplest-form history import for reporting continuity

> Migrate historical support data in the lightest useful format so buyers keep reporting continuity without turning the switch into a transcript reconstruction project.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/simplest-form-history-import-for-reporting-continuity/
- 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-25
- Rarity: rare
- Budget: low
- Channels: Docs, Sales, Support
- Stages: migration, reporting, switcher intent, support
- Key metric: Message-by-message migration can inflate API calls by 10-100x

## Why this can grow

A lot of migration fear is really reporting fear. The buyer does not always need every old thread rebuilt message by message. They need continuity, context, and enough history to trust the new system. A simpler import lowers API load, shortens the project, and still preserves the reporting baseline that makes the move feel safe.

## 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 Message-by-message migration can inflate API calls by 10-100x before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where simplest-form history import for reporting continuity can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Docs and Sales 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: Message-by-message migration can inflate API calls by 10-100x.
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 historical migration guide recommends migrating data in its simplest form when the main goal is keeping reporting inclusive of historical data, instead of recreating every message one by one.

## Adjacent tactics in the same lane

- [History structure choice before support import](/growth-ideas/history-structure-choice-before-support-import/) - same source, 2 shared channels, 2 shared stages
- [Batch test migration on sample records first](/growth-ideas/batch-test-migration-on-sample-records-first/) - same source, 2 shared channels, 2 shared stages
- [Delta-date cutover for support migration](/growth-ideas/delta-date-cutover-for-support-migration/) - same source, 2 shared channels, 2 shared stages
- [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, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The switch should feel boring before it feels done](/blog/the-switch-should-feel-boring-before-it-feels-done/) - switcher intent, migration, trust

## Advisory

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