Skip to Content

Changes for page XWiki Migrations

Last modified by Agnease on 2026/05/25 16:46
From version 9.1
edited by Agnease
on 2026/05/25 12:59
Change comment: There is no comment for this version
To version 11.1
edited by Agnease
on 2026/05/25 16:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -28,11 +28,11 @@
28 28   #set ($migrationReasonItems = [{
29 29   'title': 'Preserve structure',
30 30   'icon': 'sitemap',
31 - 'content': 'Keep spaces, hierarchies, navigation and page relationships understandable after the move.',
31 + 'content': 'Keep spaces, hierarchies, navigation, page relationships and entry points understandable after the move.',
32 32   'items': [
33 33   'Space and page hierarchy mapping',
34 34   'Navigation and landing page planning',
35 - 'Related content and category structure'
35 + 'Search and findability considerations'
36 36   ]
37 37   },{
38 38   'title': 'Protect continuity',
... ... @@ -46,11 +46,11 @@
46 46   },{
47 47   'title': 'Improve maintainability',
48 48   'icon': 'database',
49 - 'content': 'Use the migration as an opportunity to clean up content, introduce metadata and prepare better structures.',
49 + 'content': 'Use the migration as an opportunity to clean up content, introduce metadata and redesign what should not be copied as-is.',
50 50   'items': [
51 51   'Templates and structured data',
52 52   'Metadata and tagging strategy',
53 - 'Content cleanup recommendations'
53 + 'Manual cleanup recommendations'
54 54   ]
55 55   }])
56 56  
... ... @@ -60,8 +60,8 @@
60 60  
61 61   <p class="section-intro">
62 62   Documentation platforms usually contain years of accumulated knowledge, links, attachments, permissions,
63 - templates and habits. A successful migration should preserve what matters while improving how the knowledge
64 - is organized and maintained in XWiki.
63 + templates, macros and habits. A successful migration should preserve what matters, reduce broken navigation
64 + and improve how the knowledge is organized and maintained in XWiki.
65 65   </p>
66 66  
67 67   <div class="pathways">
... ... @@ -119,8 +119,9 @@
119 119   <h2 id="migration-sources-title">Common migration sources</h2>
120 120  
121 121   <p class="section-intro">
122 - Each source system has different export formats, content models and limitations. The migration approach
123 - depends on the quality of the source data, the expected XWiki structure and the amount of transformation needed.
122 + Each source system has different export formats, content models, permissions and limitations.
123 + The migration approach depends on the quality of the source data, the expected XWiki structure
124 + and the amount of conversion, cleanup or redesign needed.
124 124   </p>
125 125  
126 126   <div class="services-grid">
... ... @@ -149,13 +149,13 @@
149 149   'content': 'Decide spaces, page hierarchy, templates, metadata, permissions, naming rules and navigation strategy.'
150 150   },{
151 151   'title': 'Run a sample migration',
152 - 'content': 'Migrate a representative subset of content to identify conversion issues and validate the approach.'
153 + 'content': 'Migrate a representative subset of content to identify formatting, macro, link, attachment and structure issues.'
153 153   },{
154 154   'title': 'Refine conversion and cleanup rules',
155 155   'content': 'Adjust mappings, formatting, link handling, attachments, macros, categories and content cleanup decisions.'
156 156   },{
157 157   'title': 'Execute and validate the migration',
158 - 'content': 'Run the migration, review key content areas, verify attachments and links, and document remaining follow-up work.'
159 + 'content': 'Run the migration, review key content areas, verify attachments, links, redirects and navigation, and document remaining follow-up work.'
159 159   }])
160 160  
161 161   <section id="migration-process" class="split-section" aria-labelledby="process-title">
... ... @@ -171,8 +171,8 @@
171 171   </p>
172 172  
173 173   <p>
174 - Migrations are best handled iteratively: assess the source, run a sample migration, validate the result,
175 - adjust the transformation rules and then proceed with a controlled migration plan.
175 + Migrations are best handled iteratively: assess the source, run a sample migration, validate links,
176 + attachments, formatting and important spaces, adjust the conversion rules and then proceed with a controlled migration plan.
176 176   </p>
177 177   </div>
178 178  
... ... @@ -202,9 +202,9 @@
202 202   'icon': 'lock',
203 203   'content': 'Review and mapping of access rights where the source system contains meaningful permission rules.'
204 204   },{
205 - 'title': 'Metadata strategy',
206 - 'icon': 'tags',
207 - 'content': 'Tags, categories, templates, XWiki classes or structured data to improve long-term maintainability.'
206 + 'title': 'Cleanup and validation',
207 + 'icon': 'check-square-o',
208 + 'content': 'Post-migration review of important spaces, broken links, attachments, formatting issues and content needing manual cleanup.'
208 208   }])
209 209  
210 210   <section aria-labelledby="included-title">
... ... @@ -212,8 +212,9 @@
212 212   <h2 id="included-title">What can be included</h2>
213 213  
214 214   <p class="section-intro">
215 - The exact migration scope depends on the source system and the quality of the exported content. A migration
216 - engagement can include both technical conversion and practical information architecture work.
216 + The exact migration scope depends on the source system and the quality of the exported content.
217 + A migration engagement can include technical conversion, information architecture, permission review,
218 + cleanup recommendations and post-migration validation.
217 217   </p>
218 218  
219 219   <div class="widgets">
... ... @@ -231,59 +231,6 @@
231 231   </div>
232 232   </section>
233 233  
234 - ## IMPORTANT CONSIDERATIONS
235 - #set ($migrationConsiderationItems = [{
236 - 'title': 'Macros and special content',
237 - 'icon': 'code',
238 - 'content': 'Source-specific macros, embeds, widgets or dynamic content may require conversion, replacement or redesign.'
239 - },{
240 - 'title': 'Links and redirects',
241 - 'icon': 'link',
242 - 'content': 'Internal links, external references, old URLs and bookmarks should be reviewed to reduce broken navigation.'
243 - },{
244 - 'title': 'Search and findability',
245 - 'icon': 'search',
246 - 'content': 'Content organization, titles, metadata and navigation affect how easily users find migrated knowledge.'
247 - },{
248 - 'title': 'User adoption',
249 - 'icon': 'user',
250 - 'content': 'A technically successful migration still needs clear navigation, familiar entry points and user guidance.'
251 - },{
252 - 'title': 'Validation effort',
253 - 'icon': 'check-square-o',
254 - 'content': 'Important spaces and high-value content should be reviewed after migration to catch conversion issues.'
255 - },{
256 - 'title': 'Cutover planning',
257 - 'icon': 'clock-o',
258 - 'content': 'Timing, source freeze, final migration, redirects and communication should be planned before go-live.'
259 - }])
260 -
261 - <section class="services" aria-labelledby="considerations-title">
262 - <div class="container">
263 - <h2 id="considerations-title">Important migration considerations</h2>
264 -
265 - <p class="section-intro">
266 - Not every element from the source system maps perfectly to XWiki. The migration plan should distinguish
267 - between what can be converted automatically, what needs manual cleanup and what should be redesigned.
268 - </p>
269 -
270 - <div class="services-grid">
271 - #foreach ($entry in $migrationConsiderationItems)
272 - <article class="service">
273 - <div class="service-icon" aria-hidden="true">
274 - <i class="fa fa-$entry.icon"></i>
275 - </div>
276 -
277 - <div class="service-body">
278 - <h4>$entry.title</h4>
279 - <p>$entry.content</p>
280 - </div>
281 - </article>
282 - #end
283 - </div>
284 - </div>
285 - </section>
286 -
287 287   ## RELATED SERVICES
288 288   #set ($relatedMigrationServiceItems = [{
289 289   'title': 'XWiki Development & Integrations',
... ... @@ -302,7 +302,7 @@
302 302   <h2 id="related-title">Related XWiki services</h2>
303 303  
304 304   <p class="section-intro">
305 - Migration work often connects with custom development, support and upgrade planning.
254 + Migration work often connects with custom development, support and long-term platform maintenance.
306 306   </p>
307 307  
308 308   <div class="resource-grid">
... ... @@ -324,8 +324,8 @@
324 324   <h2 id="cta-title">Planning a migration to XWiki?</h2>
325 325  
326 326   <p>
327 - Send a short description of the source system, approximate content volume, export options and the type of
328 - XWiki structure you want to achieve. A sample export or representative content area is often enough to start.
276 + Send a short description of the source system, approximate content volume, export options, expected timing
277 + and the type of XWiki structure you want to achieve. A sample export or representative content area is often enough to start.
329 329   </p>
330 330  
331 331   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a migration</a>