Space import failed

[Alexi Vanderstraeten]

Hello there,

We are trying to import a backup from a Confluence version (6.15.4) and restored to a new one (7.4.6).

The import failed and our technicians are telling me it's because of versioning and because of that the database got corrupted.

Can you please advice on what is the best way to proceed to be able to export the content and import it back in the new one?

Cheers.

[Thiago Masutti · Accepted solution]

Hi @Alexi Vanderstraeten 

If you have a Space export from Confluence 6.15.4, then it would be fine to import that Space in an existing Confluence 7.4.6.
However, I would check if you really have a Space or a full site export.

You can unzip the export file and check the exportDescriptor.properties for that information.
For example, the below is a sample from an Space export.

source=server
buildNumber=4517
createdByVersionNumber=7.4.8
ao.data.version.com.atlassian.mywork.mywork-confluence-host-plugin=8.0.4
ao.data.version.min.com.atlassian.confluence.plugins.confluence-space-ia=5.0
supportEntitlementNumber=SEN-500
exportType=space
createdByBuildNumber=8402
spaceKey=TS1
backupAttachments=true
defaultUsersGroup=confluence-users
ao.data.list=com.atlassian.mywork.mywork-confluence-host-plugin, com.atlassian.confluence.plugins.confluence-space-ia
ao.data.version.min.com.atlassian.mywork.mywork-confluence-host-plugin=1.1.30
ao.data.version.com.atlassian.confluence.plugins.confluence-space-ia=17.4.3

If you can confirm it's a Space export, then it would be fine to import it an existing Confluence instance.

If the import failed, then you can get from the application log files the reason, which would be helpful in case of a new problem.

Now, if it's a full site import, you should be able to import it from 6.15.4 into a new 7.4.6 instance.

Kind regards,
Thiago Masutti

[Thiago Masutti]

Hi @Alexi Vanderstraeten 

If you have a Space export from Confluence 6.15.4, then it would be fine to import that Space in an existing Confluence 7.4.6.
However, I would check if you really have a Space or a full site export.

You can unzip the export file and check the exportDescriptor.properties for that information.

If you can confirm it's a Space export, then it would be fine to import it an existing Confluence instance.

If the import failed, then you can get from the application log files the reason, which would be helpful in case of a new problem.

Now, if it's a full site export, you should be able to import it from 6.15.4 into a new 7.4.6 instance as well.
Note that a full site import will overwrite whatever you have in the target instance.

Kind regards,
Thiago Masutti

[Thiago Masutti]

Hi @Alexi Vanderstraeten 

If you have a Space export from Confluence 6.15.4, then it would be fine to import that Space in an existing Confluence 7.4.6.
However, I would check if you really have a Space or a full site export.

You can unzip the export file and check the exportDescriptor.properties for that information.
For example, the below is a sample from an Space export.

source=server
buildNumber=4517
createdByVersionNumber=7.4.8
ao.data.version.com.atlassian.mywork.mywork-confluence-host-plugin=8.0.4
ao.data.version.min.com.atlassian.confluence.plugins.confluence-space-ia=5.0
supportEntitlementNumber=SEN-500
exportType=space
createdByBuildNumber=8402
spaceKey=TS1
backupAttachments=true
defaultUsersGroup=confluence-users
ao.data.list=com.atlassian.mywork.mywork-confluence-host-plugin, com.atlassian.confluence.plugins.confluence-space-ia
ao.data.version.min.com.atlassian.mywork.mywork-confluence-host-plugin=1.1.30
ao.data.version.com.atlassian.confluence.plugins.confluence-space-ia=17.4.3

If you can confirm it's a Space export, then it would be fine to import it an existing Confluence instance.

If the import failed, then you can get from the application log files the reason, which would be helpful in case of a new problem.

Now, if it's a full site export, you should be able to import it from 6.15.4 into a new 7.4.6 instance as well.
Note that a full site import will overwrite whatever you have in the target instance.

Kind regards,
Thiago Masutti