Jira · Moving out
Move from your Parody back to Jira
Your data is yours, and you can take all of it with you, even after your free month ends. This guide moves a Jira Parody's records into Jira.
Before you start#
Jira Cloud imports CSV files in two ways. Admins use External System Import, which can create parents and children and update existing work items. Everyone else can import from the work item search, up to 250 rows per file and without parent links. This guide uses the admin import.
Who can do this
A Jira admin runs the import. Create the target projects (and boards, for sprints) in Jira first.
What transfers
| In your Parody | In Jira |
|---|---|
| Projects | Projects (created in Jira before importing) |
| Sprints | Sprints (named on work items) |
| Epics | Work items of type Epic |
| Issues | Work items |
| Comments | Comment columns on work items |
What doesn't
- Ideas and service requests. Jira Product Discovery and Jira Service Management have their own imports.
- Rules, filters, and versions. Recreate them in Jira.
- Worklogs. Jira's CSV import reads them only in its own
Log Workformat. - Record history. Exports hold each record as it is now.
1. Export from your Parody#
- Open your Parody and go to Import & export. If your Parody is paused after the free month, use Download everything on the paused screen.
- Select Download everything (JSON) and keep that file. It's the complete backup.
- Download the CSV for each record type below.
Each CSV has:
id: the record's ID in the Parody.- One column per field, named like
due_dateorproject_id. - A
(name)column after every link, such asproject_id (name), holding the linked record's name. Jira can't read Parody IDs, so these are the columns to use for links. source_id, if the records first came from Jira or another tool: their original IDs.
2. Prepare the files for Jira#
Combine epics, work items, and sub-tasks into one file, in that order, with an Issue Type column. Jira links children to parents through Issue Id and Parent, and only when the parent comes first in the file.
Replace people's names with the email addresses of their Jira accounts. Jira asks for the date format during the import; Parody dates are yyyy-MM-dd.
Projects
| Parody column | Jira column |
|---|---|
name | Project name |
key | Project key |
Create each project in Jira first, with the same key. The work item import then puts rows into it by project name or key.
Sprints
| Parody column | Jira column |
|---|---|
name | Sprint |
Jira sets sprints from the Sprint column on each work item. Create the board first, and try a few rows in a test project to check that sprint names are picked up.
Epics
| Parody column | Jira column |
|---|---|
id | Issue Id |
name | Summary |
summary | Description |
status | Status |
target_date | Due date |
project_id (name) | Project name |
Add an Issue Type column set to Epic, and put the epic rows at the top of the same file as the work items below: Jira links a child to its parent only when the parent comes first in the file.
Issues
| Parody column | Jira column |
|---|---|
id | Issue Id |
summary | Summary |
description | Description |
type | Issue Type |
status | Status |
priority | Priority |
assignee | Assignee (email address) |
reporter | Reporter (email address) |
due_date | Due date |
project_id (name) | Project name |
sprint_id (name) | Sprint |
epic_id / parent_issue_id | Parent (the epic's or parent's Issue Id) |
story_points | Story point estimate |
Fill Parent from epic_id, or from parent_issue_id for sub-tasks. Both hold Parody IDs, which match the Issue Id values you gave the epics and parents in the same file.
Comments
| Parody column | Jira column |
|---|---|
body | Comment (one column per comment) |
Add comments to the work item rows as extra Comment columns. Use the same heading for each one; Jira reads repeated headings as several values.
3. Import into Jira#
- In Jira, go to Settings → System → External System Import and choose CSV.
- Upload the file. Set the date format to
yyyy-MM-dd. - Choose the project, or map the Project name column for files that span projects.
- Map each column to its Jira field, and map values where Jira asks (statuses, priorities). For unresolved work items, map Resolution's empty value to Import as blank.
- Run the import, then save the configuration file Jira offers, so you can rerun it for the next file.
Keep files to about 1,500 rows; Atlassian recommends splitting larger imports. When updating existing work items by key, columns you leave out of the file are reset to their defaults.
Prefer to stay within one project without admin rights? Import from Search work items → ⋯ → Import work items from CSV, 250 rows at a time, and set parents afterwards.
4. Check the result#
- Compare Jira's record counts with the row counts of your files.
- Open a few records and check their links, people, and dates.
5. Wind down the Parody#
- Keep the JSON backup somewhere safe.
- Cancel from the billing page. You keep access until the end of the period you've paid for.
- To clear the Parody yourself, use Delete all records on its Import & export page. To have your account and data deleted, reply to any email from us.
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.