Skip to content
Vorkhurry — home

5 min read

Importing your work

Jira, Linear or CSV — previewed, mapped, validated, and resumable.

The job is rows, not a blob

Every source record becomes an import row with its own status. That single decision is what makes the rest possible: the job is resumable because already-imported rows are skipped, errors are reported per record rather than as one failure, and a re-run updates what it created instead of duplicating it.

The steps

  1. Create the job and connect the source — API credentials for Jira or Linear, a file for CSV.
  2. Preview: the source is fetched or parsed into rows, and you see what was found.
  3. Map: point the source's statuses at your own workflow statuses.
  4. Validate: each row is checked and conflicts with existing work are detected.
  5. Resolve: decide per conflict whether to create, update or skip.
  6. Run it. Cancel, retry or delete the job at any point.

What it does not claim

This is an issue import, not a full-fidelity migration of every field, workflow, automation and add-on a mature Jira instance accumulates. Preview the rows and check the mapping before you run it.

All guides

Start with your team, not with a sales call

Create a workspace, invite the people you work with, and bring your existing issues in from Jira, Linear or a CSV.

Get startedSee pricing