Can I change the space key when exporting a space so there is no conflict when importing to an OnDemand site?

[Jeff Puzzo]

We are in the process of moving a few spaces from two different installed Confluence instances into the same OnDemand Confluence instance.

Two of the spaces that we are trying to move to the OnDemand site have the same Space Key, one from each of the installed Confluence sites.

We need, and want, them to have different keys in the new location (OnDemand).

Is there documentation available for changing a space key (even if it's manual)?

Is there a better way than modifying the database pre-export or modifying the XML post-export?

[Jeff Puzzo · Accepted solution]

I found reference to a custom User Macro written by Ed Bacher and updated by Zsolt Kocsmarszky on this page:

https://confluence.atlassian.com/pages/viewpage.action?pageId=14286901

It worked for me on a test space.

Is this condoned by Atlassian or at least can Atlassian say it won't break anything? Short of an official tool, this may be my best bet.

Other answers still welcome, especially if your solution is more "official."

EDIT 2014-04-10:

I'm going to accept my response as an answer since there doesn't seem to be a real answer and this workaround worked for me.

Thanks,

Jeff

[Ahmed Choudhry]

If I change the space name before exporting to our production server, all the pages would be update on the current server?

if yes, then I can export the space.