Blog

Efficiently Migrate Jira Configurations from Sandbox to Production with Revyz Configuration Manager

Written by Arwa Bombaywala | Jan 27, 2025 11:59:53 AM

If you're a Jira Administrator tasked with migrating configurations between sites, you're likely all too familiar with the challenges that come with this process. The complexities of configuration management can lead to time-consuming manual efforts and an increased risk of human error. Fortunately, the Revyz Configuration Manager significantly simplifies your migration experience. Designed specifically for Jira Cloud, Revyz Configuration Manager allows you to clone, migrate, and back up configurations effortlessly. 

In this blog, we will explore how Revyz Configuration Manager can enhance your Jira migration strategy, minimize risks, and ultimately boost team productivity. Whether you're transitioning from sandbox to production or managing ongoing configurations, Revyz provides the tools you need for a smooth and efficient process.

The Need for Revyz Configuration Manager

Revyz tackles the challenges of configuration management head-on with this innovative tool. It simplifies the management process while protecting against accidental or malicious data loss. By offering robust features for tracking, logging, and managing configurations in Jira Cloud, Revyz empowers administrators to focus on what truly matters—delivering value to their teams.

With Revyz, administrators can move beyond traditional methods that rely on manual recreation of configurations or risky export and import scripts. Instead, they can utilize a no-code solution that enables quick and secure migrations from sandbox to production. The platform not only enhances efficiency but also ensures that every change is meticulously recorded in an audit log, providing peace of mind during migrations.

Step-by-Step Guide to Migrating Configurations

 

1.  Getting Started

To get started with Revyz Configuration Manager, simply download the application from Atlassian Marketplace for both your sandbox and production environments. The user-friendly interface mirrors Atlassian's design, making it intuitive to navigate.

  1. Initial Setup: Install the Revyz Configuration Manager on both environments.
  2. Explore Features: Familiarize yourself with the application’s capabilities.
  3. Backup Configurations: Take an on-demand backup of configurations on both your sandbox and production sites, noting the timestamp for reference.

The Backup Jobs are now queued and will take a couple of seconds to back up on both sites.


2.  Setting Up the Cross-Site Connection

To efficiently migrate a project configuration from your sandbox environment to the production site, establishing a cross-site connection is essential. This connection enables seamless data transfer and ensures that configurations are accurately replicated without the hassle of manual adjustments.

  1. Access Settings Button: Start by navigating to your Sandbox site. On the left panel, click on the Settings option to access the configuration settings.
  2. Click on Cross-Site Connection: In the top navigation bar, find and select Cross-Site Connection. This feature is crucial for linking your sandbox and production environments, facilitating a smooth migration process.

 

Configure the Connection: Follow the prompts to set up the connection between your two Jira sites. You will need administrative access on both instances to configure this properly. Ensure that you authenticate in both directions to enable full functionality.

 

4 Activate Connection: Click on the Activate connection button from the Production site and paste the token generated on the Sandbox site. Once the connection is established, it’s important to verify that it’s active. You should be able to see linked projects and configurations between the two sites, allowing for easy navigation and management.

 

By establishing this cross-site connection, you create a robust framework for migrating project configurations with confidence. With Revyz Configuration Manager, this process is made simpler, allowing Jira Administrators to focus on delivering value rather than getting bogged down by technical complexities.

 

3. Clone Configurations

Cloning configurations from your sandbox environment to the production site is a straightforward process with the Revyz Configuration Manager. By following these steps, you can ensure that your project settings are accurately replicated, minimizing the risk of inconsistencies.

Follow these steps:

  1. Navigate to Clone and Restore: Begin by accessing your Sandbox site. On the left panel, click on Clone and Restore. This section is dedicated to managing all your cloning activities.
  2. Select Clone Configurations: Within the Clone and Restore interface, click on Clone Configurations from the available options displayed on the cards. This action will initiate the cloning process, allowing you to select the backup snapshot needed for migration.
  3. Choose Your Source Site: Your source site will be your current sandbox environment.      From the dropdown menu, select the latest backup snapshot you created earlier. This snapshot contains all the configurations you wish to migrate.

  4. Specify Destination Site: On this screen, carefully select your destination site—this will be your production environment. It’s crucial to ensure that you are targeting the correct site to avoid any unintended changes.
  5. Select Backup Snapshot for Destination: From the dropdown menu, choose the latest backup snapshot available for your destination site. This step is vital as it ensures you are working with the most current data from both environments.

  6. Compare Snapshots: Once both snapshots are selected, you'll have the opportunity to compare them side by side. This comparison is a critical step in the cloning process, providing a comprehensive view of the configurations being migrated. It allows you to identify any discrepancies or necessary adjustments before finalizing the migration.

 

4. Review Dependencies: 

Select the configurations you wish to migrate and then review their dependencies.

You can easily view the summary of what actions will be performed for the selected configurations 



5. Diff View:

The Diff View provides a visual representation of the configurations that are present, absent, or modified in both snapshots. This Revyz feature allows you to easily assess which configurations should be migrated and which ones should be excluded. With this clarity, you can make informed decisions about your migration process, ensuring that only the necessary configurations are moved to your production environment.

 

 

6. Migrate the Configurations:

Once you have selected the Configuration, Click on the clone, and voila!

Your job is now queued!

In a couple of seconds, you can view the Job ID to see the cloned configurations in the dashboard.

(Card view)

You have completed migrating your configurations. You can analyze the migrated settings in this card view. This feature provides a clear and organized overview of all configurations, allowing you to easily verify that everything has been transferred correctly and is functioning as intended.

Watch the Tutorial ▶️ here

 

Explore Revyz Data Manager for Jira.

Revyz Data Manager serves as the umbrella application that combines the functionalities of both the Configuration Manager and Asset Manager, offering a comprehensive solution for Jira administrators. This powerful tool protects your data with encryption in transit and at rest while streamlining the management of configurations and assets.

Key features include automated backups, granular restore options, and detailed analytics, empowering users to efficiently maintain data integrity and security. With additional capabilities like malware scanning and site analytics, Revyz is not just a backup solution but an essential toolbox for Jira administrators.

As organizations increasingly rely on Jira for project management, Revyz proves vital for ensuring operational efficiency and compliance, all through a no-code approach that simplifies automation and restoration processes.