Upgrade/Migration of an Atlassian Suite.
Hi, me and my Team are working to plan and execute Upgrade/Migration of an Atlassian Suite in a Customer. Current environment is comprised of (Jira 6.X, Confluence 6.x, Stash 3.x, Bamboo 5.x). Objective of the project is migrate current architecture and upgrade all applications to latest versions, in order to scale current usage to a broader internal end user base.
At this point, our team is gathering all information from current Products suite (Atlassian and other tools like Static Code Analizers, Artifact Repositories Tools). And designing an strategy in order to execute the best platform migration posible.
As you can see, current application versions are very old. Reading Atlassian documentation, we can see that there are several step to pull out a succesfull migration/upgrade of individual Atlassian products.We also have seen that there are some migration paths that require extra migration steps between source version to destination. i.e: Jira 6.0 -> Jira 7.0 -> Jira 7.12.1
From doc research, typical upgrade/migration workflow can be defined as a set of steps like following:
- Info Gathering
- Planning,
- Cloning in a test environment
- Perform the upgrade in test.
- Verify.
Then, if everything went well with the testing, same procedure is executed in Production Instance.
Do you think that this is a correct approach for individual product migration/upgrade?.
If this approach is correct. What about the other products,meanwhile?. We have not seen so much information regarding migration escenario of complete Suites. Should those be also migrated and upgraded using the same approach in parallel? Or can this be done in a secuential way to minimize risk?.For example, Upgrade/Migrate Jira in a weekend, next weekend Confluence and so on?
Can you share your views and suggestions in order to define a good strategy in described scenario.
Thanks.
Best Regards
Rodrigo Valdés
