Hi @Damilola Adeyemi ,
Hope you are doing well.
I am Dhiren, one of the Solutions Engineers at Exalate.
Exalate was originally designed as a synchronization solution rather than a migration tool. However, it can still be used effectively for migrations, and we've seen many successful cases in the past.
What can be migrated with Exalate :
- Any Issues/Work Items (Standard/Custom) from any project.
- Information within the ticket (Standard/Custom) fields including comments, statuses, worklogs etc
- Sprints
Pre-Requisites for migration :
- The project structure on the Destination Jira including field configurations, workflows, users etc.
- As Exalate needs a structure to work with, you should have these created on the target (usually done by Jira Admins)
As Exalate is a completely decentralized solution, you would need to install Exalate on both sides for this to work.
The next step after this involves creating a connection, configuring the sync rules and then starting the migration using Bulk Exalate feature provided by the tool.
Once this is done, the next step would be to monitor the sync queue and verify the data integrity on the target side.
Please create a ticket with us using this link in case you want to know more.
Thanks, Dhiren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.