# Reviewable import assistant with bulk reimport safety

> Build the migration path inside the product with a review step, selective scope choices, and a clean way to delete and rerun the import.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/reviewable-import-assistant-with-bulk-reimport-safety/
- Source: [linear.app](https://linear.app/docs/import-issues)
- GrowthDex source hub: [Linear Docs: Importer](/sources/linear-docs-importer-linear-app/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: medium
- Channels: Product, Onboarding, Website
- Stages: activation, migration, risk reduction, product-led growth


## Why this can grow

Switchers trust an importer more when it behaves like a guided workflow instead of a black box. Linear's docs show the pieces that matter: preview the fetched data, choose whether to bring only open work or the archive too, map users, and summarize everything before the run starts. The second trust lever is reversibility. If the import can be deleted in bulk and rerun, the buyer has room to experiment without feeling trapped by one bad attempt.

## 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. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 reviewable import assistant with bulk reimport safety can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Onboarding 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 its in-product import assistants retain more data than the CLI route, show review and mapping steps before import, and let teams delete an import in bulk so they can reimport cleanly if needed.

## Adjacent tactics in the same lane

- [Clean-break import pilot for switchers](/growth-ideas/clean-break-import-pilot-for-switchers/) - same source, 2 shared channels, 1 shared stage
- [Linear open-only pilot import before archive drag](/growth-ideas/linear-open-only-pilot-import-before-archive-drag/) - same source, 1 shared channel, 2 shared stages
- [Source-specific import assistant for switchers](/growth-ideas/source-specific-import-assistant-for-switchers/) - same source, 1 shared channel, 2 shared stages
- [Team-scoped project template with milestones and owners](/growth-ideas/team-scoped-project-template-with-milestones-and-owners/) - 3 shared channels, 2 shared stages

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The switch page should finish the move](/blog/the-switch-page-should-finish-the-move/) - SaaS SEO, product-led growth, brand trust

## Advisory

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