Exporting a space to another instance

Using Confluence's build-in XML export-import

When exporting a space, we don't include the requirements in the export. Therefore, the following information will be lost if you only use Confluence's built-in XML export-import:

• Baselines will be lost,
• Links from other spaces will be lost,
• Links from Jira will be lost. They will still appear on the Jira side, but will reach a 404 page in Confluence. They won't appear on the new requirements in Confluence.

After you reimport, please use Requirement Yogi's reindexation in the space administration.

If you need to

...

keep baselines, links from other spaces and from Jira, then proceed to the next title.

Moving data manually to another Confluence instance

• Our requirement is that the following tables are correct:
  • AO_32F7CE_DBBASELINE
  • AO_32F7CE_DBREQUIREMENT - Simple import
  • AO_32F7CE_DBPROPERTY- Simple import (with foreign key to DBREQUIREMENT),
  • AO_32F7CE_DBLINK - Don't forget to change the Page IDs and the Jira Applink ID.
  • AO_32F7CE_DBDEPENDENCY - Import (with foreign key to DBREQUIREMENT) + references to DBLink.
  • Don't forget AO_32F7CE_DBBASELINE, AO_32F7CE_DBTRACEABILITYMATRIX, AO_32F7CE_DBISSUE_TEMPLATE.
• Our other requirement is that tables in Jira correctly match the tables of Confluence:
  • AO_42D05A_DBREMOTEREQUIREMENT
  • AO_42D05A_DBISSUELINK
  • AO_42D05A_DBAUDITTRAIL
• So, the process would be:
  1. Import a space to the new Confluence,
  2. Find a way to map old page IDs to new page IDs,
  3. Import all RY tables, keeping foreign keys,
  4. Change Applink IDs in DBLink,
  5. Change Page IDs in DBLink,
  6. Jira: Before exporting, ensure issue numbers match issue ids, in DBIssueLink,
  7. Jira: Import all RY tables,
  8. Jira: After importing, update issue ids to issue numbers in DBIssueLink,
  9. Jira: Update the Applink IDs in DBRemoteRequirement.

...