linear-migration-deep-dive
Migrate from Jira, Asana, GitHub Issues, or other tools to Linear. Use when planning a migration to Linear, executing data transfer, or mapping workflows between tools. Trigger with phrases like "migrate to linear", "jira to linear", "asana to linear", "import to linear", "linear migration".
Install
mkdir -p .claude/skills/linear-migration-deep-dive && curl -L -o skill.zip "https://mcp.directory/api/skills/download/8778" && unzip -o skill.zip -d .claude/skills/linear-migration-deep-dive && rm skill.zipInstalls to .claude/skills/linear-migration-deep-dive
About this skill
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:
// 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:
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
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
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
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
Content truncated.
More by jeremylongshore
View all skills by jeremylongshore →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
pdf-to-markdown
aliceisjustplaying
Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.
Related MCP Servers
Browse all serversOptimize your codebase for AI with Repomix—transform, compress, and secure repos for easier analysis with modern AI tool
WayStation: a secure integration hub connecting Monday, Asana, Notion & Slack so teams access tools and Jira ticketing w
Extend your developer tools with GitHub MCP Server for advanced automation, supporting GitHub Student and student packag
PAL MCP Server — multi-model proxy for OpenAI, Gemini, OpenRouter, Azure, Grok, Ollama & custom endpoints. Use Claude Co
Pipedream — Access hosted MCP servers or deploy your own for 2,500+ APIs (Slack, GitHub, Notion, Google Drive) with buil
Chrome extension-based MCP server that exposes browser functionality to AI assistants. Control tabs, capture screenshots
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.