# Delta-date cutover for support migration

> Choose a fixed delta date, move closed history first, then bring over the remaining open and pending work at formal cutover.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/delta-date-cutover-for-support-migration/
- 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: epic
- Budget: medium
- Channels: Docs, Support, Operations
- Stages: migration, cutover, change management, support


## Why this can grow

Teams freeze when migration sounds like one giant irreversible event. A delta-date plan breaks the move into two clearer jobs: archive the stable history early, then move the still-live work when the organization is ready. That reduces operational stress and gives everyone a cleaner picture of what is left to verify on cutover day.

## 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 delta-date cutover for support migration can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Docs 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's migration guide recommends setting a Delta Date, importing only closed tickets up to that point into a non-live production environment, and then migrating the remaining closed plus open or pending tickets during cutover.

## Adjacent tactics in the same lane

- [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, 3 shared stages
- [Full transcript reply instead of message-by-message replay](/growth-ideas/full-transcript-reply-instead-of-message-by-message-replay/) - same source, 3 shared channels, 1 shared stage
- [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
- [Simplest-form history import for reporting continuity](/growth-ideas/simplest-form-history-import-for-reporting-continuity/) - 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 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.