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.
Why this can grow a startup
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.
Company 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.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
Source discovered: May 25, 2026
When to use it
Use this when Docs, Support, Operations is relevant to migration, cutover, change management and you can run a bounded test with a medium budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Intercom Help and identify what is directly supported.
- Choose one channel context: Docs, Support, Operations.
- Define the test around one observable customer behavior.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.