# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/linear-top-level-team-import-before-subteam-polish/
- Source: [linear.app](https://linear.app/docs/import-issues)
- GrowthDex source hub: [Linear Docs: Importer](/sources/linear-docs-importer-linear-app/)
- Last checked: 2026-06-08T12:08:13.000Z
- Rarity: uncommon
- Budget: low
- Channels: Migration, Operations, Developer Tools
- Stages: migration, workspace structure, risk reduction, implementation


## Why this can grow

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.

## 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 linear top-level team import before sub-team polish can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Migration and Operations 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 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.

## Adjacent tactics in the same lane

- [Linear open-only pilot import before archive drag](/growth-ideas/linear-open-only-pilot-import-before-archive-drag/) - same source, 2 shared channels, 1 shared stage
- [Reviewable import assistant with bulk reimport safety](/growth-ideas/reviewable-import-assistant-with-bulk-reimport-safety/) - same source, 2 shared stages
- [Linear JQL webhook filter before sync flood](/growth-ideas/linear-jql-webhook-filter-before-sync-flood/) - 3 shared channels, 1 shared stage
- [Source-specific import assistant for switchers](/growth-ideas/source-specific-import-assistant-for-switchers/) - same source, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The switch should look like current work before the cutover](/blog/the-switch-should-look-like-current-work-before-the-cutover/) - migration, project operations, developer tools

## Advisory

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