linear-migration-deep-dive
Migrate from Jira, Asana, GitHub Issues, or other tools to Linear. Use when planning a migration, executing data transfer, or mapping workflows between issue tracking tools. Trigger: "migrate to linear", "jira to linear", "asana to linear", "import to linear", "linear migration", "github issues to linear".
Best use case
linear-migration-deep-dive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Migrate from Jira, Asana, GitHub Issues, or other tools to Linear. Use when planning a migration, executing data transfer, or mapping workflows between issue tracking tools. Trigger: "migrate to linear", "jira to linear", "asana to linear", "import to linear", "linear migration", "github issues to linear".
Teams using linear-migration-deep-dive should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/linear-migration-deep-dive/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How linear-migration-deep-dive Compares
| Feature / Agent | linear-migration-deep-dive | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Migrate from Jira, Asana, GitHub Issues, or other tools to Linear. Use when planning a migration, executing data transfer, or mapping workflows between issue tracking tools. Trigger: "migrate to linear", "jira to linear", "asana to linear", "import to linear", "linear migration", "github issues to linear".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Linear Migration Deep Dive
## Overview
Comprehensive guide for migrating from Jira, Asana, or GitHub Issues to Linear. Covers assessment, workflow mapping, data export, transformation, batch import with hierarchy support, and post-migration validation. Linear also has a built-in importer (Settings > Import) for Jira, Asana, GitHub, and CSV.
## Prerequisites
- Admin access to source system (Jira/Asana/GitHub)
- Linear workspace with admin access
- API keys for both source and Linear
- Migration timeline and rollback plan
## Instructions
### Step 1: Migration Assessment Checklist
```
Data Volume
[ ] Total issues/tasks: ___
[ ] Projects/boards: ___
[ ] Users to map: ___
[ ] Attachments: ___
[ ] Custom fields: ___
[ ] Comments: ___
Workflow Analysis
[ ] Source statuses documented
[ ] Status-to-state mapping defined
[ ] Priority mapping defined
[ ] Issue type-to-label mapping defined
[ ] Automations to recreate: ___
Timeline
[ ] Migration window: ___
[ ] Parallel run period: ___
[ ] Cutover date: ___
[ ] Rollback deadline: ___
```
### Step 2: Workflow Mapping
**Jira -> Linear:**
| Jira Status | Linear State (type) |
|-------------|-------------------|
| To Do | Todo (unstarted) |
| In Progress | In Progress (started) |
| In Review | In Review (started) |
| Blocked | In Progress (started) + "Blocked" label |
| Done | Done (completed) |
| Won't Do | Canceled (canceled) |
| Jira Priority | Linear Priority |
|---------------|----------------|
| Highest/Blocker | 1 (Urgent) |
| High | 2 (High) |
| Medium | 3 (Medium) |
| Low/Lowest | 4 (Low) |
| Jira Issue Type | Linear Label |
|-----------------|-------------|
| Bug | Bug |
| Story | Feature |
| Task | Task |
| Epic | (becomes Project or parent issue) |
**Asana -> Linear:**
| Asana Section | Linear State |
|---------------|-------------|
| Backlog | Backlog (backlog) |
| To Do | Todo (unstarted) |
| In Progress | In Progress (started) |
| Review | In Review (started) |
| Done | Done (completed) |
### Step 3: Export from Source System
**Jira Export:**
```typescript
// src/migration/jira-exporter.ts
interface JiraIssue {
key: string;
summary: string;
description: string;
status: string;
priority: string;
issuetype: string;
assignee?: string;
labels: string[];
storyPoints?: number;
parent?: string;
subtasks: string[];
}
async function exportJiraProject(
baseUrl: string,
projectKey: string,
authToken: string
): Promise<JiraIssue[]> {
const issues: JiraIssue[] = [];
let startAt = 0;
const maxResults = 100;
while (true) {
const jql = `project = ${projectKey} ORDER BY created ASC`;
const response = await fetch(
`${baseUrl}/rest/api/3/search?jql=${encodeURIComponent(jql)}&startAt=${startAt}&maxResults=${maxResults}&fields=summary,description,status,priority,issuetype,assignee,labels,customfield_10016,parent,subtasks`,
{ headers: { Authorization: `Basic ${authToken}`, Accept: "application/json" } }
);
const data = await response.json();
for (const issue of data.issues) {
issues.push({
key: issue.key,
summary: issue.fields.summary,
description: issue.fields.description?.content
? convertAtlassianDocToMarkdown(issue.fields.description)
: issue.fields.description ?? "",
status: issue.fields.status.name,
priority: issue.fields.priority?.name ?? "Medium",
issuetype: issue.fields.issuetype.name,
assignee: issue.fields.assignee?.emailAddress,
labels: issue.fields.labels ?? [],
storyPoints: issue.fields.customfield_10016,
parent: issue.fields.parent?.key,
subtasks: issue.fields.subtasks?.map((s: any) => s.key) ?? [],
});
}
startAt += maxResults;
if (startAt >= data.total) break;
}
console.log(`Exported ${issues.length} issues from Jira ${projectKey}`);
return issues;
}
```
**Jira Markup -> Markdown Converter:**
```typescript
function convertJiraToMarkdown(text: string): string {
if (!text) return "";
return text
.replace(/h([1-6])\.\s/g, (_, level) => "#".repeat(parseInt(level)) + " ")
.replace(/\*([^*]+)\*/g, "**$1**")
.replace(/_([^_]+)_/g, "*$1*")
.replace(/\{code(?::([^}]*))?\}([\s\S]*?)\{code\}/g, "```$1\n$2\n```")
.replace(/\{noformat\}([\s\S]*?)\{noformat\}/g, "```\n$1\n```")
.replace(/^\*\s/gm, "- ")
.replace(/^#\s/gm, "1. ")
.replace(/\[([^|]+)\|([^\]]+)\]/g, "[$1]($2)");
}
```
### Step 4: Transform to Linear Format
```typescript
interface LinearImportIssue {
title: string;
description: string;
priority: number;
stateId: string;
assigneeId?: string;
labelIds: string[];
estimate?: number;
parentId?: string;
sourceId: string; // Original ID for tracking
}
async function transformJiraIssue(
jiraIssue: JiraIssue,
stateMap: Map<string, string>,
userMap: Map<string, string>,
labelMap: Map<string, string>
): Promise<LinearImportIssue> {
// Priority mapping
const priorityMap: Record<string, number> = {
Highest: 1, Blocker: 1,
High: 2,
Medium: 3,
Low: 4, Lowest: 4,
};
// Map labels
const labelIds: string[] = [];
// Issue type becomes a label
const typeLabel = labelMap.get(jiraIssue.issuetype);
if (typeLabel) labelIds.push(typeLabel);
// Original Jira labels
for (const label of jiraIssue.labels) {
const mapped = labelMap.get(label);
if (mapped) labelIds.push(mapped);
}
return {
title: jiraIssue.summary,
description: convertJiraToMarkdown(jiraIssue.description),
priority: priorityMap[jiraIssue.priority] ?? 3,
stateId: stateMap.get(jiraIssue.status) ?? stateMap.get("Todo")!,
assigneeId: jiraIssue.assignee ? userMap.get(jiraIssue.assignee) : undefined,
labelIds,
estimate: jiraIssue.storyPoints ?? undefined,
sourceId: jiraIssue.key,
};
}
```
### Step 5: Import to Linear
```typescript
import { LinearClient } from "@linear/sdk";
async function importToLinear(
client: LinearClient,
teamId: string,
issues: JiraIssue[],
stateMap: Map<string, string>,
userMap: Map<string, string>,
labelMap: Map<string, string>
): Promise<{ created: number; errors: number; idMap: Map<string, string> }> {
const idMap = new Map<string, string>(); // sourceId -> linearId
let created = 0;
let errors = 0;
// Sort: parents first, then children
const sorted = [...issues].sort((a, b) => {
if (a.subtasks.length > 0 && !a.parent) return -1; // Parents first
if (b.subtasks.length > 0 && !b.parent) return 1;
return 0;
});
for (const jiraIssue of sorted) {
try {
const transformed = await transformJiraIssue(jiraIssue, stateMap, userMap, labelMap);
// Set parent if it was already imported
if (jiraIssue.parent && idMap.has(jiraIssue.parent)) {
transformed.parentId = idMap.get(jiraIssue.parent);
}
const result = await client.createIssue({
teamId,
title: transformed.title,
description: `${transformed.description}\n\n---\n*Migrated from ${jiraIssue.key}*`,
priority: transformed.priority,
stateId: transformed.stateId,
assigneeId: transformed.assigneeId,
labelIds: transformed.labelIds,
estimate: transformed.estimate,
parentId: transformed.parentId,
});
if (result.success) {
const issue = await result.issue;
idMap.set(jiraIssue.key, issue!.id);
created++;
if (created % 25 === 0) console.log(`Imported ${created}/${sorted.length}`);
}
// Rate limit: 100ms between requests
await new Promise(r => setTimeout(r, 100));
} catch (error: any) {
console.error(`Failed to import ${jiraIssue.key}: ${error.message}`);
errors++;
}
}
console.log(`Import complete: ${created} created, ${errors} errors`);
return { created, errors, idMap };
}
```
### Step 6: Post-Migration Validation
```typescript
async function validateMigration(
client: LinearClient,
teamId: string,
sourceIssues: JiraIssue[],
idMap: Map<string, string>
): Promise<{ valid: boolean; issues: string[] }> {
const problems: string[] = [];
// Check all issues were imported
if (idMap.size < sourceIssues.length) {
problems.push(`Missing: ${sourceIssues.length - idMap.size} issues not imported`);
}
// Sample validation: check 50 random issues
const sample = sourceIssues.slice(0, 50);
for (const source of sample) {
const linearId = idMap.get(source.key);
if (!linearId) {
problems.push(`${source.key}: not imported`);
continue;
}
try {
const issue = await client.issue(linearId);
if (issue.title !== source.summary) {
problems.push(`${source.key}: title mismatch`);
}
} catch {
problems.push(`${source.key}: not found in Linear (${linearId})`);
}
await new Promise(r => setTimeout(r, 50));
}
return { valid: problems.length === 0, issues: problems };
}
```
## Post-Migration Checklist
```
[ ] All issues imported and validated
[ ] Parent/child relationships correct
[ ] Labels and priorities mapped correctly
[ ] User assignments transferred
[ ] Integrations reconfigured (GitHub, Slack)
[ ] Team workflows customized in Linear
[ ] Team trained on Linear
[ ] Source system set to read-only
[ ] Parallel run period started (2 weeks recommended)
[ ] Archive source system after parallel run
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| User not found | Unmapped email | Add to userMap |
| Rate limited | Too fast import | Increase delay to 200ms |
| State not found | Unmapped status | Update stateMap |
| Parent not found | Import order wrong | Sort parents before children |
| Markup broken | Incomplete conversion | Improve markdown converter |
## Resources
- [Linear Import (Built-in)](https://linear.app/docs/import-issues)
- [Jira REST API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/)
- [Asana API](https://developers.asana.com/reference)
- [Linear GraphQL API](https://linear.app/developers/graphql)Related Skills
workhuman-upgrade-migration
Workhuman upgrade migration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman upgrade migration".
wispr-upgrade-migration
Wispr Flow upgrade migration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr upgrade migration".
windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
windsurf-migration-deep-dive
Migrate to Windsurf from VS Code, Cursor, or other AI IDEs with full configuration transfer. Use when migrating a team to Windsurf, transferring Cursor rules, or evaluating Windsurf against other AI editors. Trigger with phrases like "migrate to windsurf", "switch to windsurf", "windsurf from cursor", "windsurf from copilot", "windsurf evaluation".
webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
webflow-migration-deep-dive
Execute major Webflow migrations — from other CMS platforms to Webflow CMS, between Webflow sites, or large-scale content re-architecture using the Data API v2 bulk endpoints, strangler fig pattern, and data validation. Trigger with phrases like "migrate to webflow", "webflow migration", "import into webflow", "webflow replatform", "move content to webflow", "webflow bulk import", "wordpress to webflow".
vercel-upgrade-migration
Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection. Use when upgrading Vercel CLI versions, migrating Node.js runtimes, or updating Next.js between major versions on Vercel. Trigger with phrases like "upgrade vercel", "vercel migration", "vercel breaking changes", "update vercel CLI", "next.js upgrade on vercel".
vercel-migration-deep-dive
Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".
veeva-upgrade-migration
Veeva Vault upgrade migration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva upgrade migration".
veeva-migration-deep-dive
Veeva Vault migration deep dive for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva migration deep dive".
vastai-upgrade-migration
Upgrade Vast.ai CLI, migrate API versions, and handle breaking changes. Use when upgrading vastai CLI, detecting deprecations, or migrating between API versions. Trigger with phrases like "upgrade vastai", "vastai migration", "vastai breaking changes", "update vastai CLI".
vastai-migration-deep-dive
Migrate GPU workloads to or from Vast.ai, or between GPU providers. Use when switching from AWS/GCP/Azure GPU instances to Vast.ai, migrating between GPU types, or re-platforming ML infrastructure. Trigger with phrases like "migrate to vastai", "vastai migration", "switch to vastai", "vastai from aws", "vastai from lambda".