How to migrate from Linear to Huly
Issues and tasks usually migrate fine via CSV; what almost never survives is your automation and custom workflow-state configuration.
- 1
Export your projects from Linear to CSV
Filter by project and export issues/tasks with all fields (status, assignee, labels, due date). Export one project at a time to keep field mapping simple.
- 2
Map fields when importing into Huly
Before importing, create the same statuses and labels in Huly that you used in Linear — if the names don't match exactly, the importer will leave those fields empty.
- 3
Rebuild your automation workflows
Rules like "notify X when an issue closes" aren't exported. Write down your current automations before migrating and recreate them one by one in Huly.
- 4
Migrate team by team, not all at once
Start with one pilot team or project for a full sprint before moving the rest — that way you catch mapping issues at low risk.
Before cancelling Linear
Before cancelling Linear, also export the comments on your most important issues — some importers only bring over the issue itself, not the comment history.
Ready to deploy Huly?
Full profile with license, tech stack and ready-to-copy docker-compose.
View Huly's profileThese steps are a general guideline — the exact export menu can vary depending on Linear's plan and version.