# Linear

- Canonical HTML: https://growth.iangoh.com/sources/linear-linear-app/
- Original source: https://linear.app/switch/migration-guide
- Domain: linear.app
- Latest check: 2026-05-27
- Channels: Communities, Community, Customer Support, Docs, Documentation, Integrations, Internal Comms, Lifecycle, Onboarding, Operations, Procurement, Product, Product Marketing, Referrals, Sales, Slack, Support, Website, Word of Mouth

## Cited GrowthDex tactics

- [Bug-vs-feature-request template split at intake](/growth-ideas/bug-vs-feature-request-template-split-at-intake/) - Split intake into separate bug and feature-request templates before the queue starts growing so each report enters triage with the right shape and destination.
- [Channel-specific notification queues for external feedback](/growth-ideas/channel-specific-notification-queues-for-external-feedback/) - Pipe posts from each outside surface into dedicated internal channels so the team can scan by source and notice which room keeps producing useful pain.
- [Minimum required fields for fast feedback filing](/growth-ideas/minimum-required-fields-for-fast-feedback-filing/) - Keep intake templates lean enough that frontline teams can file issues fast while still capturing the few facts engineering and product actually need.
- [Weekly CX on-call for off-platform feedback](/growth-ideas/weekly-cx-on-call-for-off-platform-feedback/) - Rotate one person each week to watch off-platform feedback from social, community, and app-store surfaces so useful demand does not die outside the product queue.
- [Fewer teams first before workspace sprawl](/growth-ideas/fewer-teams-first-before-workspace-sprawl/) - Start the new workspace with fewer teams than you think you need, then add more only after live work shows where the boundaries belong.
- [Hidden-work audit from switch pilot](/growth-ideas/hidden-work-audit-from-switch-pilot/) - Run a one- or two-team pilot and measure how much work was previously going untracked before you pitch the wider switch.
- [Integration cutover checklist before tracker switch](/growth-ideas/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.
- [Read-only shutdown note after cutover](/growth-ideas/read-only-shutdown-note-after-cutover/) - After the migration is complete, put the old tool into read-only mode or shut off access and announce that change in the shared support channel.
- [Shared language guide before org-wide rollout](/growth-ideas/shared-language-guide-before-org-wide-rollout/) - Publish a short internal guide that shows how to label work, name teams, and find daily views before the wider migration starts.
- [Go-live date tied to the old tool's renewal window](/growth-ideas/go-live-date-tied-to-the-old-tools-renewal-window/) - Set the migration go-live date with leadership around the incumbent tool's renewal timing so the switch has a financial forcing function instead of drifting into a soft maybe.
- [Internal transition guide with pilot findings and team quotes](/growth-ideas/internal-transition-guide-with-pilot-findings-and-team-quotes/) - Package the rollout into an internal switch guide that explains the migration choice, shares pilot findings, and includes a few real teammate quotes before asking the rest of the company to move.
- [Migration Slack channel for switcher support](/growth-ideas/migration-slack-channel-for-switcher-support/) - Create one migration Slack channel for rollout questions, resources, and unblockers so the switch feels supported instead of chaotic.
- [Migration task force with office hours](/growth-ideas/migration-task-force-with-office-hours/) - Form a small cross-functional switch team and back it with recurring office hours so the migration has owners, shared language, and visible help.
- [Pre-provision matched users before tracker import](/growth-ideas/pre-provision-matched-users-before-tracker-import/) - Before importing work from another tracker, provision users in the new system with the same email addresses and linked accounts so ownership and comments survive the move cleanly.
- [Switch kit with pitch, pilot, and migration guides](/growth-ideas/switch-kit-with-pitch-pilot-and-migration-guides/) - Package the switch into three separate artifacts: a pitch guide for internal champions, a pilot guide for evaluation, and a migration guide for the move itself.
- [Trial sync before full project-tracker cutover](/growth-ideas/trial-sync-before-full-project-tracker-cutover/) - Offer two-way sync during the trial so a team can test the new workflow without forcing an all-at-once cutover from Jira or GitHub Issues.
- [Customer request linkback close loop](/growth-ideas/customer-request-linkback-close-loop/) - Attach support threads, Slack posts, and other customer conversations directly to product issues, then push the resolution back into the original conversation when it ships.
- [Quality-first product experience flywheel](/growth-ideas/quality-first-product-experience-flywheel/) - Use product quality as a distribution strategy by fixing obvious friction fast and letting delighted users carry the product into other teams.

## Related reading

- [GrowthDex Blog](/blog/)
- [All growth ideas](/growth-ideas/index.md)