You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Jira Service Management system (JSM) is a go-to service desk for businesses planning ITSM migration. The reason?
Affordable and feature-rich pricing plans, integration-friendly architecture, and high compatibility with third-party tools. But before reaping these benefits, the organization should migrate its data, and it often becomes the toughest part of the journey.
Which way should you choose for data migration to Jira Service Management? It depends on many factors. This article will review the key points you need to keep in mind.
Help desk migration means moving the IT help desk from one location to another. It includes file formatting, change of storage type (on-premise to cloud and vice versa), data structuring, switching to new data architecture, etc. And the process isn’t as simple as it might sound.
There are a few concerns associated with data migration, such as:
They are the reason why only 16% of companies report successful data migration. Luckily, you can overcome these risks and benefit from relocation. You should plan the process wisely and use the right approach. Now let’s look at three common ways of data migration to Jira Service Management.
The choice of migration method and tools depends on the type, quality, and amount of the data you have, data management strategy, data governance requirements, and other business-specific objectives. Let’s explore in detail how you can transfer data to Jira SM.
You can transfer data to Jira using its data importer tool for CSV (comma-separated value) files. It’s the format most databases and spreadsheets use, so it might also work for your data. If your data is in other formats, you must convert it into CSV first.
Some companies do hire data engineer teams to complete the job, which comes with its own challenges.
Hiring developers is a perfect choice for large companies that have different types of data with complex relationships that need to be transferred. In this case, the data gets sorted, formatted, and structured by data engineers who write code or use ready-made software to do the transfer.
None of these options suits your case? Here’s an alternative to consider.
Automated migration services transfer data not only from CSV files but also from shared inboxes, help desk platforms, and other systems. It significantly streamlines the process.
Help Desk Migration is one of such tools. Its guided Migration Wizard helps even non-technical users complete the migration successfully. Plus, it’s compatible with over 300 help desk providers.
Whichever record import option you use, one thing is true: you must prepare your data and thoroughly plan every step of your migration.
No matter which option you go with, the basic migration steps would be to prepare, migrate, and maintain your data. Each step must be modified for your particular case as data, legal requirements, and possibilities vary.
Here’s what the migration process looks like with the Help Desk Migration tool.
Before you start any migration process or CSV import, you need to inform all your teams and users about the scheduled changes to avoid bottlenecks, downtime, unavailability, and support ticket uptick. You should also back up every ticket and issue you want to transfer to safeguard the data.
After you finish the backup, set up the Jira account for full data migration. It includes mapping out, creating custom fields, adding all users and emails, managing specificities and limitations, etc.
After preparing the account and location, you can start a demo migration or initiate the full migration right away. You may use automated options and bulk migration to the assigned fields to speed up the process. Depending on the data volume, it may take from a few hours to a few days, so make sure you have a stable connection and power supply.
After completing the data import, go into your Jira account and check the migration report in Migration Wizard. It will show the migration status and the files that need to be migrated manually. You can use the search bar to locate a particular file or contact the support team to find it.
Don't forget to update your new platforms after the check, connect the communication channels with a new Jira help desk, and re-forward the emails. Run a few test tickets within a team to check if all works — and you’re all set!
Data migration to Jira Service Management may be stressful — but it shouldn’t. With Jira-native, third-party, or custom-guided data transfer options, you can choose the option that works best for you! And if you need any help with the process, we’re here to assist you!