# The switch should look like current work before the cutover > Why open-only pilot imports, top-level team staging, mapped Jira owners, filtered sync, and date-backed project graphs make a migration trial feel real. - Canonical HTML: https://growth.iangoh.com/blog/the-switch-should-look-like-current-work-before-the-cutover/ - Published: 2026-06-08 - Updated: 2026-06-08T12:08:13.000Z - Categories: migration, project operations, developer tools - Niches: SaaS, developer tools, B2B SaaS, AI products, internal tools ## On this page - Do not import history just because it exists - Separate hierarchy cleanup from the main migration job - Identity drift kills trust faster than missing polish - Filter the sync before the old system floods the new one - The project should produce a believable timeline early ## Start with these related tactics - [Linear open-only pilot import before archive drag](/growth-ideas/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. - [Linear top-level team import before sub-team polish](/growth-ideas/linear-top-level-team-import-before-subteam-polish/): Import into a top-level team first, then convert it to a sub-team after the data lands cleanly. - [Linear Jira personal-account link before assignee drift](/growth-ideas/linear-jira-personal-account-link-before-assignee-drift/): Have each user connect their own Jira account before dual-run sync so assignee and creator fields keep pointing to the right person. A migration trial usually fails long before the contract or the cutover plan. It fails when the new workspace still feels like a staged demo while the old tool still looks like the place where real work lives. That is why the first win is not feature parity. The first win is making the trial look enough like current work that a team can trust what it sees. ## Do not import history just because it exists [Linear open-only pilot import before archive drag](/growth-ideas/linear-open-only-pilot-import-before-archive-drag/) is the cleanest move in this batch. If the team is still evaluating the product, the workspace should answer today's planning questions first. Old backlog can wait. It belongs next to [reviewable import assistant with bulk reimport safety](/growth-ideas/reviewable-import-assistant-with-bulk-reimport-safety/). One keeps the scope small. The other makes the first pass reversible. ## Separate hierarchy cleanup from the main migration job [Linear top-level team import before sub-team polish](/growth-ideas/linear-top-level-team-import-before-subteam-polish/) sounds operational because it is operational. That is also why it matters. The switch gets calmer when the team can land the data first and rearrange the org shape second. A lot of migrations go sideways because they try to solve every structural preference in the same pass. Buyers do not need that much elegance on day one. They need continuity. ## Identity drift kills trust faster than missing polish [Linear Jira personal-account link before assignee drift](/growth-ideas/linear-jira-personal-account-link-before-assignee-drift/) is the move I would check first in any dual-run trial. If the new issue says the wrong person owns it, the workspace stops feeling real immediately. That pairs naturally with [dual-run sync during trial before full Jira cutover](/growth-ideas/dual-run-sync-during-trial-before-full-jira-cutover/). A dual run only helps if the mirrored work still points to the people who actually own it. ## Filter the sync before the old system floods the new one [Linear JQL webhook filter before sync flood](/growth-ideas/linear-jql-webhook-filter-before-sync-flood/) fixes another quiet trial failure. The new product gets judged by every low-value queue, stale bug class, and legacy ticket type it never needed to inherit. A narrower sync is not cheating. It is a cleaner test of whether the new workflow handles the work you actually care about. ## The project should produce a believable timeline early [Linear start and target dates before graph guesswork](/growth-ideas/linear-start-and-target-dates-before-graph-guesswork/) is where the workspace stops being a container and starts being a planning tool. Once the graph can show scope, velocity, and a live completion estimate, the buyer has something better than a promise. I would read that beside [project overview starts with resources, docs, and milestones](/growth-ideas/project-overview-starts-with-resources-docs-and-milestones/). One makes the room feel ready. The other makes the timeline feel alive. If I were tightening one migration this week, I would import only the live slice, avoid hierarchy fuss during the landing, link every Jira identity that matters, trim the sync with JQL, and put real dates into the project graph early. That is how the switch starts looking like current work instead of a rehearsed demo. If you want help turning a migration trial, project workspace, or switcher path into a cleaner product-led conversion system, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Linear open-only pilot import before archive drag](/growth-ideas/linear-open-only-pilot-import-before-archive-drag/) - Migration, Onboarding, Developer Tools - [Linear top-level team import before sub-team polish](/growth-ideas/linear-top-level-team-import-before-subteam-polish/) - Migration, Operations, Developer Tools - [Linear Jira personal-account link before assignee drift](/growth-ideas/linear-jira-personal-account-link-before-assignee-drift/) - Migration, Product, Developer Tools - [Linear JQL webhook filter before sync flood](/growth-ideas/linear-jql-webhook-filter-before-sync-flood/) - Migration, Operations, Developer Tools - [Linear start and target dates before graph guesswork](/growth-ideas/linear-start-and-target-dates-before-graph-guesswork/) - Product, Onboarding, Developer Tools ## Essay chronology - [Newer essay: The extension page should survive the week after install](/blog/the-extension-page-should-survive-the-week-after-install/) - browser extensions, marketplaces, brand trust - [Older essay: The docs page should show signs of life before support does](/blog/the-docs-page-should-show-signs-of-life-before-support-does/) - documentation, proof surfaces, support-led growth ## Keep reading - [The docs page should let the buyer send the first request](/blog/the-docs-page-should-let-the-buyer-send-the-first-request/) - documentation, API docs, developer tools - [The support switch usually leaks in the routing layer](/blog/the-support-switch-usually-leaks-in-the-routing-layer/) - support-led growth, migration, seo - [The switch should feel boring before it feels done](/blog/the-switch-should-feel-boring-before-it-feels-done/) - switcher intent, migration, trust ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Linear Docs: Importer](https://linear.app/docs/import-issues) · [GrowthDex source hub](/sources/linear-docs-importer-linear-app/) - [Linear Docs: Importer](https://linear.app/docs/import-issues) · [GrowthDex source hub](/sources/linear-docs-importer-linear-app/) - [Linear Docs: Jira](https://linear.app/docs/jira) · [GrowthDex source hub](/sources/linear-docs-jira-linear-app/) - [Linear Docs: Jira](https://linear.app/docs/jira) · [GrowthDex source hub](/sources/linear-docs-jira-linear-app/) - [Linear Docs: Project overview](https://linear.app/docs/project-overview) · [GrowthDex source hub](/sources/linear-docs-project-overview-linear-app/) ## Editing notes - Kept the piece on one plain claim: the new workspace has to look like live work before a team will trust the migration. - Used ordinary migration objects like stale backlog, assignees, JQL filters, and project dates instead of abstract transformation language. - Cut broad platform claims and tied each paragraph to one concrete failure mode in a switch trial. - Ended on a practical weekly sequence and one advisory CTA instead of a polished migration conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.