Skip to Content

Changes for page XWiki Migrations

Last modified by Agnease on 2026/05/25 16:46
From version 1.1
edited by Agnease
on 2026/05/12 13:02
Change comment: There is no comment for this version
To version 10.1
edited by Agnease
on 2026/05/25 16:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -xwiki-migrations
1 +XWiki Migrations
Content
... ... @@ -1,0 +1,328 @@
1 +{{velocity}}
2 +#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 +{{html clean="false"}}
4 + ## PAGE HEADER
5 + <section class="hero hero-centered" aria-labelledby="hero-title">
6 + <div class="container hero-inner">
7 + <div class="hero-kicker">
8 + <i class="fa fa-exchange" aria-hidden="true"></i>
9 + XWiki migration services
10 + </div>
11 + <h1 id="hero-title">Migrate knowledge into XWiki with structure and continuity</h1>
12 + <p class="lead">
13 + Move content from Confluence, SharePoint, MediaWiki, file-based documentation or legacy systems into XWiki
14 + while preserving hierarchy, attachments, links, permissions and long-term maintainability.
15 + </p>
16 + <div class="hero-actions">
17 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a migration</a>
18 + <a class="btn btn-secondary" href="#migration-process">See the migration approach</a>
19 + </div>
20 + </div>
21 + </section>
22 + ## WHY MIGRATION NEEDS CARE
23 + #set ($migrationReasonItems = [{
24 + 'title': 'Preserve structure',
25 + 'icon': 'sitemap',
26 + 'content': 'Keep spaces, hierarchies, navigation and page relationships understandable after the move.',
27 + 'items': [
28 + 'Space and page hierarchy mapping',
29 + 'Navigation and landing page planning',
30 + 'Related content and category structure'
31 + ]
32 + },{
33 + 'title': 'Protect continuity',
34 + 'icon': 'link',
35 + 'content': 'Reduce disruption by handling links, attachments, redirects, permissions and known content dependencies.',
36 + 'items': [
37 + 'Attachment and link preservation',
38 + 'Redirect and URL transition planning',
39 + 'Permission model review'
40 + ]
41 + },{
42 + 'title': 'Improve maintainability',
43 + 'icon': 'database',
44 + 'content': 'Use the migration as an opportunity to clean up content, introduce metadata and prepare better structures.',
45 + 'items': [
46 + 'Templates and structured data',
47 + 'Metadata and tagging strategy',
48 + 'Content cleanup recommendations'
49 + ]
50 + }])
51 + <section aria-labelledby="why-migration-title">
52 + <div class="container">
53 + <h2 id="why-migration-title">A migration is more than moving pages</h2>
54 + <p class="section-intro">
55 + Documentation platforms usually contain years of accumulated knowledge, links, attachments, permissions,
56 + templates and habits. A successful migration should preserve what matters while improving how the knowledge
57 + is organized and maintained in XWiki.
58 + </p>
59 + <div class="pathways">
60 + #foreach ($entry in $migrationReasonItems)
61 + <article class="pathway-card">
62 + <div class="card-heading">
63 + <div class="pathway-icon">
64 + <i class="fa fa-$entry.icon" aria-hidden="true"></i>
65 + </div>
66 + <h3>$entry.title</h3>
67 + </div>
68 + <p>$entry.content</p>
69 + <ul>
70 + #foreach ($item in $entry.items)
71 + <li>$item</li>
72 + #end
73 + </ul>
74 + </article>
75 + #end
76 + </div>
77 + </div>
78 + </section>
79 + ## MIGRATION SOURCES
80 + #set ($migrationSourceItems = [{
81 + 'title': 'Confluence to XWiki',
82 + 'icon': 'book',
83 + 'content': 'Migration of pages, spaces, attachments, links and content that may include macros or Confluence-specific formatting.'
84 + },{
85 + 'title': 'SharePoint to XWiki',
86 + 'icon': 'windows',
87 + 'content': 'Migration planning for document libraries, wiki-like content, intranet pages and knowledge structures.'
88 + },{
89 + 'title': 'MediaWiki to XWiki',
90 + 'icon': 'globe',
91 + 'content': 'Migration of wiki pages, links, categories, attachments and content that may require syntax or structure conversion.'
92 + },{
93 + 'title': 'Files and folders',
94 + 'icon': 'folder-open',
95 + 'content': 'Migration from file shares, exported documentation, PDFs, Word files or folder-based knowledge repositories.'
96 + },{
97 + 'title': 'Legacy knowledge systems',
98 + 'icon': 'archive',
99 + 'content': 'Extraction and restructuring of content from older internal tools, portals or custom documentation systems.'
100 + },{
101 + 'title': 'Mixed-source migrations',
102 + 'icon': 'random',
103 + 'content': 'Consolidation of content from multiple sources into a more coherent XWiki knowledge platform.'
104 + }])
105 + <section class="services" aria-labelledby="migration-sources-title">
106 + <div class="container">
107 + <h2 id="migration-sources-title">Common migration sources</h2>
108 + <p class="section-intro">
109 + Each source system has different export formats, content models and limitations. The migration approach
110 + depends on the quality of the source data, the expected XWiki structure and the amount of transformation needed.
111 + </p>
112 + <div class="services-grid">
113 + #foreach ($entry in $migrationSourceItems)
114 + <article class="service">
115 + <div class="service-icon" aria-hidden="true">
116 + <i class="fa fa-$entry.icon"></i>
117 + </div>
118 + <div class="service-body">
119 + <h4>$entry.title</h4>
120 + <p>$entry.content</p>
121 + </div>
122 + </article>
123 + #end
124 + </div>
125 + </div>
126 + </section>
127 + ## MIGRATION PROCESS
128 + #set ($migrationProcessItems = [{
129 + 'title': 'Assess the source content',
130 + 'content': 'Review structure, volume, attachments, links, permissions, formatting, macros, metadata and export options.'
131 + },{
132 + 'title': 'Define the target XWiki structure',
133 + 'content': 'Decide spaces, page hierarchy, templates, metadata, permissions, naming rules and navigation strategy.'
134 + },{
135 + 'title': 'Run a sample migration',
136 + 'content': 'Migrate a representative subset of content to identify conversion issues and validate the approach.'
137 + },{
138 + 'title': 'Refine conversion and cleanup rules',
139 + 'content': 'Adjust mappings, formatting, link handling, attachments, macros, categories and content cleanup decisions.'
140 + },{
141 + 'title': 'Execute and validate the migration',
142 + 'content': 'Run the migration, review key content areas, verify attachments and links, and document remaining follow-up work.'
143 + }])
144 + <section id="migration-process" class="split-section" aria-labelledby="process-title">
145 + <div class="container">
146 + <div class="split-grid">
147 + <div class="split-copy">
148 + <h2 id="process-title">A practical migration approach</h2>
149 + <p>
150 + A good migration starts with understanding how the source content is used today and how it should work
151 + in XWiki after the move. The objective is not only to transfer data, but to create a usable knowledge
152 + platform that people can navigate, search and maintain.
153 + </p>
154 + <p>
155 + Migrations are best handled iteratively: assess the source, run a sample migration, validate the result,
156 + adjust the transformation rules and then proceed with a controlled migration plan.
157 + </p>
158 + </div>
159 + <ol class="process-list">
160 + #foreach ($entry in $migrationProcessItems)
161 + <li>
162 + <strong>$entry.title</strong>
163 + $entry.content
164 + </li>
165 + #end
166 + </ol>
167 + </div>
168 + </div>
169 + </section>
170 + ## WHAT CAN BE INCLUDED
171 + #set ($migrationIncludedItems = [{
172 + 'title': 'Content conversion',
173 + 'icon': 'file-text-o',
174 + 'content': 'Page content, syntax, formatting, links, images, attachments and other reusable knowledge assets.'
175 + },{
176 + 'title': 'Structure mapping',
177 + 'icon': 'sitemap',
178 + 'content': 'Spaces, page hierarchy, navigation, naming rules, landing pages and organization of knowledge areas.'
179 + },{
180 + 'title': 'Permissions review',
181 + 'icon': 'lock',
182 + 'content': 'Review and mapping of access rights where the source system contains meaningful permission rules.'
183 + },{
184 + 'title': 'Metadata strategy',
185 + 'icon': 'tags',
186 + 'content': 'Tags, categories, templates, XWiki classes or structured data to improve long-term maintainability.'
187 + }])
188 + <section aria-labelledby="included-title">
189 + <div class="container">
190 + <h2 id="included-title">What can be included</h2>
191 + <p class="section-intro">
192 + The exact migration scope depends on the source system and the quality of the exported content. A migration
193 + engagement can include both technical conversion and practical information architecture work.
194 + </p>
195 + <div class="widgets">
196 + #foreach ($entry in $migrationIncludedItems)
197 + <article class="widget">
198 + <div class="icon" aria-hidden="true">
199 + <i class="fa fa-$entry.icon"></i>
200 + <h4>$entry.title</h4>
201 + </div>
202 + <p>$entry.content</p>
203 + </article>
204 + #end
205 + </div>
206 + </div>
207 + </section>
208 + ## IMPORTANT CONSIDERATIONS
209 + #set ($migrationConsiderationItems = [{
210 + 'title': 'Macros and special content',
211 + 'icon': 'code',
212 + 'content': 'Source-specific macros, embeds, widgets or dynamic content may require conversion, replacement or redesign.'
213 + },{
214 + 'title': 'Links and redirects',
215 + 'icon': 'link',
216 + 'content': 'Internal links, external references, old URLs and bookmarks should be reviewed to reduce broken navigation.'
217 + },{
218 + 'title': 'Search and findability',
219 + 'icon': 'search',
220 + 'content': 'Content organization, titles, metadata and navigation affect how easily users find migrated knowledge.'
221 + },{
222 + 'title': 'User adoption',
223 + 'icon': 'user',
224 + 'content': 'A technically successful migration still needs clear navigation, familiar entry points and user guidance.'
225 + },{
226 + 'title': 'Validation effort',
227 + 'icon': 'check-square-o',
228 + 'content': 'Important spaces and high-value content should be reviewed after migration to catch conversion issues.'
229 + },{
230 + 'title': 'Cutover planning',
231 + 'icon': 'clock-o',
232 + 'content': 'Timing, source freeze, final migration, redirects and communication should be planned before go-live.'
233 + }])
234 + <section class="services" aria-labelledby="considerations-title">
235 + <div class="container">
236 + <h2 id="considerations-title">Important migration considerations</h2>
237 + <p class="section-intro">
238 + Not every element from the source system maps perfectly to XWiki. The migration plan should distinguish
239 + between what can be converted automatically, what needs manual cleanup and what should be redesigned.
240 + </p>
241 + <div class="services-grid">
242 + #foreach ($entry in $migrationConsiderationItems)
243 + <article class="service">
244 + <div class="service-icon" aria-hidden="true">
245 + <i class="fa fa-$entry.icon"></i>
246 + </div>
247 + <div class="service-body">
248 + <h4>$entry.title</h4>
249 + <p>$entry.content</p>
250 + </div>
251 + </article>
252 + #end
253 + </div>
254 + </div>
255 + </section>
256 + ## RELATED SERVICES
257 + #set ($relatedMigrationServiceItems = [{
258 + 'title': 'XWiki Development & Integrations',
259 + 'url': 'services.xwiki-development-integrations',
260 + 'content': 'Custom applications, workflows, dashboards, integrations and structured knowledge solutions built on top of XWiki.',
261 + 'linkLabel': 'View development services'
262 + },{
263 + 'title': 'XWiki Support & Maintenance',
264 + 'url': 'services.xwiki-maintenance-support',
265 + 'content': 'Ongoing technical care for production environments after the migration is completed.',
266 + 'linkLabel': 'View support services'
267 + }])
268 + <section class="resource-strip" aria-labelledby="related-title">
269 + <div class="container">
270 + <h2 id="related-title">Related XWiki services</h2>
271 + <p class="section-intro">
272 + Migration work often connects with custom development, support and upgrade planning.
273 + </p>
274 + <div class="resource-grid">
275 + #foreach ($entry in $relatedMigrationServiceItems)
276 + <article class="resource-card">
277 + <h4>$entry.title</h4>
278 + <p>$entry.content</p>
279 + <a href="$xwiki.getURL($entry.url)">$entry.linkLabel</a>
280 + </article>
281 + #end
282 + </div>
283 + </div>
284 + </section>
285 + ## RELATED SERVICES
286 + #set ($relatedUpgradeServiceItems = [{
287 + 'title': 'XWiki Support & Maintenance',
288 + 'url': 'services.xwiki-maintenance-support',
289 + 'content': 'Ongoing technical care for production XWiki environments, including troubleshooting, maintenance planning and upgrade readiness.',
290 + 'linkLabel': 'View support services'
291 + },{
292 + 'title': 'XWiki Security Review',
293 + 'url': 'services.xwiki-security-review',
294 + 'content': 'Security-aware review of XWiki versions, extensions, permissions, authentication and upgrade exposure.',
295 + 'linkLabel': 'View security review'
296 + }])
297 + <section class="resource-strip" aria-labelledby="related-title">
298 + <div class="container">
299 + <h2 id="related-title">Related XWiki services</h2>
300 + <p class="section-intro">
301 + Upgrade work often connects with long-term maintenance, security review and production platform stability.
302 + </p>
303 + <div class="resource-grid">
304 + #foreach ($entry in $relatedUpgradeServiceItems)
305 + <article class="resource-card">
306 + <h4>$entry.title</h4>
307 + <p>$entry.content</p>
308 + <a href="$xwiki.getURL($entry.url)">$entry.linkLabel</a>
309 + </article>
310 + #end
311 + </div>
312 + </div>
313 + </section>
314 + ## CTA
315 + <section class="cta-section" aria-labelledby="cta-title">
316 + <div class="container">
317 + <div class="cta-panel">
318 + <h2 id="cta-title">Planning a migration to XWiki?</h2>
319 + <p>
320 + Send a short description of the source system, approximate content volume, export options and the type of
321 + XWiki structure you want to achieve. A sample export or representative content area is often enough to start.
322 + </p>
323 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a migration</a>
324 + </div>
325 + </div>
326 + </section>
327 +{{/html}}
328 +{{/velocity}}
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,0 +1,1 @@
1 +XWiki migration services for moving knowledge from Confluence, SharePoint, MediaWiki, file shares or legacy systems into a structured XWiki platform.
metaTitle
... ... @@ -1,0 +1,1 @@
1 +XWiki Migration Services from Confluence, SharePoint and MediaWiki | Agnease