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.
Company 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 and metric
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.
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.
Founder checklist
- Read Linear Docs: Importer and identify what is directly supported.
- Choose one channel context: Migration, Operations, Developer Tools.
- Define the test around Linear blocks direct sub-team imports and explicitly routes teams through a top-level import first..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.