Linear top-level team import before sub-team polish
Import into a top-level team first, then convert it to a sub-team after the data lands cleanly.
Why this can grow a startup
Migration breaks trust when hierarchy cleanup blocks the main job of getting live work across. Linear's import path avoids that by separating the concerns: data lands in a top-level team first, and the org-chart refinement happens afterwards. That sounds small, but it keeps the switch focused on continuity instead of making the buyer solve structure, permissions, and historical import in one nervous step.
Source-backed example
Linear says imports cannot target a sub-team directly and instructs teams to import into a top-level team, then convert it into a sub-team afterwards.
Source-reported evidence
Source: Linear Docs: Importer · Browse Linear Docs: Importer tactics
Linear blocks direct sub-team imports and explicitly routes teams through a top-level import first.
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.
When to use it
Use this when Migration, Operations, Developer Tools is relevant to migration, workspace structure, risk reduction and you can run a bounded test with a low 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 Migration and Operations, using evidence from Linear Docs: Importer as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next 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 Linear Docs: Importer
Explore related GrowthDex examples and evidence connected to Linear Docs: Importer.
Open Linear Docs: Importer source hub