History structure choice before support import
Decide whether imported history should become conversations or tickets before scripting the migration so the buyer sees one coherent system instead of a messy hybrid.
Why this can grow a startup
A migration starts feeling risky when the destination model is fuzzy. If one team thinks the old records are live support threads and another thinks they are structured back-office tickets, the switch inherits confusion before users even log in. Choosing one primary structure early keeps the scripts simpler, the validation cleaner, and the buyer's mental model more stable.
Source-backed example
Intercom's migration guide tells teams to choose whether Zendesk history should be created as conversations or tickets before writing import scripts, and warns that mixing structures adds complexity.
Source-reported evidence
Source: Intercom Help · Browse Intercom Help tactics
Limit the number of record structures created during migration
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 26, 2026
When to use it
Use this when Support, Product, Docs is relevant to migration, support ops, data model and you can run a bounded test with a free 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Support and Product, using evidence from Intercom Help as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from Intercom Help
Explore related GrowthDex examples and evidence connected to Intercom Help.
Open Intercom Help source hub