...
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: - After a Confluence reimport, perform a Jira reimport.
|
Confluence DC → Same Confluence DC, but later in time. | Yes, but there is no reason to do that. - Please simply backup your Confluence instance using a way recommended by Atlassian.
|
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, or a Jira project | 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. |
Migrate from the Cloud to DC | No, this is not supported yet. Same, we're hoping to do it. |
...
Requirement Yogi lets you choose:
- The scope: It can be a Jira project or a Confluence space, or you can export the whole instanceis 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.
...