Jira · Moving in

Move from Jira to a Parody

Export your records from Jira, import them into a Jira Parody with CSV files, check them, then switch over. You can move back the same way: Move back to Jira.

Before you start#

Jira Cloud exports search results as CSV. Atlassian now calls issues work items; older screens and exports may still say issues. You'll run a few searches, export each one, and import the files into your Parody.

Who can do this

Anyone who can browse the projects can export their work items. You don't need to be a Jira admin.

What comes over

In JiraIn your Parody
ProjectsProjects
SprintsSprints
EpicsEpics
Work items (formerly issues)Issues
CommentsComments

What doesn't

  • Attachments. The export lists them as links that need a Jira login.
  • Workflows, screens, permissions, and notification schemes.
  • Automation rules. Recreate them on the Rules screen; in hosted Parodies they're listed but don't run yet.
  • Work item history, watchers, votes, and time tracking.
  • Custom fields other than story points.
  • Anything the Jira Parody has no field for. Check the column tables below; columns without a match are left out.

1. Set up your Parody#

  1. Create a Jira Parody with at least these features, so every record type has a home: Projects, Sprints, Epics, Issues, Comments. See what's in the Jira Parody.
  2. New Parodies come with sample records. Open Import & export in your Parody, and under Start empty, delete them.

2. Export from Jira#

  1. In Jira, open the work item search (Filters → Search work items) and switch to JQL.
  2. Run each search below, adding your project, for example project = MOB AND ….
  3. Select Export, then Export CSV (current fields). Pick the columns in the tables below first, so the file stays small. All fields works too but makes very large files.

Large projects

A direct export stops at 1,000 work items. Newer sites export up to 10,000 in the background; otherwise split the search by date, such as created < 2025-01-01 and created >= 2025-01-01.

What to export:

  • Projects: Jira has no CSV export of the project list. Every work item export carries its project's columns, so copy the distinct Project name, Project key, and Project lead values into a Projects sheet. A short list is quicker to type.
  • Sprints: there's no sprint export. The Sprint column on work items holds sprint names, so make a Sprints sheet with each sprint's name and project, and add dates from the board if you want them.
  • Epics: search with issuetype = Epic, then export.
  • Work items (formerly issues): search with issuetype != Epic AND issuetype not in subTaskIssueTypes(), then export. Export sub-tasks as a second file with issuetype in subTaskIssueTypes().
  • Comments: they come with the work item export, one Comment column per comment, each cell holding the date, author, and text separated by semicolons. Split them into a Comments sheet with one row per comment, or leave them behind.

3. Prepare the files#

You need one CSV per record type. Open each export in a spreadsheet app, make the changes below, and save it as CSV (UTF-8). Keep the header row.

Dates can stay as Jira writes them, like 21/Nov/26 2:30 PM; the importer reads that format. People columns hold display names, which carry over as written.

Keep the ID column

Map Jira's own ID to ID. Your Parody remembers it, so later files can link to the record by that ID, and importing a fresh export later updates records instead of duplicating them.

Projects

Jira columnParody field
Project nameName
Project keyKey
Project leadLead
Project descriptionDescription

Sprints

Jira columnParody field
SprintName
Project nameProject
Start dateStart date
End dateEnd date
StateState

Epics

Jira columnParody field
Issue keyID (match and link rows)
SummaryName
Project nameProject
DescriptionSummary
StatusStatus
Due dateTarget date

If the Parent column on your work items holds numbers rather than keys like MOB-12, those are work item IDs: map Issue id to ID here instead of Issue key.

Issues

Jira columnParody field
Issue keyID (match and link rows)
SummarySummary
DescriptionDescription
Issue TypeType
StatusStatus
PriorityPriority
AssigneeAssignee
ReporterReporter
Due dateDue date
Project nameProject
SprintSprint
ParentEpic
Custom field (Story point estimate)Story points

For the sub-tasks file, map Parent to Parent issue instead of Epic, and import it after the main file.

A work item in more than one sprint gets several Sprint columns. Keep the last one, which is its current sprint. Story points may be called Custom field (Story Points) on older sites.

Comments

Jira columnParody field
Issue keyIssue
AuthorAuthor
BodyBody

4. Import, in this order#

Import parents before the records that link to them, so links resolve:

  1. Projects
  2. Sprints
  3. Epics
  4. Issues
  5. Comments

For each file:

  1. In your Parody, open Import & export.
  2. Under Import, choose the record type and the CSV file.
  3. Check the column list. Columns named like the tables above are matched for you; pick a field for any that aren't, or leave them out.
  4. Select Import. If any row has a problem, nothing is written and you get a list of the problems by line number. Fix the file and import again, or tick Skip rows with problems.

Files can hold up to 5,000 rows and 4 MB. Split bigger exports and import the parts one after another. The full rules are in Import & export.

5. Check the result#

  • Compare the counts on your Parody's overview with the row counts of your files.
  • Open a few records of each type and check their links (the project on a task, the account on a contact).
  • Open the boards and reports and check that records sit in the right columns.

6. Switch over#

  1. Pick a cutover time and ask your team to stop editing in Jira.
  2. Export again and import the new files. Rows with an ID you've imported before update those records; new rows are added.
  3. Share the Parody's address with your team, and keep Jira read-only until you're sure nothing is missing.

Troubleshooting#

MessageWhat to do
No … named or with id "…"The record it links to isn't in the Parody yet. Import that record type first, or check the name is spelled exactly the same.
"…" matches 2 … recordsSeveral records share that name. Also map the column that links to their parent (the project or board), or use the ID instead of the name.
… is not a date we can readUse YYYY-MM-DD. Day-first dates like 21/11/2026 aren't read, because 03/04/2026 would be ambiguous.
… is not a numberRemove words and units other than currency symbols, commas, and %.
The file has more than … rowsSplit it into files of up to 5,000 rows.

Sources

Checked against these pages on 2026-11-21. Vendors change their export and import tools often; if a step doesn't match what you see, their page wins.