Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is there a way to get the migration assistants to use fewer resources and keep to the background?

Rob Horan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 19, 2022

JCMA and CCMA can be a bit of a resource hog.  Is there any way to run these in more of a background mode so that users are not seriously impacted while a test migration is in progress?  This is a major issue when there are many GB of attachments.

2 answers

1 vote
James Richards
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 19, 2022


Another solution is to set up a test instance locally that's a replication of your production server. You can get a developer licence for a local testing server to use. You can review this documentation on how to get one


There is no publicly available documentation indicating it can be.

What we generally do is enable the attachment-only migration (which I believe is no longer a hidden feature flag) and do them off-hours, even for the test migration.

For prod, we generally migrate attachments the week prior to migration. When the prod migration goes over the weekend, this allows it to go much quicker as it only has to upload a diff of attachments and then re-link them to their issues.

IT may be able to setup some QoS rules based on the domain the Jira Server instance is communicating with. For example, you could lower the priority of the JCMA traffic. URLs and IPs can be found easily with a "atlassian JCMA ip whitelist" search.

Also, they recommend 6-8 GB of RAM for a small/medium instance and 10-12GB for a larger instance. This won't affect network resources, but you really didn't define "resource hog" so I don't have much to go off.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events