Recommendation of retaining unmigrated server data

Bharadwaj Jannu

Hi,

 

We first started using Jira and Confluence in 2012. When we migrated Jira and Confluence from Server to Cloud in March 2023, we only migrated three years' worth of data to complete the migration over the weekend. Now, we are exploring options to retain the 2012-2020 unmigrated data. Can anyone please help on our questions below:

1. Any recommendations on how we can retain the unmigrated data? 
2. One of the options under consideration is to migrate the remaining content to the Cloud:
- Do the migrators(CCMA, JCMA) still work?
- Do you have any recommendations on whether we should migrate the remaining content to a separate instance or to the production instance? Here are some pros and cons we have identified:

Same instance:
Pros: No additional cost for plugins.
Cons: Since the instance's size will increase, will operations take longer, e.g., searching, copying data from production to sandbox?

Separate instance:
Pros: Production instance remains unchanged.
Cons: Additional plugin costs and the need to maintain two separate instances.


Thank you!

Dick

Hi @Bharadwaj Jannu , welcome to the Atlassian Community!

ad 1: I recommend keeping your cloud instance as small as possible. Retain the 2012-2020 data in a separate datacenter Jira instance with minimized user count. If people want to search the old content, give them an account for the datacenter Jira. 

This way:

• You keep tabs on how many people use the old data (if it's worth keeping at all!)
• Keep cost at a minimum for the "old issues" on-prem solution
• Keep cost at a minimum for the current-issues cloud solution

 

I hope this helps,

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well