Confluence generates "Migrate all Page Templates using a storage format round-trip conversion" - Not Ok message during space export

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Problem

The legacy backup and restore system is available only in versions lower than Confluence 9.0. This means that scheduled backups, which used the legacy system, are no longer available.

During the nightly backup or during a space export (through Space Tools > Content Tools > Export > XML), the atlassian-confluence.log file shows

atlassian-confluence.log

1 2 2015-08-30 02:00:00,113 INFO [scheduler_Worker-6] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 4517: "Migrate all Page Templates using a storage format round-trip conversion" - Not Ok 2015-08-30 02:00:00,114 INFO [scheduler_Worker-6] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: "Migrate all Page Templates using a storage format round-trip conversion" prevents compatibility before 4517

Diagnosis

Environment

  • Occurs on versions of Confluence from 5.3 (Build 4523).

Cause

This is an information level message (INFO) that is generated when exporting a space in a version of Confluence 5.3 (Build 4527) or higher.

Solution

Resolution

This information message alerts the administrator that the exported space cannot be imported into a a version of Confluence lower than 5.3 (Build 4527). The Confluence Build Information page lists the versions of Confluence with their build number.

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.