Back to GrowthDex
Growth idea action plan

Linear open-only pilot import before archive drag

Pilot the migration with a few teams and open issues first before dragging years of stale backlog into the evaluation workspace.

rare tacticlow budget

Why this can grow a startup

A switch stalls when the first demo workspace already feels bloated, historical, and hard to parse. Linear's importer docs are blunt about that tradeoff: some teams use the move as a clean break, some keep a fuller history, and evaluators often start by importing only a few teams. Pair that with the option to bring only open issues while sending old work to the archive, and the trial starts to feel like current work instead of a museum of the old system.

Company example

Linear recommends considering whether old data needs to live in the new workspace at all, suggests piloting with just a few teams during evaluation, and lets import assistants bring only open issues or also place closed and stale work into the archive.

Source and metric

Source: Linear Docs: Importer · Browse Linear Docs: Importer tactics

Linear import assistants let teams choose open issues only or also import closed and stale issues into the archive, and the docs recommend piloting with just a few teams during evaluation.

MigrationOnboardingDeveloper Toolsswitcher intentactivationmigrationworkspace setup
GrowthDex operator note

When to use it

Use this when Migration, Onboarding, Developer Tools is relevant to switcher intent, activation, migration 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

  1. Read Linear Docs: Importer and identify what is directly supported.
  2. Choose one channel context: Migration, Onboarding, Developer Tools.
  3. Define the test around Linear import assistants let teams choose open issues only or also import closed and stale issues into the archive, and the docs recommend piloting with just a few teams during evaluation..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian