Query regarding cloud migration on an existing instance post clean-up

abhishek_sharma03
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.
December 25, 2023

Hello Everyone,

 

Wishing you Merry Christmas & Happy New Year ! 

 

Seeking your inputs regarding the ongoing Cloud migration project. In light of some ongoing challenges, we are considering the same instance which is currently being used for UAT and test migration for upcoming production migration as well. We plan to reset and clean it up after UAT signoff. Would like to understand on whether proceeding with this option is advisable or not and would like to be aware if there are any potential challenges or risks associated with using the same instance for both test and prod migration. Have heard in few forums that performing prod migration in the UAT instance post clean-up can cause unforeseen issues due to some pre-existing DB references.

 

Any insights would be really helpful.

 

BR

Abhishek

2 answers

1 vote
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 25, 2024

@abhishek_sharma03 I would suggest cleaning up prior to UAT, then move and do any additional clean up if necessary in PROD.

0 votes
Jehan Bhathena
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 4, 2024

Hi @abhishek_sharma03 

Based on your use case it would depend what would be your approach to the clean up, if you plan a complete Reinstallation or would you just clean out the test entries and then perform the migration?

There are a few benefits When migrating from the UAT instance, eg. If you need to change all the users email domains, this change would break a lot on PROD but on the UAT site you could run a basic sql and make the change and then migrate the site to your cloud env. Also if you encounter an error when migrating to cloud, the fix application has to be throughly thought out for PROd since changing anything there means updating a live entry.

While expensive the best option would be to consult with an Atlassian Professional service provider, since they have a lot of insight into such scenarios.

Hope this helps.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events