Skip to content
Skills Library
Management & product · Planning

linear-migration-deep-dive

/linear-migration-deep-dive

Plan and execute a controlled migration into Linear using supported import assistants or the CLI importer. Use when moving issues from Jira, GitHub, Asana, Shortcut, another Linear workspace, or CSV. Trigger with "migrate to Linear", "import issues into Linear", or "plan Linear cutover".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Plan and execute a controlled migration into Linear using supported import assistants or the CLI importer. Use when moving issues from Jira, GitHub, Asana, Shortcut, another Linear workspace, or CSV. Trigger with "migrate to Linear", "import issues into Linear", or "plan Linear cutover".

Triggers from the description

migrate to Linearimport issues into Linearplan Linear cutover

Arguments

/linear-migration-deep-dive [source-system] [pilot|cutover|reconcile]
Original author description

Plan and execute a controlled migration into Linear using supported import assistants or the CLI importer. Use when moving issues from Jira, GitHub, Asana, Shortcut, another Linear workspace, or CSV. Trigger with "migrate to Linear", "import issues into Linear", or "plan Linear cutover".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 76 lines, 572 words
SKILL.md preview
---
name: linear-migration-deep-dive
description: >-
  Plan and execute a controlled migration into Linear using supported import assistants or the CLI importer. Use when moving issues from Jira, GitHub, Asana, Shortcut, another Linear workspace, or CSV. Trigger with "migrate to Linear", "import issues into Linear", or "plan Linear cutover".
argument-hint: "[source-system] [pilot|cutover|reconcile]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.13.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- linear
- data-migration
model: inherit
effort: high
compatibility: Designed for Claude Code; live verification requires network access and an approved Linear workspace credential
---
# Linear Workspace Data Migration

## Overview

Choose the supported importer that preserves the required data, pilot a bounded team, and prove mappings and rollback before cutover.

## Prerequisites

- The target repository, Linear workspace, environment, and accountable owner
- Current security, privacy, compliance, capacity, and change-control requirements
- An approved Linear credential only when a bounded live verification is necessary

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect code, configuration, and evidence. Use `WebFetch` only for current first-party Linear documentation and package metadata. Use `Write` or `Edit` only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables.

## Current Contract

- Imports require a workspace admin; dedicated import assistants are preferred because they retain more source data and can support bulk deletion for a limited time.
- The CLI importer is for sources without a dedicated assistant and does not preserve all data such as comments or projects.
- Re-importing the same source into the same team skips already-imported issues unless the prior import is deleted first.

## Authentication

Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use `Authorization: <API_KEY>`; OAuth tokens use `Authorization: Bearer <ACCESS_TOKEN>`. Store credentials server-side in an approved secret manager.

Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions.

## Instructions

1. Inventory source entities, volumes, users, teams, statuses, labels, projects, comments, attachments, timestamps, and compliance constraints.
2. Choose a dedicated assistant when available; use the CLI only after documenting the data it cannot preserve.
3. Define deterministic user, team, workflow, priority, estimate, and label mappings plus explicit exclusions.
4. Run a small pilot into an approved destination team and validate counts, samples, permissions, links, and timestamps.
5. Approve the cutover window, source freeze, communications, duplicate policy, rollback window, and accountable owners.
6. After import, reconcile counts and sampled semantics, preserve receipts, and keep the legacy source read-only for the approved period.

## Approval Boundaries

Do not create, reveal, rotate, or revoke credentials; authorize an OAuth app; change scopes or team access; create, mutate, archive, or delete workspace data; configure or re-enable webhooks; import or export data; change roles, SCIM, or audit streaming; transmit diagnostics; change paid entitlements; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.

## Output

Return the workspace and team scope, auth mode without credential value, files and contracts inspected, exact operation names, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.

## Error Handling

| Condition | Response |
|---|---|
| Unsupported field | Record the loss and choose an archive or alternate migration path before cutover. |
| User mapping ambiguous | Require owner-confirmed mapping; do not create or merge identities automatically. |
| Pilot incorrect | Delete the pilot only while the supported option remains and after approval, then repair mappings. |
| Rollback window unknown | Do not cut over until current importer deletion behavior is verified. |

## Examples

Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.

Input:

```text
source=jira; teams=2; issues=500; mode=pilot; comments=required
```

Expected handoff:

```text
method=dedicated-assistant; mappings=review; cutover=not-approved
```

## Resources

- [Skill-specific official documentation](references/official-docs.md)
- [Linear developer documentation index](https://linear.app/llms.txt)
- [Linear GraphQL API](https://linear.app/developers/graphql.md)
Files in this package (2)
  • SKILL.md 5 KB
  • references/official-docs.md 3 KB

Versions

RepositoryScoreLicence
This page · jeremylongshore/tons-of-skills-marketplace100MIT
HelixDevelopment/agent95MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 752feb81d6cd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100draft
    Use when asked to file or write a ticket, bug report, Jira epic, Linear issue or regression, GitLab issue, Asana task, Trello card, or Shortcut story.
  • 100clickup-migration-deep-dive
    Plan and execute resumable migrations into or between ClickUp Workspaces with explicit mapping, stable source IDs, bounded writes, and reconciliation. Use when moving Jira, Asana, Trello, or ClickUp data. Trigger with "migrate to ClickUp", "ClickUp migration", or "clone ClickUp Workspace".
  • 100ticket-draft
    Use when asked to file or write a ticket, bug report, Jira epic, Linear issue or regression, GitLab issue, Asana task, Trello card, or Shortcut story.
  • 90dev10x:linear
    Linear issue tracker operations via MCP tools. Get, create, update issues and list comments. Documentation-only skill — no scripts. TRIGGER when: performing CRUD operations on Linear issues, comments, or statuses. DO NOT TRIGGER when: using GitHub Issues or JIRA (use…
  • 100use-linear-cli
    Use when driving Linear through linear-cli for issues, bulk operations, search, or git and PR workflows.
  • 100start-ticket
    Use when starting work on an existing Jira, Asana, Linear, GitHub, or GitLab issue — given its key or URL — that must become an implementation plan before any code is written.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.