You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
This is the first of seven articles bringing you through the most important and beneficial experiences we gained in out migration project that concluded May 2020. This first article will focus on what we had and why we decided to migrate our self-managed Jira instance to Jira cloud.
Digizuite is a major player in the global DAM market, providing powerful digital asset management solutions to businesses and organizations around the world.
Our software, Digizuite™, makes it easy to collaborate across departments, countries, and digital channels. Users can simply upload, edit, search, manage, distribute, and repurpose rich media content, such as images, videos, documents, and PDF files, across internal and external channels from one centralized source through automated and intelligent workflows.
Based on the above benefits we accepted a slightly increased cost for users and the budgeted migration cost for both internal and external resources.
* Tempo Timesheets will not migrate (or very expensive service) it has to do with accounts being lost and must be reconfigured.
* Satisfaction data from JSD is lost.
* SLA information from JSD is somewhat restorable but will be changed due to changing SLA’s
In the next article we will provide the Do’s and don’ts in the migration test process. At the end of the article series we will conclude on if we achieved the benefits listed above.
As a part of the project limitations we need to calculate an estimated budget and get it approved by the project sponsor.
Between the authors in this article series we have more than 40 years in IT and with more than 21 years together working with Atlassian Jira products in several organization.
Introducing Jakob F. Gormsen has been working as an Atlassian Expert the last 16 years specializing in helping organizations get the most out of the Atlassian products, with a special knowledge about Jira Server. You can reach out to Jakob at https://condoctor.dk/.
Henrik has mainly been a Manager and user of Jira to run Development and support. Henrik in this context is the Project Manager of the Migration project and responsible for Support and Quality in Digizuite. The reason we are writing this article series is to pass on our experiences from the process and want to help the Atlassian community get a more successful cloud migration. We have received support from the Atlassian Migrations and communications team to provide you with their initiatives to prevent the issues we experienced in the future.
1 accepted answer