It’s done in a step-wise manner, but we have worked on projects merging 60+ instances as part of a single project. These have included various Atlassian tools, including Jira Software, Confluence, Jira Service Management, Bitbucket, hundreds of Add-ons, and 3rd party applications.
Leave licensing decisions and steps to us. We extended time to trial products and to build them at no cost before you use them. In addition, we can give you advice as you consider changes to user tiering when you bring separate but similarly functional teams together. One thing is for sure, you have fewer options if you go it alone with licensing, so reach out to Trundl.
Certainly! We have a whole team dedicated to hosting migrations. If it’s required, we will add it into the scope of the project and handle it as part of the larger effort.
That’s a big question we can’t answer without knowing more. Some 1-to-1 Jira merges with simple configuration mapping takes just a few weeks. Some Enterprise level merges (with 50+ instances) have year-long project plans. There are a lot of factors. Ask Trundl to look closer.
Unless you are using Enterprise Cloud licenses, we (along with your leadership) will need to get buy-in and dig deeper into push-back, offering technical solutions or workarounds to keep them happy. We have done this before, and offer our expertise at all points. Sometimes, it takes executive mandates, so be prepared for that as well.
