...
Situation | Is it supported? |
|---|
Confluence* DC** instance → New Confluence DC instance Export and reimport a whole instance, with all the data. * Same with Jira ** Server and Data Center are both supported. |  Yes, it is supported.
We recommend to use the same RY version on both sides (and we support a small range of versions). Please perform the Confluence-level import first, so pages, spaces, etc. already exist in the destination, Please create the application links, and set them up in the RY administration, before starting the RY import, Requirement Yogi settings will be imported. Page IDs, user keys, etc. must be remapped manually. This will be a long and mundane operation on your side. During the mappings, you can even change the space keys.
Note that Confluence and Jira are imported separately, therefore: |
Confluence DC → Same Confluence DC, but later in time. | Yes, but there is no reason to do that. |
Confluence DC space → another Confluence DC instance. Ideal for merger-acquisitions, Ideal for centralization into a large Confluence/Jira DC cluster. | Yes, it is supported. Same specificities as above, The global entities (the settings) will not be imported, If there are pages outside the space pointing to these requirements, they will keep pointing to the old place.
|
Confluence space → New Confluence space with different key. Rename a space | Yes, it is supported. Please have the new space with the page IDs ready, before starting the RY import, Requirements can even exist in both spaces after import, but Jira links will only point to one of them. Jira links won't be updated, and this will be a problem. Please export-then-reimport the Jira data as well, mapping the space key with the new one.
|
Backups |  No, this is not supported.
We require the same version on both sides, and it may take some back-and-forth between the two sides, Confluence data is not part of the RY backup, so you would have to perform a Confluence backup anyway, It is not a sane way to perform backups (backup size, process, etc.).
|
Migrate from DC to the Cloud | No, this is not supported yet. However, that's the idea for the future. Yes, you can migrate macros and Jira links, but we do not support other RY data (baselines etc.). Find more information here: Migration to the Cloud |
Migrate from the Cloud to DC | No, this is not supported yet. Same, we're hoping to do it. |
...
Step 1 - Export the entities to a temporary table
Confluence | Jira |
|---|
 Image Removed Image Added |  |
Requirement Yogi lets you choose: The scope: It is possible to restrict the export to a single Confluence space. Restricting by Jira projects is not supported (The screenshot below doesn't contain the field 'Project key' anymore). The backup key: In order to avoid collisions when 2 administrators are working on imports/exports, you can specify your own key. It doesn't matter what the key is, please keep it simple.
|  |
This step only copies all data into a single table, in preparation for the export. The table is as big as the entire database, therefore it will be important, later on, to empty this table. None of those long-running task should be interrupted by, for example, a Confluence restart. If it happens, please restart the step. Of course you can leave the page. If you lose the link, you can find the progress of the task in the "Queue" tab. |  Image Removed Image Added |
At the end, we suggest to write the file to disk. If you have lost the link to this progress screen, you can perform this operation using the main menu: |  Image Removed Image Added |
Step 2 - Write to disk
...
Here are the possible statuses (matching the database column AO_32F7CE_DBBACKUPMAPPING.STATUS): (null): Not mapped yet, UNMAPPED: Couldn't find a match, MAPPED_AUTO: Displayed as "MAPPED" + an exclamation mark "!" - It was guessed by the software, MAPPED_MANUAL: Displayed as "MAPPED" + a green checkmark - It was either set manually by the user, or the user clicked the button "MAPPED" to confirm a "MAPPED_AUTO" value.
|  Image Removed Image Added |
Once all entities are mapped, you can proceed to the next step.
...