What efforts are needed to move data from Jira Align back to Jira Jira v8.5.3?

[Humair Imam]

Our company is running Jira and JA.  We migrated some of the teams to Jira Align to integrate with a SAFe implementation.  Our product team is looking to move away from Jira Align to a products such as Aha or ProductBoard.  In addition, leadership is considering to decommission Jira Align and move the JA teams back to Jira.

Kindly, shed some light on this matter regarding the possible impact on revenue, data and custom fields migrations, development efforts needed to accommodate the JA fields back into Jira, and everything else that are the possibilities leading to failure and long term risks. 

What are my possible options for a backwards migration from JA to Jira to guide the organization back to the original starting point?     

Specifications:

Copyright © 2002 - 2020 Atlassian Corporation Pty Ltd.

The use of this product is subject to the terms of the Atlassian End User Agreement, unless other specified therein.

This product includes software developed by the Apache Software Foundation.

This product also includes the following libraries which are covered by the GNU LGPL license:

• atlassian-image-consumer (com.atlassian.image:atlassian-image-consumer:1.0.1:jar)
• carol (carol:carol:1.5.2:jar)
• carol-properties (carol:carol-properties:1.5.2:jar)
• datafile (datafile:datafile:1.3.3:jar)
• image4j (org.jclarion:image4j:0.7:jar)
• jcaptcha (com.octo.captcha:jcaptcha:2.0-alpha-1:jar)
• jcaptcha-api (com.octo.captcha:jcaptcha-api:2.0-alpha-1:jar)
• jcommon (jfree:jcommon:1.0.8:jar)
• jfreechart (jfree:jfreechart:1.0.13:jar)
• JSCalendar (1.0)
• jStyleParser (net.sf.cssbox:jstyleparser:1.16-atlassian-1:jar)
• TinyMCE-TinyMCE (4.4.0)
• xapool (xapool:xapool:1.3.1:jar)

This product also includes code written by other third parties.

Additional details regarding these and other third party code included in this product, including applicable copyright, legal and licensing notices, are available in the "licenses" directory under the Jira installation directory.

License Information for Jira Plugins

JIRA Service Desk Application v4.5.3

Copyright © 2002 - 2016 Atlassian Corporation Pty Ltd.

The use of this plugin is subject to the terms of the Atlassian End User Agreement, unless other specified therein.

This plugin includes software developed by the Apache Software Foundation.

This plugin includes the following libraries covered by the GNU LGPL license:

• atlassian-image-consumer(com.atlassian.image:atlassian-image-consumer:1.0.1:jar)
• dbUnit Extension(org.dbunit:dbunit:2.5.2:jar)
• jStyleParser(3.0)
• jcommon(jfree:jcommon:1.0.8:jar)
• jfreechart(jfree:jfreechart:1.0.13:jar)

This plugin also includes code written by other third parties.

Additional details regarding these and other third party code included in this plugin, including applicable copyright, legal and licensing notices, are available in the "licenses" directory inside the plugin.

Advanced Roadmaps for Jira v3.29.2

Copyright © 2014 Atlassian Corporation Pty Ltd.

The use of this product is subject to the terms of the Atlassian End User Agreement, unless other specified therein.

This plugin includes software developed by the Apache Software Foundation.

This plugin includes the following libraries covered by the GNU LGPL license:

• GNU Trove(net.sf.trove4j:trove4j:3.0.3)
• JGraphT - Core(org.jgrapht:jgrapht-core:0.9.2)
• jStyleParser(net.sf.cssbox:jstyleparser:1.16-atlassian-1)

This plugin also includes code written by other third parties.

Additional details regarding these and other third party code included in this plugin, including applicable copyright, legal and licensing notices, are available in the "licenses" directory inside the plugin.

JIRA Agile v8.5.3

Copyright © 2002 - 2013 Atlassian Corporation Pty Ltd.

The use of this plugin is subject to the terms of the Atlassian End User Agreement, unless other specified therein.

This plugin includes software developed by the Apache Software Foundation.

This plugin also includes code written by other third parties.

Additional details regarding these and other third party code included in this plugin, including applicable copyright, legal and licensing notices, are available in the "licenses" directory inside the plugin.

Thank you.  Appreciate all your help and leadership.  Looking forward to a cordially reply.

[Rich Sparks]

There's not a simple answer to how you can move your data from Jira Align back to Jira; it really depends on which features of Jira Align your teams are already using. For example, if you're using Dependency Management in Jira Align, there isn't a corresponding capability in Jira or Aha for that, so you'll need to create a custom solution. Also, Jira Align work objects have many useful attributes which aren't in the standard Jira issue types, and if you've taken advantage of those in Jira Align, you'll need to create custom fields on the corresponding issue types in Jira Align.

One place to start is to look at the Jira Integration Guide in Jira Align to see which standard fields Jira Align synchronizes with Jira. If you are using only those fields, moving the data to Jira is straightforward.

You can find the guide here: https://help.jiraalign.com/hc/en-us/articles/115000088854-10X-Jira-Integration-Guide

But if you are using lots of specific attributes in Jira Align and you want to continue to use them in Jira, that will require more work in Jira. As an example, here is a list of many of the attributes found on the Feature work object in Jira Align (synchronizes with the Epic in Jira.) https://help.jiraalign.com/hc/en-us/articles/115005899568-10X-Manage-Features

And as @Gonchik Tsymzhitov  suggests, you can get the data out of Jira Align via the Export function. Or you can explore using the API's in Jira Align to get the data if that solution works better for you.

[Humair Imam]

@Rich Sparks thank you very much for the valuable advice.  This is most helpful in chartering a few analytical discussions to substantiate a full impact of the backwards migration and the disruptions this will cause in operations, development, and revenue.

I appreciate your and @Gonchik Tsymzhitov's expert advice on this subject.  I will keep everyone posted on our findings.  Once again, thank you very much for your time, guidance, and leadership.  

[Gonchik Tsymzhitov]

Hi @Humair Imam , 

That's really interesting to read about JA -> Aha. 

Because we will do the opposite action to Aha -> JA. 

Regarding effort, it's quite non-one step activity. 

1. Did you reviewed your JA? interesting the scheme etc.

2. Do you know how does your exist integration work ? I mean in data level https://help.jiraalign.com/hc/en-us/articles/115000088393-10X-Jira-Data-Synchronization

I am asking as it's long term step

Shortly you need export data and import. 

1. Export like as example https://help.jiraalign.com/hc/en-us/articles/115005998387-10X-Export-Objects-to-Excel

2, Do transfer data and clean

3. import data https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html

But 1,2,3 will many times and please, start everything from test env to be sure all thing is ready for doing on prod.

Cheers,

Gonchik Tsymzhitov

[Humair Imam]

Thank you very much for the kind words and valuable advise.  I will discuss this with my team members and see if this gives us a starting point towards a long and a short term solution.

Once again, thank you for all your time, patience, and guidance.