Scroll to top
en pl

Consolidation vs. synchronization of multiple Jira applications – learn what is better


Łukasz Krupa - 6 September 2019 - 0 comments

Sometimes companies merge or take over one another. In such situations, administrators and IT staff carry out a lot of work to ensure data protection and two-way flow of all information.

Regardless of the reason behind the merger and the adopted strategy, the most critical issue is improving the work between two units. Both organizations often have their project management systems that would be worth combining for optimal performance.

In this situation, we can consider two solutions. One of them is joining these two applications into one. The other one is synchronization, which allows connecting and automatically transferring data between instances.

Consolidation of Jira applications

Joining is a rather complicated task, which involves the migration of data from one application to another. However, before this process occurs, the target Jira instance should be prepared for the import of this information, i.e., the transfer the appropriate configuration. After the merge, users of joined entities can work in a common system.

The application used in the acquired enterprise is disabled for users, and the view is only available to the administrator, who checks whether all data has been properly copied. At a later stage, the instance is archived and disabled.

The challenges facing the administrator in this task are as follows:

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

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

Synchronization of Jira instances

If we have two instances of Jira, we can use the existing IssueSYNC solution to synchronize both applications. Thanks to this mechanism, updates of applications, attachments, or workflows are made automatically. Also, thanks to the configuration, we can decide which information we want to share.

Comparison of Jira instance consolidation and synchronization

Both solutions seem attractive, but it is worth considering the advantages and disadvantages of either to make the best decision for your organization.

The only aspect that is difficult to compare is the cost. The consolidation of two Jira applications is only seemingly cheaper. The value of administrator’s work and data transfer is huge. By using an out-of-the-box solution, the process can be carried out faster and the result is easier to predict. Sometimes our clients decide to use both solutions, i.e. they use synchronization at the initial stage to ensure the continuity of work, and in the meantime they work on combining processes and tools.

Would you like to learn more? Get in touch with us. We also encourage you to take advantage of IssueSYNC in a free 30-day trial period, available on the Atlassian Marketplace.

Related posts