# Drain-and-fill cutover before final support history batch

> Move new support traffic to the new tool first, work both systems temporarily, and migrate the remaining closed history after the old queue drains.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/drain-and-fill-cutover-before-final-support-history-batch/
- 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: epic
- Budget: medium
- Channels: Support, Operations, Lifecycle
- Stages: migration, cutover, support ops, change management


## Why this can grow

Not every migration needs a dramatic big-bang cutover. A drain-and-fill approach reduces risk by separating live routing from final history cleanup. The support team can start learning the new workspace while the old system naturally loses open threads, and the buyer sees a calmer path that does not depend on one perfect weekend move.

## 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 drain-and-fill cutover before final support history batch can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Operations 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 describes a drain-and-fill approach where teams cut over to Intercom before launch, work both tools until the old queue closes out, and then run the last migration batch.

## Adjacent tactics in the same lane

- [Delta-date cutover for support migration](/growth-ideas/delta-date-cutover-for-support-migration/) - same source, 2 shared channels, 3 shared stages
- [Contact and attribute preload before support history import](/growth-ideas/contact-and-attribute-preload-before-support-history-import/) - 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, 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, 2 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.