Breadcrumbs

Migration to the Cloud

This page describes how to migrate Requirement Yogi Data Center to Confluence and Jira Cloud, using the official CCMA (Confluence Cloud Migration Assistant) and JCMA (Jira Cloud Migration Assistant).

This document is mostly a checklist to ensure the task will be successful.

Follow each steps

What will be migrated?

Due to technical difficulties with the APIs, we have only just published the Phase 1 and 2 of CCMA. It will allow you to migrate requirements, and Jira links.

  • Requirements

    • As they are defined on Confluence pages, they will always be migrated, as well as their properties and dependencies.

check mark Ready

  • Requirement-property macros

check mark Ready.

Note that the feature is different. RY Properties macro are replaced by a Configuration macro: RY Configuration instead. For each RY Property in a column header, only one configuration macro is used at the top of the page. Find more information on differences here: https://confluence.intranet.requirementyogi.com/wiki/x/LwAHpw.

  • Requirements links to Jira issues + relationship

check mark Ready

  • Baselines

check mark Ready with manual export/import.

Not within the CCMA but it is possible to manually export Baselines from Server and import them back to the Cloud (since 4.2.14)

  • Traceability Matrices

cross mark

  • Other RY macros on pages

  • Requirement Types

  • Excel Imports

cross mark

Overview of the migration process

  1. Perform the prerequisite steps,

  2. Migrate the Confluence data,

  3. Check and acknowledge the warnings and errors in Requirement Yogi for Confluence Cloud,

  4. Migrate the Jira data,

  5. Check and acknowledge the warnings and errors in Requirement Yogi for Jira Cloud,

  6. The migration is done.


1. Required steps before migrating

RY for Confluence

RY for Jira

1

On the Server/DC side, upgrade the CCMA plugin to the latest version;

On the Server/DC side, upgrade the JCMA plugin to the latest version;

2

Upgrade Requirement Yogi for Confluence Server to the latest version (minimum 4.4.10)

Upgrade Requirement Yogi for Jira Server to the latest version (minimum 4.4.12)

3

Install Requirement Yogi on Confluence Cloud.

Install Requirement Yogi on Jira Cloud.

4

Once the installation is complete, make sure you link your RY for Confluence and RY for Jira instances together, see docs.

5

Make sure permissions are set up so we can view and create pages in your spaces:

  • More information in the FAQ.


6

Make sure pages with requirements on your Server / Data Center instance are not restricted.

  • If there are page-level restrictions, then the app will not be able to view/edit pages with requirements.

  • See possible solutions in the FAQ.


7


If you are using multiple relationships for requirement-issue links in Server / Data Center, make sure you create the same relationships in the RY for Jira Cloud administration as well.

2. Starting the migration

If you have both Jira and Confluence, we recommend doing the Confluence migration first. If you choose to migrate Jira first, we will still create links to requirements that were not yet migrated, but you won’t see them on your Jira issues until you have migrated your Confluence requirements.

Go to the Migration Assistant

In your Confluence Server / Data Center instance, go to the General Configuration > Migration Assistant.

  • In the section ‘Assess your apps’, mark Requirement Yogi as “Needed in cloud”

    Screenshot 2023-03-24 at 14.07.57.png

  • Proceed to the rest of the migration steps required by Atlassian.

  • Keep track of the progress of the migration and wait for it to be complete.

    Screenshot 2023-03-24 at 14.11.21.png

💡 App migration can take a long time to run, especially if you have thousands of pages. On our test instance, the migration took 20s per 1000 requirements (1h30 for a sample of 220k requirements spread on 2000 pages).

2. Monitoring the migration

It is possible that the percentage of progress remains to 0% for a long time, that’s because the percentage is calculated based on the total of DC pages processed, so you’ll have to wait for all DC pages to be processed before seeing progress.

You can monitor errors and success by downloading the csv with logs.

3. Ending the migration

  • When the migration is set as success you can go into your Confluence site and visit pages with requirements to make sure they are transformed.

  • If you want to make sure no DC macro ‘requirement’ exist anymore, you can use cql and look for macro=requirement. (See: FAQ & Troubleshooting | How can I find non migrated content? )

If the migration is in ‘Failed’, please do feel free to open a ticket to notify us of errors generated by the migration tool by raising a support ticket.

Limitations

  • On the Cloud, pages containing requirements must be migrated to the new editor experience, since we only have transformers for the new JSON/ADF storage backend, and not for the XML one. The migration will be triggered when we apply the transformation.

Frequently Asked Questions