You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I've migrated all of our Confluence spaces from on prem to the cloud, except for one. I used the Cloud Migration Tool and every time I try to migrate just that site it fails with the same useless error: "Failed to export [spaceKey=EXD,fileid=7ea....,cloudId=4e60....]" (I used the ... instead of typing out the full ID).
The only errors I see on the server have to do with failing to find images (that don't exist) or this: "[swift.confluence.scriptutil.ScriptUtils] isReadOnly Cannot determine whether readonly mode is enabled : {}"
I've tried exporting/importing and get an error about the version of Confluence Server needing to be newer but that doesn't apply since my version of server is newer than the minimum listed in the error.
I assume there is something wonky in this space but can't pin down what it is.
Any ideas?
Did your other spaces utilize the Swift Scripting add-on? I know that it is not supported by Cloud, so that could be causing your issues.
The space doesn't exist already - neither the name nor the key.
I tried the export and it keeps failing with the error about how it needs to be 6.14 or later, but I'm on 6.7.1.
The permissions are the same on both sides.
Like I said, it works for all other spaces. For this one it absolutely will not. On trying to export it does fail unless I exclude a certain page but I see nothing strange about that page. I tried removing it and the images on it, then it exported but the same error came up on import.
Thanks for your responses. I'm baffled.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Abby Cooke I assume you're using either Standard or Premium, both of which entitle you to support directly from Atlassian. You may want to contact them if you have exhausted searching the Knowledgebase and Community forums.
Darryl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a case open with them. I was hoping while I waited to find someone else who encountered this. I've tried everything I can think of.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another suggestion or two if @Kiran Panduga {Appfire} 's don't work out:
Have you tried exporting the space without using the tool? Space Settings-Content Tools-Export-XML.
Also, have you verified that there are no permission restrictions on the space to not allow it to be exported?
Darryl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Abby Cooke ,
Suspect the spaceName or SpaceKEY already exist in the Confluence Cloud.
Can you verify the spaceName and key in Confluence Cloud. Duplicate spaceName and key will not allow the import of the space?
Also, Could you confirm with us from what version of Confluence the space export originated?
Thanks,
Kiran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.