Summary
Challenge: Split a single Atlassian instance into two Cloud environments during a company restructure, with complex JSM configurations, 70+ automation rules, and tight timelines.
Solution: We conducted trial migrations to identify issues, reconfigured JSM request types and automation rules (including consolidating 70+ rules into one), documented all changes, and provided proactive stakeholder support.
Outcome: Completed migration 10 days early with zero workflow disruption, streamlined automation, full security controls, and rapid adoption of new Cloud environments.
Background
Discover how we delivered an Atlassian Cloud-to-Cloud migration in record time – delivering secure, streamlined and stable new environments, during a period of great organisational change for a travel giant.
Established in the late 1800s, our client is the world’s longest-running cruise expedition company, chartering journeys to over 250 destinations.
Challenge
Here at Automation Consultants, we were recommended to our client as Atlassian and Cloud migration experts. When we met, the company was in the midst of a restructure – essentially splitting into two brands at the organisational level.
As part of this, the organisation needed to split its Atlassian instance into two distinct sites. It used Jira, JSM and Confluence as business-critical tools. Our role was to migrate anything related to the new brand to the new Cloud site, whilst leaving other data on the original site.
The challenge was delivering this migration in a short time-frame, whilst aligning with the company’s wider restructuring activities. Due to the brand split, there were notable complexities around mapping, duplicating and reworking configuration from the original site to the new Cloud site.
Solution
Due to the potential complexity of the split between the two brands, our team here at AC first conducted an investigation, to truly understand what needed to be migrated to the new Cloud site, and how this would be achieved.
We then conducted a trial migration, to ensure the production migration could proceed smoothly. During this time, we spent time addressing challenges around accurate user-mappings, duplicate accounts, and configuration that needed decoupling or reworking.
We also had to identify a solution for JSM request type layouts, which weren’t compatible with the Atlassian ‘Data Copy’ tool. This challenge occurred during the trial migration – demonstrating the value of our rigorous testing stage before a production migration.
A number of our client’s JSM projects had a significant volume of request type layouts (20+), and each also had 30+ fields. To address this, we carefully documented how we would solve each of them, and ran rapid fixes ahead of the production migration.
We also had to ensure that existing automation rules would still run effectively on the new Cloud site, post-migration. With some projects comprising over 70 automation rules, this was a significant task. We refactored those 70+ automations into one single, powerful automation rule that provided the same functionality, and enabled users to continue working without disruption to BAU activities.
With complex client requirements, we took a highly flexible and bespoke approach to this Cloud-to-Cloud migration. From working outside expected working hours on production weekend to ensure a smooth end-result, to providing out-of-scope Early Life Support, we demonstrated great responsiveness, proactivity and creativity to deliver the project to a successful outcome.
Results
Despite the unexpected complexities of this Atlassian Cloud-to-Cloud migration, we delivered the new Jira, JSM and Confluence Cloud sites a full 10 days ahead of schedule, exceeding client expectations during what was already a short time-frame.
Due to our robust configuration work, we were also able to ensure that our client’s teams were able to hit the ground running post-migration, with minimal disruption to their BAU activities. With replicated JSM request types, streamlined automation rules, and sophisticated user-mapping, users within the newly created brand were able to jump right in to their new Cloud site and continue their work.
Going into this new organisational era, both brands can now wholly benefit from Atlassian Cloud features – from centralised support, to alleviated pressure over security and user provisioning.
Ultimately, during a period of transition for the wider business, our work here at Automation Consultants resulted in a stable, migrated Cloud environment that provided those working across the both brands autonomy and reliable management of their new sites.
