I have 2 different JIRA cloud instances and I want to migrate project from one instance to another.
My requirement is that I ahve 1000 users but i wantt o migrate only 800 users
I am using MIgration Cloud site, but there is not option to select certain user, all user are migrated and if we use a group then group is migrated but not user.
do we have any atlassian app to migrate some user.
How we can do such migration
Hi @ranjanajindal ,
for my knowledge, all users will be migrated because potentially all of them could be involved in some tickets (assignee, reporter, history and so on). My suggestion is to migrate all users and then clean users by deactivating them (deleteion is not the right way).
Hope this helps,
Fabio
Thanks Fabio. Yes for one customer we have followed this approach, but now this customer has some restriction for migrating all users, so looking fr laternate solution
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@ranjanajindal , hi! Indeed, some 3rd party tools can help you with the migration - allowing you to specify which users to be migrated. Check out the ZigiOps platform. ZigiOps is a no-code connector, but it works perfectly for migrations and can be customized to fit your use case.
Regards, Diana (ZigiOps team)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@ranjanajindal in that case, do not hesitate to give ZigiOps a try. Feel free to drop me a line if you'd like to know more about how it works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As mentioned in the previous answer, migrating only a subset of users is not recommended, as users have change history against them. But if you are looking to migrate only some selected projects or issues, then you can consider third party migration tools.
In addition to migrating the selected data, third party tools will be useful for following scenarios as well:
1) Downtime: Downtime adds operational costs and impacts development operations as teams may not be able to use Jira during the ongoing migration. If you want to avoid migration downtime, then you can look for a third-party tool that can remove any downtime requirement while the migration is going on.
2) Field Template Inconsistency: If there is any field scheme configuration difference between your cloud instances or you want to split or merge projects while the migration is going on.
OpsHub with its extensive experience in undertaking complex migration projects, ensuring ZERO downtime, no data loss, complete date integrity and full ownership of the migration process can be a good choice for the given job. It supports the migration of all System & Custom Issue Types, Sub-Task Types, Version and Worklog, etc. from Jira cloud to Jira Cloud. Feel free to contact our migration experts for the initial migration planning.
Thanks,
Brad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.