# Integration cutover checklist before tracker switch

> Map every upstream and downstream integration before cutover so the new tracker already knows where bugs, notifications, and requests will come from.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/integration-cutover-checklist-before-tracker-switch/
- Source: [linear.app](https://linear.app/switch/migration-guide)
- GrowthDex source hub: [Linear](/sources/linear-linear-app/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: low
- Channels: Product, Integrations, Operations
- Stages: switching, integrations, cutover, workflow continuity


## Why this can grow

A tracker migration looks successful right up until work stops arriving from the tools around it. The real risk is often in the connected systems: Slack notifications, support-ticket intake, GitHub syncing, or triage rotations. Writing the integration checklist ahead of time turns hidden dependencies into visible work. It also reassures buyers that the move is about keeping the operating loop intact, not just changing where tickets live.

## 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 integration cutover checklist before tracker switch can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Integrations channel.
3. Use the evidence from linear.app 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

Linear's migration guide tells teams to work with admins and owners of other internal tools to get each integration running, naming Slack, support tools like Zendesk or Intercom, GitHub, triage rotations, and calendar sync as common cutover items.

## Adjacent tactics in the same lane

- [Read-only shutdown note after cutover](/growth-ideas/read-only-shutdown-note-after-cutover/) - same source, 2 shared channels, 2 shared stages
- [Hidden-work audit from switch pilot](/growth-ideas/hidden-work-audit-from-switch-pilot/) - same source, 2 shared channels, 1 shared stage
- [Shared language guide before org-wide rollout](/growth-ideas/shared-language-guide-before-org-wide-rollout/) - same source, 2 shared channels, 1 shared stage
- [Fewer teams first before workspace sprawl](/growth-ideas/fewer-teams-first-before-workspace-sprawl/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The switch feels real when the old habits have nowhere to hide](/blog/the-switch-feels-real-when-the-old-habits-have-nowhere-to-hide/) - switching, product operations, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.