It starts with a short call and a standard checklist. Some basics will be covered first such as what your migration goals are, what core applications are involved, current versions, desired completion date, etc. We will also have you (or your Jira Administrator) provide specific information about the source instance. This includes things like the number of projects and issues, attachment size, add-ons, etc. From this information, we are able to provide a low and high estimate.
This does not happen often these days, but we are prepared for it. Add-ons can present a lot of different variables. Sometimes we find replacement add-ons to move or convert data (i.e. Power Scripts for Scriptrunner), sometimes we have to manually recreate data, and other times we have to recommend an alternative add-on. In any case, we will give you all your options and provide a recommendation on a case-by-case basis.
Yes. We will help get you to the latest migration-friendly version and will include it in our overall scope if necessary.
You are an important part of the migration. We expect there to be a known executive sponsor and project lead so communications or escalations keep the right people informed. The most important engagement is in verifying test migrations and actively participating in UAT. Trundl will be there at every step.
Yes. We procure Atlassian licenses for over 150 customers and know ways to extend trial licenses as well as provide other benefits during the transition. Trundl can also provide quotes if you are still considering hosting choices.