Haut de page

Consolidation vs Synchronization of multiple Jira applications


Posted by
Phil McCormick

February 25, 2020

On occasion, businesses merge or take over one another. When this happens, administrators and IT staff carry out a lot of work to secure data protection and a two-way flow of all information. Whatever the reason is behind the merger and the strategy, the most important issue is improving the work between two units. Both organizations usually have their project management operations that would be worth combining for optimal performance.

In this situation, we’ll discuss two possible solutions. One of them is joining the two applications into one (consolidation). The other one is synchronization, which allows us to connect and automatically transfer data between instances.

Consolidation of Jira applications

Merging can be an intricate task that requires the migration of data from one application to another. Yet, before this process occurs, the target Jira instance should be prepared for the import of this information: the transfer of the relevant configuration. Following the merge, users of joined entities can work in a common system.

The application utilized in the acquired enterprise is disabled for users, and will only be available to the administrator, they check whether all data has been accurately replicated. After this, the instance is archived and disabled.

The hurdles facing the administrator during this task are as follows:

  • access permissions
  • two different applications (different versions, configuration)
  • two different servers
  • reconstruction of projects (Jira), data loss, i.e., creation or modification date
  • two different ways of managing, naming (e.g., username)
  • transfer of data between servers (e.g., attachments

As we can see, organizations need to ensure that the entire merge operation is correct on many different levels.

Synchronization of Jira instances

If we have two instances of Jira, we can use the existing Elements Copy & Sync solution to synchronize both applications. Thanks to this tool, updates of applications, attachments, or workflows are made automatically. Also, thanks to the configuration, we can decide which data we want to share.

Comparison of Jira instance consolidation and synchronization

Consolidation Pros

  • Maintaining one application server instead of two
  • More organic process unification
  • One common portal, the application can positively influence the company’s culture resulting from the merger

Consolidation Cons

  • Complicated process of unification and merging of data and processes
  • No option for saving your own configurations
  • If not properly designed, it can have a negative impact on your instance
  • Partial information loss after transfer of data
  • Problems with the different Jira versions
  • Lack of perfect environment mapping

Synchronization Pros

  • A simpler and faster configuration
  • A good, temporary solution
  • Teams can start working together very quickly
  • No problems with apps
  • Small cost of implementing the solution

Synchronization Cons

  • The need for further administration
  • Two Jira instances may generate higher costs over time (upgrading)

Conclusion

Both solutions offer attractive advantages and not-so-attractive disadvantages so it’s best to analyze and weigh the best decision for your organization. The only aspect that is hard to compare is the cost. However, this is a non-determining criterion when you want to efficiently optimize your configuration.

Sometimes our clients decide to use both solutions, i.e. they use synchronization at the beginning to ensure the continuation of work, and in the meantime, they work on merging processes and tools.

Why choose Valiantys?

If you would like to learn more about the solutions we offer or talk to an expert, why not contact us and discuss your issue with one of our consultants. Our expertise will allow you to eliminate as much as possible all the weak points of the solution you will choose.