Database doesn't display after migrating a space to a different cloud account

Question

I have successfully migrated a Confluence space from a cloud account to a different cloud account, using xml export - import.

The Confluence space includes several databases.

All databases have the same issue after migration:

* The database gets displayed in the space's page tree. It has a URL in the new space.
However, it does not load in the UI.
* Individual entries that are inserted on pages point to the database in the original location

I am testing with a user that has admin permissions in both accounts and for both spaces. I have checked permissions after migration and all content is working fine.

Re-indexing should not be the cause. The space is small, and migration was completed several hours ago.

This is the first time I have tried to migrate a space that includes databases.

Any proposal how to preserve a database when migrating the space to a different account?

Tomislav Tobijas · Answer

Hey @Thierry Raoul Berset ,

Yeah... Unfortunately, if you do space export/import, databases and whiteboards will not be copied or imported. Specifically, the database shell will import, but once you click on it in the destination space, it won't open.

There's a feature request for it: CONFCLOUD-77610: Following the import of Space in Confluence cloud to cloud migration using CSV, Confluence database data is missing > this one is for CSV format, but the same applies for XML.

Anyway, what I do in these cases is stick with the same export/import method, and then once that's done, I navigate to each database and export it to CSV format. Once I've exported all DBs, I would navigate to the destination site and then create new databases and import data from those downloaded CSV files. 👈

Not the most user-friendly experience, but it works.

Cheers,
Tobi

Trudy P Claspill · Answer

Hello @Thierry Raoul Berset

I have not tried that process myself.

Have you opened a support case directly with Atlassian to find out if this is a known limitation? I did not find it in the documentation I checked nor in the public backlog.

I did see that databases are not supported in the export of a Site backup.

https://support.atlassian.com/confluence-cloud/docs/create-a-site-backup/

But I don't know if that also applies to Space exports.