Case Study – Migrating from Monday to Jira

Monday to Jira 3

While working with our customers, we often get the request to assist to migrate existing projects from to Jira’s projects. The customers do not want to integrate the two because they will not be using Monday once everything has been moved. We see more and more customers taking this path, as many of them are looking into systems consolidations, and reducing the total number of systems used in their network.

Even though it sounds like a simple request, it has several layers of work and design that are required to fulfill the customer’s request.


Look and Fill

One of the main obstacles in such process is usually not a technical briar, it is actually a look and feel issue perceived by the users. They are used to group based operations, and several statuses display, and this is not the Jira out of the box look and feel. Showing them the Kanban board and issue filter display are not getting them their known and familiar environment, and often creates some tension with adopting the new system.

We recommend on working with a Jira APP called QuickView, which gives Jira a grouping display which has some similarity to the work concept.

With groups, drag and drop, and on display edit capabilities, most of the user find it easier to make the move to Jira. Look at the following screenshot and see how the Jira data can be viewed in groups rather than a kanban board. This look and feel is more than a sematic change, it allows users too work on meangfull groups rather the on statuses. Thi sfeature is very common in many other work managment tools but is missing in the plain vanilla Jira. Now with this APP you can get these capabilities inside Jira.

You can add this APP to your Jira from the Atlassian Marketplace here


Data Mapping

Moving data from to Jira needs to have a more global thinking as the issues hierarchies’ capabilities in Jira and their capabilities are different from

We suggest customers to think about the data hierarchy they want (or already have) in Jira and see how they are mapped to their existing data.

Another aspect is field mapping. Jira uses system fields for many elements (such as Assignee, Priority, etc..) and it is crucial to map the fields to those fields. Another thing would be using global fields which are already used in other projects in Jira and try to reuse them rather to create new fields or existing data sets (e.g., drop down values of existing fields may require to adjust the exported data before insertion)

Data Migration

Our recommendation on the process of migrating your data from Monday to Jira would be by CSV (Excel) export/import.

Following are the needed steps:

  1. Export your items from to a CSV, following the guide below:
    1. From the “More actions” sub menu click “Export board to Excel”. choose whether you want to export just the table or to include all updates and update replies.
  2. Import the file to your Jira application, properly edit it in the way you need (See the Mapping Section):
    1. Prepare the Kira Project you want to upload your data
    2. Import the data from CSV to the Jira


Our Process

PractiProject Experts, start with understanding both the Jira and usage by the customer, go through the different scenarios, data colorations and expected structure. As a result of this process, we prepare a design document to describe the work and the outcome.

We continue with a dry run to imitate the actual migration and allow the customer to review the outcome and test it.

After all is approved, we set up the migration date, and perform the actual migration, and support the users to on-board the system with training and support with their first days work.

For more information, please contact [email protected]