Growth idea action plan
Workflow exceptions before API-led migration
Before importing conversations by API, disable or exempt the automations that would treat imported records like fresh customer activity.
Why this can grow a startup
A migration can look broken even when the data import succeeds, because the surrounding automations fire at the wrong time. Surveys send, notifications leak, states change, and users get pulled into a fake live conversation. Guarding the workflows first prevents avoidable trust damage and makes the cutover feel controlled instead of messy.
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. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where workflow exceptions before api-led migration can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Lifecycle and Support channel.
- Use the evidence from intercom.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- 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 warns teams to add trigger-rule exceptions for records created via API or temporarily turn workflows off during migration, and to suppress email notifications when imported conversations would otherwise message customers.
Source: Intercom Help (intercom.com)
GrowthDex source hub: Intercom Help
Last checked: 2026-05-25
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Batch test migration on sample records first same source · 2 shared channels · 2 shared stages
- History structure choice before support import same source · 2 shared channels · 1 shared stage
- Drain-and-fill cutover before final support history batch same source · 2 shared channels · 1 shared stage
- Automatic forwarding and domain auth before support cutover same source · 2 shared channels · 1 shared stage
Related GrowthDex essays
- The switch should feel boring before it feels done switcher intent, migration, trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory