I am trying to migrate one space from our on-premises installation to Confluence Cloud. Everything is set up:
The export of the space fails at 40% in both development and production environments with the following error in the logs:
2022-05-13 10:06:34,638 INFO [Caesium-1-3] [service.stepexecutor.space.SpaceExportExecutor] info Initiating space export for spaceKey: ABCD planId: 54aed50f-0ccc-4811-83f0-a498ea8c44dd
-- stepConfig: {"spaceKey":"ABCD","fileId":"1ba14f60-d09e-4fff-bd86-58fa7e19e3a6","cloudId":"9e1ce7f8-2061-4dda-805e-4c5d60ce3b8c"} | cloudId: 9e1ce7f8-2061-4dda-805e-4c5d60ce3b8c | planName: ToCloudMigration02 | stepType: CONFLUENCE_EXPORT | stepId: c2817bb1-4152-426d-b7bb-38a0dfce51f3 | planId: 54aed50f-0ccc-4811-83f0-a498ea8c44dd | cloudUrl: https://acme.atlassian.net | taskName: Migrate space ABCD | taskId: 4a495af7-f063-47f6-958c-d3103f634cd3
2022-05-13 10:06:36,265 ERROR [Caesium-1-3] [agent.service.stepexecutor.ProgressTracker] error Step failed, message: Failed to export [cloudId=9e1ce7f8-2061-4dda-805e-4c5d60ce3b8c,fileId=1ba14f60-d09e-4fff-bd86-58fa7e19e3a6,spaceKey=ABCD]
-- stepConfig: {"spaceKey":"ABCD","fileId":"1ba14f60-d09e-4fff-bd86-58fa7e19e3a6","cloudId":"9e1ce7f8-2061-4dda-805e-4c5d60ce3b8c"} | cloudId: 9e1ce7f8-2061-4dda-805e-4c5d60ce3b8c | planName: ToCloudMigration02 | stepType: CONFLUENCE_EXPORT | stepId: c2817bb1-4152-426d-b7bb-38a0dfce51f3 | planId: 54aed50f-0ccc-4811-83f0-a498ea8c44dd | cloudUrl: https://acme.atlassian.net | taskName: Migrate space ABCD | taskId: 4a495af7-f063-47f6-958c-d3103f634cd3
java.lang.NullPointerException
at com.atlassian.migration.agent.export.SpaceNoAttachmentsXmlExporter.configureXmlExporter(SpaceNoAttachmentsXmlExporter.java:83)
at com.atlassian.migration.agent.export.SpaceNoAttachmentsXmlExporter.doExportImpl(SpaceNoAttachmentsXmlExporter.java:76)
at com.atlassian.migration.agent.export.SpaceNoAttachmentsXmlExporter.lambda$doExport$1(SpaceNoAttachmentsXmlExporter.java:71)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
2022-05-13 10:06:43,517 INFO [Caesium-1-4] [service.stepexecutor.export.SpaceExportCacheService] removeExpiredCacheEntries Removing export cache entries that have exceeded their TTL.
The Users and groups migration prior to the space export succeeds every time before I hit this error.
draw.io does have a pre-migration step for Cloud migrations. Info can be found here:
They recommend doing this on a test instance. Their wording makes it sound like you must convert the entire site at the same time (you cannot convert a single Space) and that the existing pages will break (make site read-only and immediately migrate to Cloud).
Their wording isn't very clear on this, so you may want to reach out to their support team if you cannot use a test instance.
If you have links to Confluence pages within your diagrams, you also need to do this (the CCMA App Assessment should have shown you this link - it's the 'Cloud migration pathway' link on their Marketplace listing):
Since draw.io data is stored within the page and page attachments, it does not require a separate CCMA step, which is why it is not listed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, we're on 7.14.1 so will upgrade. I will check the known issues next time, cheers.
I think the draw.io migration guide only applies if you have links to confluence docs in your diagrams (which we don't for the space I'm migrating).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.