# Contact and attribute preload before support history import

> Create the customer contacts and required attributes before importing historical threads so every migrated record lands with the right identity and fields attached.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/contact-and-attribute-preload-before-support-history-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: low
- Channels: Support, CRM, Operations
- Stages: migration, identity mapping, data hygiene, support ops


## Why this can grow

Support history without a clean identity layer is just noise in a new inbox. Preloading contacts and attributes means imported records can map to the right user, keep the right metadata, and avoid a second repair project after the migration supposedly finished. It also helps the buyer trust the move because the new system looks organized on day one instead of partially stitched together.

## 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 contact and attribute preload before support history import can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and CRM 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 says contacts must exist before conversations or tickets are imported and that custom data attributes should be created in Intercom before history is brought over.

## Adjacent tactics in the same lane

- [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
- [Drain-and-fill cutover before final support history batch](/growth-ideas/drain-and-fill-cutover-before-final-support-history-batch/) - 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, 2 shared stages
- [Cutover runbook and rollback plan before support launch](/growth-ideas/cutover-runbook-and-rollback-plan-before-support-launch/) - 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 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.