Before you start
- You must be a WorkThroughLine administrator.
- Create a separate export for each large Jira project.
- Agree on a date after which the team stops changing Jira.
- Do not rename CSV columns.
1. Export from Jira Cloud
- Open the Jira project.
- Select the “List” view.
- Open the three-dot menu.
- Choose “Export”.
- Download “Export CSV - all fields”.
Why “all fields”?
This variant includes comments, sprints, parent data, links and custom fields needed for accurate mapping.
Official Atlassian CSV guide2. Upload the original file
In WorkThroughLine open Settings > Import, select Jira and upload the original UTF-8 CSV. Do not open and resave it with an old Excel version.
3. Run preview without writes
- Project and item counts
- Jira statuses, types and priorities
- Users that can and cannot be matched
- Sprints and missing dates
- Comments, links and additional fields
4. Make mapping decisions
For each unknown value, choose the matching WorkThroughLine status, type or priority. Map unknown users to existing members or intentionally leave them unassigned.
5. Confirm import
Import runs in the background with visible status and history. The encrypted temporary CSV is cleared after successful completion.
6. Verify before cutover
- Compare active item counts.
- Open several epics and subtasks.
- Check comments and issue links.
- Confirm the active sprint and unassigned users.
- Check JPD opportunities, interviews and insights when applicable.
Large migrations
For more than 10,000 items or 15 MB, split by project, date range or JQL filter. Stable Jira source identity prevents duplicates across consecutive files.
Attachments
CSV carries attachment references, not physical files. Direct Jira Cloud connection is designed to copy them after production OAuth verification.
Repeat import and manual changes
You can run the same file again. Stable Jira identity prevents duplicates. If someone manually changed a previously imported item, safe mode skips it and reports a conflict.