![]() Clone your production Confluence instance to a test server on another computer now. Space keys may only consist of ASCII letters or numbers (A-Z, a-z, 0-9) and no empty spaces are allowed in the key.Ģ. Select a new, unique space key and name for the second space. * Read the process in full before beginning.ġ. * When importing a space export for a space that already exists, the previous space content will be overwritten. You need to substitute your own keys for oldkey and newkey, and your own space names for Old Space Name and New Space Name. * Where examples are given, they involve changing oldkey:Old Space Name into newkey:New Space Name. Users running older versions are recommended to upgrade Confluence before continuing. * The instructions have been confirmed for Confluence 2.2 onwards. * May require manually updating external links to that space. Option 2: Manually Clone Or Rename A SpaceĪlternatively, it is possible to manually clone or rename a space by modifying an XML backup of the target space. If this occurs, please ensure that your space has not been created before attempting to copy the space again. ![]() Note that copying a space can take a long time and may appear to time out when using this plugin (even when the copied space is created correctly). Note that this plugin is still in beta release, and is not officially supported by Atlassian. If you have exported a space that was using the documentation theme, make sure you make a note of any wiki markup customizations you may have made to the theme, as these will not be automatically applied to the default theme when the space is imported.The best option is to install the Copy Space Plugin. An easy way to do this is to first import users and groups, then import any spaces. To maintain your groups' permissions settings, make sure all your groups have a corresponding group with the same name that already exists in the destination site before importing the space. User data that will be imported includes:Īny permissions settings (space or page) associated with groups will be lost during import, unless a group with the same name already exists in the destination site. This is to make sure that mentions, comments, and page history stay active. It will, however, import some user data connected to the spaces you're importing. User accounts, meaning it doesn't give users product access or add them to any groups. If it is important to you to have a different space key, you can create a new space with a different key, move your pages into that space, and then import the new space. You can't change space keys in Confluence. This is so that Confluence can update any Jira macros to pull the Jira data from the new location. If you are also importing or migrating a Jira project that is linked to your Confluence space, complete the Jira import before you import your Confluence space. If your Confluence site also has Jira, you can link a Confluence space to a Jira project when importing a space by selecting the project from the Link to Cloud project dropdown on the import screen. On this page, the terms 'source Confluence site' or 'source site' are used to mean the Confluence Cloud instance that data is being copied from. To integrate an existing G Suite user directory, see Integrate with G Suite. To learn about importing user accounts, which lets you give users product access and add them to groups, read the Confluence section of Determine your user migration strategy. For instructions on how to migrate an entire cloud site, see Migrate a Confluence Cloud site to an existing cloud site. These instructions are for importing a Confluence Cloud space, rather than an entire site, to another cloud site. To migrate a Confluence space from a server instance to a cloud site, we recommend using the Confluence Cloud Migration Assistant. This document is specific to importing a Confluence space from a cloud site to another cloud site.
0 Comments
Leave a Reply. |