Exalate is not a migration solution.
Check corresponding document
Using Exalate for migration purposes
We are using "Configuration Manager for Jira" for migration from Server to AWS Cloud datacenter. The requirement is only 200 projects want to migrate to AWS. Once the migration for 200 projects gets completed, we will use the "Exalate" to synch the issues which are missed while doing the migration. Because users will use the source Jira while the migration work.
Is exalate feasible to use in this usecase?
Yes it is.
You will have to create a bulk connect file containing the mapping between the local and remote key.
Once that this is done, issues keep in sync according to the configured sync rules.
Thanks Francis,
How many projects can we configure at one time for live data synch using exalate plugin. We are planning to synch data from on-premise to AWS cloud datacentre JIRA.
~Tushar
All of them - and it can be done with a single connection.
Of course - the devil is in the detail - and proper testing is required.
If you would like to have expert advice - please check out our partner directory
https://exalate.com/partners
I'm sure you can find a partner near you, who can assist.
We are using "Configuration Manager for Jira" for migration from Server to AWS Cloud datacenter. The requirement is only 200 projects want to migrate to AWS. Once the migration for 200 projects gets completed, we will use the "Exalate" to synch the issues which are missed while doing the migration. Because users will use the source Jira while the migration work.
Is exalate feasible to use in this usecase?
We want to migrate 200 out of 600 Jira projects from On-Premises to AWS Jira center. The Source Jira is of V 7.10.XX and Destination JIRA is V 8.14.X. SO can we install the exalate plugin on both the JIRA tools and do synch ups? Below is JIRA migration plan:
What objects did exalate plugin will cover?
What are limitations using the exalate plugin.