Last modified by Anca Luca on 2026/11/10 09:12

Hide last authors
Raphaël Jakse 1.1 1 During a Confluence migration, Confluence elements are migrated to the XWiki elements that are the most similar to them. Here's a table that match Confluence elements to their XWiki counterparts:
2
Raphaël Jakse 9.1 3 |=Confluence element|=XWiki element|=Remarks
4 |User|User profile in the XWiki space|Confluence user ids can be mapped to specific XWiki user names with the user id mapping input stream property.
Raphaël Jakse 8.1 5 User ids are also used for comments and permission migrations. See [[Documentation on the Confluence Input filter stream parameters>>documentation.extensions.admin.confluence.input-parameters.WebHome]].
Raphaël Jakse 9.1 6 |Groups|Goups in the XWiki space|Group names can be mapped to specific XWiki group names with the group mapping input stream property.
Raphaël Jakse 8.1 7 Group names are also used during permission migrations. See [[Documentation on the Confluence Input filter stream parameters>>documentation.extensions.admin.confluence.input-parameters.WebHome]].
Raphaël Jakse 9.1 8 |Labels|Tags (XWiki.TagClass objects)|(((
Raphaël Jakse 1.1 9 Each label has its own XWiki tags object.
10
11 * Page labels are set as tags on the document
12 * Space labels are set as tags on the space home page
13 * Attachment labels are dropped
14
15 In Confluence, a label belongs to a user. We drop this information.
16 )))
Raphaël Jakse 11.1 17 |Page Favorites|We don't support favorites, which are implemented using the label named "favourite"|
18 |Space Favorites|We don't support space favorites.|
Raphaël Jakse 10.1 19 |Comments|Comments (XWiki.XWikiComments objects)|
Raphaël Jakse 9.1 20 |Space|(((
Raphaël Jakse 1.1 21 An XWiki space and all its children
22
23 often a root space, though not necessarily if the "root space" parameter of the migrator is used
Raphaël Jakse 9.1 24 )))|(((
Raphaël Jakse 1.1 25 The confluence space key is, by default, translated to a XWiki entity name, following the XWiki page name validation, at the root of the wiki or in the space set in the "root space" parameter.
26
27 Note: A confluence space is not the same thing as an XWiki space.
28
29 * A confluence space is something at the root of the instance that contains a document tree, among other things
30 * A XWiki space is just one level in the tree and is not necessarily at the root
31
32 Confluence users might be confused by this subtle semantic difference and could cause misunderstandings between us and the clients.
33 )))
Raphaël Jakse 9.1 34 |Space owner|-|We don't have this concept in XWiki. Space and content permissions will be used to reproduce who has access to what.
35 |Space description|Nothing|The space descriptions are discarded. We don't have such a thing in XWIki
36 |Space Home page|XWiki WebHome Document|(((
Raphaël Jakse 6.1 37 Space home pages are migrated to the top level WebHome page in the migrated space.
38
39 {{info}}
40 In Confluence, the home page of a space can be a child of another page.
41
42 In this case, we break this relationship: after import, the home page is the top level page of the space and the top level ancestor of the home page in Confluence is considered an orphan.
43 {{/info}}
44
45 {{info}}
46 In Confluence, it is possible for a space not to have any home page.
47
48 In this case, a minimal home page (with a ConfluencePageClass object with a fake id) listing its children will be generated on import.
49 {{/info}}
50 )))
Raphaël Jakse 9.1 51 |Orphans|Regular children of the space home page|In Confluence, it is possible for pages in a space not to have any parent page. We call these pages orphans. By default, these pages are imported as regular documents under the home page. There's a [[parameter>>documentation.extensions.admin.confluence.input-parameters.WebHome]], "Orphan mode", to hide them or to drop them altogether.
Raphaël Jakse 13.1 52 |Page|XWiki WebHome Document|(((
Raphaël Jakse 1.1 53 Documents are migrated as XWiki WebHome documents in their own space.
54
55 Their name is built from their title in confluence (optionally and by default converted to a valid name in the page naming strategy of XWiki).
56 \\Content marked as deleted, archived or draft is not imported. If the locale parameter is set, it will be used for the locale of all imported documents.
57 \\These properties will be set from the Confluence page object property:
58
59 * The parent
60 * The revision
61 * The revision comment
62
63 The creation author, the creation date and the title of the document are set from the revision author, the revision date and the title present in the Confluence Page object.
64
65 Note: the "Preserve version" output filter stream parameter needs to be set to true for dates to be kept after migration, or the document date will be set to the time at which the document was migrated. The creation author can also be overridden using an output filter stream parameter. Output filter stream parameters are hidden from the Confluence Migrator Pro UI.
66
67 For the content, the confluence syntax are translated into XWiki syntax, including macros. Some macros need special handling and  are imported in a specific way (especially if for some Confluence macro named X, there exists a XWiki macro named X that does not do the same thing. Then X is renamed to a macro Y that implement X with similar functionality as in Confluence, either in XWiki Standard or in the Pro Macros).
68 )))
Raphaël Jakse 13.1 69 |Page history|XWiki document revisions|Optional and by default.
Raphaël Jakse 12.1 70 |Space Permissions|XWiki rights objects in a WebPreferences document|(% colspan="1" rowspan="2" %)See [[Confluence to XWiki permission mapping>>doc:documentation.extensions.admin.confluence.permission-handling.WebHome]].
Raphaël Jakse 13.1 71 |Page Permissions|XWiki rights objects in the document
Raphaël Jakse 9.1 72 |Blog space| |Same as space
73 |Blog descriptor|XWiki WebHome document with a Blog.BlogClass object|(((
Raphaël Jakse 1.1 74 At the time of writing, title is set to the blog space name, postsLayout is set to "image" and is displayType is set to "paginated".
75 )))
Raphaël Jakse 9.1 76 |Blog posts|XWiki Document with a Blog.BlogPostClass object|Blog posts are migrated as Blog.BlogPostClass objects, each in its XWiki terminal documents. At the time of writing, title is set to the blog post title, published is set to 1, content is set to the content, hidden is set to 0
77 |Attachment|Attachment|(((
Raphaël Jakse 1.1 78 If the actual attachment file is not found in the export package, the attachment won't be imported at all.
79 The attachment size is taken from the confluence export XML file if present, fallback to the actual file content size if not found.
80
Anca Luca 3.1 81 {{version since="9.78.0" product="Confluence XML"}}
82 Attachments history is imported.
83 {{/version}}
Raphaël Jakse 1.1 84 )))
Raphaël Jakse 13.1 85 |Space Template|Template and corresponding Template provider|(((
Anca Luca 14.1 86 Space templates are migrated as templates in the Templates subtree, under the page that corresponds to the Confluence space they belong to. For each template, a template provider is created as well, to configure the availability of the template in the pagetree corresponding to the Confluence space.
Raphaël Jakse 13.1 87
88 In Confluence, templates contain placeholders that are filled with a dialog box on page creation. In XWiki, placeholders are left as-is (the content of placeholders is migrated in the template document).
89 )))
Raphaël Jakse 9.1 90 |Confluence object id|Converted object title or name|(((
Raphaël Jakse 1.1 91 All confluence object has an integer id. This id isn't kept in XWiki. When applicable, its key (for spaces) or title (for documents) is used instead and converted (using page name validation for document and space names).
92 \\If the "Store Confluence details" is set to true, confluence detail are stored in a Confluence.Code.ConfluencePageClass object (id : the page id, url: the reconstructed confluence url, space: the space key).
93 )))
Raphaël Jakse 9.1 94 |Language macros (multilingual support)|Multilingual documents|(((
Raphaël Jakse 4.1 95 The way it works in Confluence: in the same document, you add macros named french, or english (Ieach supported language probably has a macro of its name, unprefixed). Then, when you display the document, only the parts matching your language are displayed. There's an "All" mode that displays everything.
Raphaël Jakse 1.1 96
Raphaël Jakse 4.4 97 If the Translated content support is enabled (which is the default; see [[xwiki:documentation.extensions.admin.confluence.input-parameters.WebHome]]), pages containing different languages are converted to translated XWiki documents. If the support is disabled, all the content is migrated, leaving these language macros as is (with a ##confluence_## prefix by default), in one document.
Raphaël Jakse 1.1 98 )))
Raphaël Jakse 9.1 99 |Follower / Followee|The follow feature|We don't currently import follower / followee relationships
100 |Likes|Likes|We don't currently import likes
101 |Roles and user classes|(We have yet to study these new features)|We don't currently support migrating these new features.

Get Connected