Confluence Space Import Error

[Roei Soudai]

Hi, 
I export a space in XML format from one account and I`m trying to import it to another account but I`m getting a FK issue after extracting the space zip file.

ERROR: insert or update on table "content" violates foreign key constraint "fk_content_creator"

I saw another issue raised and closed and the data model was fixed but both accounts are on the cloud with latest version, so what should I do?

Regards,
Roei

[Max Foerster - K15t]

Hi @Roei Soudai, and welcome to the community!

There's an ongoing issue with XML exports (from DC and Cloud; it doesn't matter) not being able to be imported again. Confluence will return a variety of error messages like the foreign key constraint you saw or, for example,

"Transaction rolled back because it is marked as rollback only."

I work for a marketplace partner, and we have seen these errors often lately as we rely on space exports to troubleshoot customer issues. I contacted Atlassian to escalate this issue and have been in touch with them since the end of July, as it's blocking our customers and us. Here's what I can tell you to fix your situation.

We were told to refer our customers running into those issues to Atlassian support as they have the tools to fix the broken imports and import them anyway.

But this might be a lengthy process because I just had to discuss and explain the issue to the support after a customer added me to the request. After all, they were unaware and did not understand what she requested. But hey, it's worth a try.

Additionally, I got the response that it's unlikely that the broken XML exports in Confluence will be fixed, as CSV export is the new and preferred export method. The disadvantage is that CSV exports are not customizable and don't contain third-party application content.

So, I would ask you to vote on this public issue that was created: CONFCLOUD-76611 - CSV space import is missing content properties from marketplace apps 

Best, Max

[Ravina]

Hi @Roei Soudai Welcome to the Atlassian community.

This looks like a known bug with space confluence import, there is no workaround for this as Atlassian closed it and mentioned that workaround will be added whenever available. please check the below ticket for more details

https://jira.atlassian.com/browse/CONFCLOUD-75487

Thanks

Ravina