1. Home
  2. Knowledge Base
  3. Jira Software Data Migration Checklist

Jira Software Data Migration Checklist

Let's break down how to set up and run a seamless Jira Software data migration with Relokia's Migration Wizard. This Jira Software data migration checklist has all the steps you need for both bulk migration and one-by-one project migration.

What project management data can you import to Jira Software in a default migration?

EntityStatus in a default migration
Sections (task list)Possible in a custom work
Groups of tasks (the status of a task)Possible in a custom work
TasksAvailable
Task commentsAvailable
Created_at CommentPossible in a custom work
Comment authorPossible in a custom work
Task attachmentsAvailable
Task tagsAvailable
Task custom fieldsAvailable
Inline imagesPossible in a custom work
Task due dateAvailable
Task completed at datePossible in a custom work
Task created at datePossible in a custom work
Task updated datePossible in a custom work
Subtasks (in the task)Available
UsersAvailable

Important:

  • Task attachments will migrate within the comment body.
  • Multi-select type fields will be transferred as select ones, taking the first selected value.
  • Updated-at dates of tasks will be imported as the dates of data migration if you are switching to a trial version of Jira Software.
  • If certain records don't move in a Free Demo, aren't shown here, or are marked as 'Possible in custom work,' reach out to us for more info on how to transfer that data into Jira Software.

There are two methods for transferring data into Jira Software:

To help you navigate each method, check the separate lists for both types of Jira Software migration.

One-by-one project migration to Jira Software

Switching to Jira Software project by project ensures a smooth and focused data import. Let's explore how this one-by-one migration approach simplifies and enhances the import for each project.

Step and detailsPriority
Get started, set up your account at app.relokia.comLow
Pick your source project management system from the list and provide the required access details. The information needed varies depending on the project management platforms you choose.Low
Configure your Source connection and choose a project you want to export.Low

Create users on Jira Software, follow these steps:

Navigate to Settings → select User management → click on Invite users → enter the email address → choose a product role for Jira Software → Send invitation by clicking Invite users.

High

Configure email visibility for every user in Jira Software.

Click on an account icon → Manage accountProfile and visibilityContactAnyone.

High

Create a project to which you’re going to import data and add users to it.

Navigate to ProjectsCreate projectKanbanUse templateSelect a company-managed project → add project details → click Next.

High

Set up custom fields in Jira Software manually

  • if you plan to migrate them to different projects than they are on the Source,
  • if you have other options (e.g., for a dropdown field) or
  • if your Source field names differ from those you have in Jira Software.

Go to SettingsIssues → click on Custom fields → choose Create custom fields → select a field type → click Next → fill in the name and description → click Create.

High

Generate an API Token for Jira Software.

Go to https://id.atlassian.com/manage/api-tokensCreate API token → fill in the Label for identification purposes → click Create, then copy the token to the clipboard.

Be sure to save the API Token as it won’t be visible later.

High

Connect Jira Software to the Migration Wizard and specify import settings, follow these steps:

  • Select Jira Software as the Target and connect it to Migration Wizard.
  • Fill in the URL, email address, and API Token for authentication.
  • Choose the Project, Issue type, and Sub-task type for the test migration.
Low
Choose the data you want to transfer to Jira Software: users and issues along with comments, attachments, tags, and custom fields.Low
Match user profiles. If there are unassigned, deleted, or inactive users, select a default user to map those records. Once you've made your choices, click “Save matching.”Mid
Map issue fields, including default and custom ones. To map a custom field, simply choose it and click “Add the same field in Jira Software.” It'll then appear at the bottom. When finished, click "Save mapping.”Mid
Set up a Free Demo to assess your migration. Reports will provide details on migrated, skipped, and failed records, along with lists of record IDs from the Source and their new IDs in Jira Software. Just click the button next to the report to view it.Low
Run a Demo Migration for each Source project from which you want to transfer data.Mid
To edit any data mapping, navigate to the left sidebar and click to return to the settings.Low
Review the Important Migration Notes, then proceed to payment.High
Once the payment is confirmed, you can start the Full Data Migration or schedule it for later.High

Bulk migration to Jira Software

If you are interested in a bulk migration, it's available as a custom option with an additional fee. For more information on how it works and the associated charges, reach out to our support team.

Step and detailsPriority
Sign up at app.relokia.comLow
Select your current project management system from the list and enter your access details. The information needed will vary depending on the project management platforms you choose.Low
Set up your Source connection and choose a project to export.Low

Create agents on Jira Software.

Go to Settings → select User management → click Invite users → enter the email address → choose a product role for Jira Software → Send invitation by clicking Invite users.

High

Configure email visibility for every team member profile in Jira Software.

Tap on your account icon → select Manage account → go to Profile and visibility → under Contact, select Anyone.

High

Set up a project for data import and adding users.

Go to Projects → click on Create project → choose Kanban → select Use templateselect a company-managed project → add project details and click Next.

High

Set up custom fields manually in Jira Software

  • if you want to migrate them to different spaces than they are on the Source,
  • if you have other options (e.g., for a dropdown field) or
  • if your field names in the Source differ from those you have in Jira Software.

Open Settings → go to Issues → click on Custom fields → choose Create custom fields → choose a field type → click Next → provide the name and description and click Create.

High

Generate an API Token for Jira Software.

Visit https://id.atlassian.com/manage/api-tokens → click Create API token → enter the Label → click Create and then сopy the token to the clipboard.

Remember to save the API Token since you won't be able to see it later.

High

Connect Jira Software as the Target

  • Connect Jira Software to Migration Wizard with the URL, email address, and API Token.
  • Select the Project, Issue type, and Sub-task type for importing data in this test migration.
Low
Specify what project records you’d like to import: users and issues, including comments, attachments, tags, and custom fields.Low
Match teammates. If there are unassigned, deleted, or inactive users, select a default user to map those records. When you're finished, click 'Save matching.'Mid
Map issue fields for default and custom ones. To map a custom field, select it and click “Add the same field in Jira Software' – the custom field will be added at the bottom. When you’re done, click “Save mapping.”Mid
Run a Demo Migration for one Source project. Review the reports, which display migrated, skipped, and failed records, each with a list of record IDs in the Source and new IDs in Jira Software. Click the button next to the report to view it.Mid
Share the list of projects you want to migrate. If you're importing all projects, just let us know.High
Provide the Relokia team the list of custom fields you want to migrate if they're not all available in a default migration. If you want to import all available custom fields, simply inform us.High
If you haven’t added all agents to Jira Software from the Source or if your agents’ emails on Source and Jira Software differ, you'll need to compile and send us a list. This list that describes what Source agent should be matched to the agent on Jira Software, including agent’s name and email at the Source and the corresponding name and email at Jira Software.High

Frequently Asked Questions

  1. How to find issues in Jira Software by IDs?

    Copy the Target task ID and go to Jira Software. Open Filters → View all issues → Switch to JQL → "ImportedId" = [issue ID].

    Or you can open up a migrated task via a link in Migration Wizard.

  2. Is there any difference in functionality of Demo and Full Data Migration?

    The Free Demo offers the same functionality as the Full Migration, ensuring your data is migrated equally in both. If you have any questions or notice inconsistencies during the Demo, contact us for assistance.

  3. Can I change data during the Full Data Migration?

    During Full Migration, avoid making any changes. Doing so will pause your data migration and make it take longer to transfer records.

  4. How much time will the Full Data Migration take?

    The time for Full Data Migration varies. It could range from 20 minutes to a few days. The duration of your Full Migration depends on:

    • Total number of records to import
    • API limits of the Source and Target platforms
    • API specifications
    • Your Target platform’s capabilities

Looking for more details on data migration?

Let's talk now
Was this article helpful?
Sign up