Skip to Content

Changes for page XWiki Upgrade Services

Last modified by Agnease on 2026/05/25 16:11
From version 1.3
edited by Agnease
on 2026/05/01 12:16
Change comment: There is no comment for this version
To version 9.5
edited by Agnease
on 2026/05/25 16:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -xwiki-upgrades
1 +XWiki Upgrade Services
Content
... ... @@ -1,198 +1,126 @@
1 1  {{velocity}}
2 - #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 - {{html clean="false"}}
4 -
5 - ## HERO
2 +#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 +{{html clean="false"}}
4 + ## PAGE HEADER
6 6   <section class="hero hero-centered" aria-labelledby="hero-title">
7 7   <div class="container hero-inner">
8 - <h1 id="hero-title">XWiki Upgrades</h1>
9 - <p class="lead">Safe, planned upgrades for production XWiki platforms.</p>
10 -
11 - <ul class="benefits">
12 - <li>Latest LTS versions</li>
13 - <li>Security fixes</li>
14 - <li>Extension checks</li>
15 - <li>Minimal downtime</li>
16 - <li>Rollback planning</li>
17 - </ul>
18 -
19 - <div class="hero-cta">
20 - <a href="mailto:alex@agnease.com?subject=XWiki%20Upgrade%20Assessment">Request an upgrade assessment</a>
7 + <div class="hero-kicker">
8 + <i class="fa fa-refresh" aria-hidden="true"></i>
9 + XWiki upgrade services
21 21   </div>
22 - </div>
23 - </section>
24 -
25 - ## INTRO
26 - <section aria-labelledby="intro-title">
27 - <div class="container">
28 - <h2 id="intro-title">Upgrade XWiki with confidence</h2>
11 + <h1 id="hero-title">Safe XWiki LTS upgrades for production environments</h1>
29 29   <p class="lead">
30 - Agnease helps organizations upgrade XWiki instances with a focus on security, stability,
31 - compatibility, and predictable execution.
13 + Upgrade XWiki safely with a clear plan, compatibility checks and reduced production risk,
14 + even for instances with custom extensions, integrations and workflows.
32 32   </p>
33 -
34 - <p>
35 - Whether your instance is one version behind or several years outdated, an XWiki upgrade should be treated
36 - as a controlled technical operation, not a simple version change. The upgrade may affect installed
37 - extensions, custom developments, authentication, PDF export, database behavior, scripts, and the
38 - application server environment.
39 - </p>
40 -
41 - <p>
42 - The goal is to keep your platform secure, stable, maintainable, and ready for future improvements
43 - while reducing the risk of unexpected downtime or failed production upgrades.
44 - </p>
16 + <div class="hero-actions">
17 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
18 + <a class="btn btn-secondary" href="#upgrade-process">See the upgrade approach</a>
19 + </div>
45 45   </div>
46 46   </section>
47 -
48 - ## WHY UPGRADE
49 - #set ($whyUpgradeData = [{
50 - 'title': 'Security fixes',
22 + ## WHY UPGRADES MATTER
23 + #set ($upgradeReasonItems = [{
24 + 'title': 'Reduce security exposure',
51 51   'icon': 'shield',
52 - 'content': 'Older versions may miss important fixes that were introduced in later XWiki releases.'
26 + 'content': 'Staying close to supported XWiki versions helps reduce exposure to known vulnerabilities and missing fixes.',
27 + 'items': [
28 + 'Review current version exposure',
29 + 'Plan upgrade to a supported version',
30 + 'Validate security-sensitive features'
31 + ]
53 53   },{
54 - 'title': 'Stability improvements',
55 - 'icon': 'check-square-o',
56 - 'content': 'Regular upgrades reduce accumulated bugs and keep the platform easier to maintain.'
33 + 'title': 'Preserve compatibility',
34 + 'icon': 'cogs',
35 + 'content': 'Extensions, custom applications, authentication systems and infrastructure components need to remain compatible.',
36 + 'items': [
37 + 'Check installed extensions',
38 + 'Review custom code and scripts',
39 + 'Validate integrations after upgrade'
40 + ]
57 57   },{
58 - 'title': 'Compatibility',
59 - 'icon': 'plug',
60 - 'content': 'Modern integrations, authentication systems, Java versions, databases, and application servers require careful compatibility planning.'
61 - },{
62 - 'title': 'Lower future risk',
42 + 'title': 'Improve maintainability',
63 63   'icon': 'line-chart',
64 - 'content': 'Frequent smaller upgrades are usually safer and more predictable than large delayed migrations.'
44 + 'content': 'Smaller, regular upgrades are usually easier to control than large jumps after years of accumulated changes.',
45 + 'items': [
46 + 'Avoid long upgrade gaps',
47 + 'Document the current platform state',
48 + 'Prepare future upgrade cycles'
49 + ]
65 65   }])
66 -
67 67   <section aria-labelledby="why-upgrade-title">
68 68   <div class="container">
69 - <h2 id="why-upgrade-title">Why XWiki upgrades matter</h2>
70 - <p class="lead">Regular upgrades help keep your XWiki platform secure, reliable, and easier to evolve.</p>
71 -
72 - <div class="widgets">
73 - #foreach ($entry in $whyUpgradeData)
74 - <article class="widget">
75 - <div class="icon" aria-hidden="true">
76 - <i class="fa fa-$entry.icon"></i>
77 - <h4>$entry.title</h4>
53 + <h2 id="why-upgrade-title">Why regular XWiki upgrades matter</h2>
54 + <p class="section-intro">
55 + An outdated XWiki instance can become harder to maintain over time. Security fixes, browser compatibility,
56 + extension updates, platform changes and infrastructure requirements continue to evolve, while older versions
57 + become more difficult and risky to upgrade.
58 + </p>
59 + <div class="pathways">
60 + #foreach ($entry in $upgradeReasonItems)
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>
78 78   </div>
68 +
79 79   <p>$entry.content</p>
70 +
71 + <ul>
72 + #foreach ($item in $entry.items)
73 + <li>$item</li>
74 + #end
75 + </ul>
80 80   </article>
81 81   #end
82 82   </div>
83 83   </div>
84 84   </section>
85 -
86 - ## WHEN TO UPGRADE
87 - #set ($whenToUpgradeData = [{
88 - 'title': 'Your XWiki version is old',
81 + ## COMMON SITUATIONS
82 + #set ($upgradeSituationItems = [{
83 + 'title': 'Old XWiki versions',
89 89   'icon': 'clock-o',
90 - 'content': 'If your current version is more than one year old, the upgrade gap may already be significant.'
85 + 'content': 'Instances that have not been upgraded for several months or years and require a careful upgrade path.'
91 91   },{
92 - 'title': 'You are not on the latest LTS',
93 - 'icon': 'refresh',
94 - 'content': 'Production instances should normally stay close to the latest suitable Long Term Support version.'
87 + 'title': 'Custom extensions and scripts',
88 + 'icon': 'puzzle-piece',
89 + 'content': 'Wikis with custom applications, Velocity scripts, macros, UI extensions, rights logic or business workflows.'
95 95   },{
96 - 'title': 'You use custom extensions',
97 - 'icon': 'cogs',
98 - 'content': 'Custom applications, scripts, macros, UI extensions, or Java components should be reviewed before upgrading.'
91 + 'title': 'Authentication integrations',
92 + 'icon': 'lock',
93 + 'content': 'LDAP, Active Directory, SSO, OIDC, SAML, MFA or custom login setups that must keep working after upgrade.'
99 99   },{
100 - 'title': 'Authentication is critical',
101 - 'icon': 'key',
102 - 'content': 'LDAP, Active Directory, OpenID Connect, SAML, or MFA integrations need careful validation during upgrades.'
103 - },{
104 - 'title': 'Your wiki supports business processes',
105 - 'icon': 'sitemap',
106 - 'content': 'Instances used for intranets, procedures, documentation, approvals, or workflows deserve controlled upgrade planning.'
107 - },{
108 - 'title': 'You are preparing infrastructure changes',
95 + 'title': 'Infrastructure changes',
109 109   'icon': 'server',
110 - 'content': 'Java, Tomcat, Docker, database, or operating system changes can make upgrade planning more important.'
111 - }])
112 -
113 - <section class="services" aria-labelledby="when-title">
114 - <div class="container">
115 - <h2 id="when-title">When should you consider an upgrade?</h2>
116 - <p class="lead">
117 - An upgrade is recommended when your XWiki instance is becoming outdated, exposed, or harder to maintain.
118 - </p>
119 -
120 - <div class="services-grid">
121 - #foreach ($entry in $whenToUpgradeData)
122 - <article class="service">
123 - <div class="service-icon">
124 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
125 - </div>
126 - <div class="service-body">
127 - <h4>$entry.title</h4>
128 - <p>$entry.content</p>
129 - </div>
130 - </article>
131 - #end
132 - </div>
133 - </div>
134 - </section>
135 -
136 - ## WHAT AGNEASE HANDLES
137 - #set ($upgradeScopeData = [{
138 - 'title': 'Assessment & planning',
139 - 'icon': 'search',
140 - 'content': 'Review the current version, environment, extensions, customizations, and target upgrade path.',
141 - 'items': [
142 - 'Current version and environment review',
143 - 'Recommended target version',
144 - 'Release notes and compatibility analysis'
145 - ]
97 + 'content': 'Java, Tomcat, database, Docker, filesystem, reverse proxy or hosting changes required by newer versions.'
146 146   },{
147 - 'title': 'Extension & customization review',
148 - 'icon': 'puzzle-piece',
149 - 'content': 'Identify risks related to installed extensions, custom code, scripts, templates, and integrations.',
150 - 'items': [
151 - 'Installed extension review',
152 - 'Custom code impact analysis',
153 - 'Authentication and integration checks'
154 - ]
99 + 'title': 'Business-critical features',
100 + 'icon': 'file-pdf-o',
101 + 'content': 'PDF exports, dashboards, structured data, templates, permissions, notifications and workflows that need validation.'
155 155   },{
156 - 'title': 'Staging upgrade',
157 - 'icon': 'flask',
158 - 'content': 'Test the upgrade before production when a staging environment is available.',
159 - 'items': [
160 - 'Backup and restore validation',
161 - 'Upgrade execution in test environment',
162 - 'Troubleshooting and issue fixing'
163 - ]
164 - },{
165 - 'title': 'Production rollout',
166 - 'icon': 'rocket',
167 - 'content': 'Execute or guide the production upgrade with a clear plan and validation steps.',
168 - 'items': [
169 - 'Downtime and rollback planning',
170 - 'Production upgrade execution',
171 - 'Post-upgrade verification'
172 - ]
103 + 'title': 'Low-downtime rollout',
104 + 'icon': 'warning',
105 + 'content': 'Upgrade planning with backups, testing, rollback options and a controlled production deployment window.'
173 173   }])
174 -
175 - <section class="services" aria-labelledby="scope-title">
107 + <section class="services" aria-labelledby="situations-title">
176 176   <div class="container">
177 - <h2 id="scope-title">What Agnease handles</h2>
178 - <p class="lead">
179 - Upgrade support can cover the full process, from assessment to production rollout.
109 + <h2 id="situations-title">Common situations we handle</h2>
110 + <p class="section-intro">
111 + XWiki upgrades are often simple in clean environments, but production instances usually include additional
112 + constraints that need to be understood before touching the live system.
180 180   </p>
181 -
182 182   <div class="services-grid">
183 - #foreach ($entry in $upgradeScopeData)
115 + #foreach ($entry in $upgradeSituationItems)
184 184   <article class="service">
185 - <div class="service-icon">
186 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
117 + <div class="service-icon" aria-hidden="true">
118 + <i class="fa fa-$entry.icon"></i>
187 187   </div>
120 +
188 188   <div class="service-body">
189 189   <h4>$entry.title</h4>
190 190   <p>$entry.content</p>
191 - <ul>
192 - #foreach ($item in $entry.items)
193 - <li>$item</li>
194 - #end
195 - </ul>
196 196   </div>
197 197   </article>
198 198   #end
... ... @@ -199,200 +199,99 @@
199 199   </div>
200 200   </div>
201 201   </section>
202 -
203 203   ## PROCESS
204 - #set ($processData = [{
205 - 'title': '1. Initial review',
206 - 'icon': 'info-circle',
207 - 'content': 'We review your current XWiki version, hosting environment, installed extensions, customizations, authentication setup, and known issues.'
131 + #set ($upgradeProcessItems = [{
132 + 'title': 'Review the current instance',
133 + 'content': 'Version, extensions, database, filesystem, authentication, custom code, logs and infrastructure constraints.'
208 208   },{
209 - 'title': '2. Upgrade path',
210 - 'icon': 'map-signs',
211 - 'content': 'We identify the recommended target version and whether the upgrade should be direct, staged, or combined with infrastructure changes.'
135 + 'title': 'Define the upgrade path',
136 + 'content': 'Target version, intermediate steps if needed, compatibility risks, expected downtime and rollback options.'
212 212   },{
213 - 'title': '3. Compatibility checks',
214 - 'icon': 'check',
215 - 'content': 'We review release notes, extensions, custom developments, authentication integrations, PDF export, and other sensitive areas.'
138 + 'title': 'Prepare and validate',
139 + 'content': 'Backups, test upgrade when needed, extension checks and validation of critical XWiki features.'
216 216   },{
217 - 'title': '4. Backup and rollback plan',
218 - 'icon': 'database',
219 - 'content': 'Before production work, the database, permanent directory, application files, and configuration backup strategy should be clear.'
141 + 'title': 'Upgrade production',
142 + 'content': 'Controlled execution, post-upgrade checks, issue resolution and confirmation that key features still work.'
220 220   },{
221 - 'title': '5. Staging validation',
222 - 'icon': 'desktop',
223 - 'content': 'Whenever possible, the upgrade is tested in a staging environment to validate key pages, extensions, permissions, and workflows.'
224 - },{
225 - 'title': '6. Production upgrade',
226 - 'icon': 'upload',
227 - 'content': 'The production upgrade is executed according to the agreed plan, with attention to downtime, rollback options, and validation.'
144 + 'title': 'Document next steps',
145 + 'content': 'Upgrade notes, observed risks, remaining recommendations and future maintenance guidance.'
228 228   }])
229 -
230 - <section class="services" aria-labelledby="process-title">
147 + <section id="upgrade-process" class="split-section" aria-labelledby="process-title">
231 231   <div class="container">
232 - <h2 id="process-title">A structured upgrade process</h2>
233 - <p class="lead">
234 - The process is designed to reduce surprises and keep the platform operational.
235 - </p>
236 -
237 - <div class="services-grid">
238 - #foreach ($entry in $processData)
239 - <article class="service">
240 - <div class="service-icon">
241 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
242 - </div>
243 - <div class="service-body">
244 - <h4>$entry.title</h4>
245 - <p>$entry.content</p>
246 - </div>
247 - </article>
248 - #end
149 + <div class="split-grid">
150 + <div class="split-copy">
151 + <h2 id="process-title">A practical upgrade approach</h2>
152 + <p>
153 + The goal is not only to install a newer version. The goal is to move your XWiki instance forward
154 + while protecting the data, configuration, customizations and business processes that already depend on it.
155 + </p>
156 + <p>
157 + The upgrade is always prepared outside production first, using a staging environment or a temporary clone
158 + of the live instance. This allows compatibility issues, extension problems, authentication changes and
159 + custom features to be validated before the controlled production rollout.
160 + </p>
161 + </div>
162 + <ol class="process-list">
163 + #foreach ($entry in $upgradeProcessItems)
164 + <li>
165 + <strong>$entry.title</strong>
166 + $entry.content
167 + </li>
168 + #end
169 + </ol>
249 249   </div>
250 250   </div>
251 251   </section>
252 -
253 - ## COMMON SCENARIOS
254 - #set ($scenariosData = [{
255 - 'title': 'Regular LTS upgrade',
256 - 'icon': 'calendar-check-o',
257 - 'content': 'For organizations that upgrade regularly and want to stay aligned with the latest stable XWiki release line.'
173 + ## DELIVERABLES
174 + #set ($upgradeDeliverableItems = [{
175 + 'title': 'Upgrade review',
176 + 'icon': 'search',
177 + 'content': 'Review of the current version, installed extensions, customizations, authentication and hosting constraints.'
258 258   },{
259 - 'title': 'Delayed upgrade',
260 - 'icon': 'exclamation-triangle',
261 - 'content': 'For instances that have not been upgraded for one or more years and need a more careful compatibility review.'
179 + 'title': 'Upgrade plan',
180 + 'icon': 'map',
181 + 'content': 'Recommended target version, risk areas, validation checklist, downtime expectations and rollback approach.'
262 262   },{
263 - 'title': 'Major platform transition',
264 - 'icon': 'random',
265 - 'content': 'For upgrades that also involve Java, Tomcat, Docker, database, or operating system changes.'
183 + 'title': 'Post-upgrade validation',
184 + 'icon': 'check-circle',
185 + 'content': 'Verification of key pages, rights, authentication, extensions, jobs, PDFs, dashboards and custom applications.'
266 266   },{
267 - 'title': 'Custom application upgrade',
268 - 'icon': 'code',
269 - 'content': 'For XWiki instances with custom workflows, scripts, macros, PDF templates, or Java extensions.'
270 - },{
271 - 'title': 'Authentication-sensitive upgrade',
272 - 'icon': 'lock',
273 - 'content': 'For platforms using LDAP, Active Directory, OpenID Connect, SAML, MFA, or other authentication integrations.'
274 - },{
275 - 'title': 'Failed upgrade recovery',
276 - 'icon': 'ambulance',
277 - 'content': 'For organizations that already attempted an upgrade and encountered startup errors, broken extensions, or rendering issues.'
187 + 'title': 'Upgrade notes',
188 + 'icon': 'file-text-o',
189 + 'content': 'Practical documentation of the performed work, important decisions and recommended follow-up actions.'
278 278   }])
279 -
280 - <section class="services" aria-labelledby="scenarios-title">
191 + <section aria-labelledby="deliverables-title">
281 281   <div class="container">
282 - <h2 id="scenarios-title">Common upgrade scenarios</h2>
283 - <p class="lead">
284 - Agnease can help with both routine upgrades and complex migration situations.
193 + <h2 id="deliverables-title">What you can expect</h2>
194 + <p class="section-intro">
195 + The exact scope depends on your XWiki version, hosting setup and customizations, but an upgrade engagement
196 + usually includes a clear technical review, a controlled upgrade plan and post-upgrade validation.
285 285   </p>
286 -
287 - <div class="services-grid">
288 - #foreach ($entry in $scenariosData)
289 - <article class="service">
290 - <div class="service-icon">
291 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
292 - </div>
293 - <div class="service-body">
198 + <div class="widgets">
199 + #foreach ($entry in $upgradeDeliverableItems)
200 + <article class="widget">
201 + <div class="icon" aria-hidden="true">
202 + <i class="fa fa-$entry.icon"></i>
294 294   <h4>$entry.title</h4>
295 - <p>$entry.content</p>
296 296   </div>
205 + <p>$entry.content</p>
297 297   </article>
298 298   #end
299 299   </div>
300 300   </div>
301 301   </section>
302 -
303 - ## PLATFORM NOTE
304 - <section aria-labelledby="platform-title">
211 + ## CTA
212 + <section class="cta-section" aria-labelledby="cta-title">
305 305   <div class="container">
306 - <h2 id="platform-title">Major version upgrades require planning</h2>
307 - <p class="lead">
308 - Some XWiki upgrades also require infrastructure-level preparation.
309 - </p>
310 -
311 - <div class="widgets">
312 - <article class="widget">
313 - <div class="icon" aria-hidden="true">
314 - <i class="fa fa-server"></i>
315 - <h4>Application server compatibility</h4>
316 - </div>
317 - <p>
318 - Major XWiki versions may introduce changes that affect Java, Tomcat, Docker images,
319 - database drivers, or deployment configuration. These changes should be reviewed before production rollout.
320 - </p>
321 - </article>
322 -
323 - <article class="widget">
324 - <div class="icon" aria-hidden="true">
325 - <i class="fa fa-plug"></i>
326 - <h4>Extension compatibility</h4>
327 - </div>
328 - <p>
329 - Installed extensions and custom applications should be checked against the target version,
330 - especially when the instance contains business-specific workflows or integrations.
331 - </p>
332 - </article>
333 -
334 - <article class="widget">
335 - <div class="icon" aria-hidden="true">
336 - <i class="fa fa-shield"></i>
337 - <h4>Security and stability</h4>
338 - </div>
339 - <p>
340 - Staying close to the recommended LTS version helps reduce exposure to known issues and keeps
341 - the platform easier to maintain over time.
342 - </p>
343 - </article>
214 + <div class="cta-panel">
215 + <h2 id="cta-title">Planning an XWiki upgrade?</h2>
216 + <p>
217 + Send your current XWiki version, target version if known, hosting setup and any custom extensions or integrations
218 + that may affect the upgrade. A short description is enough to start with.
219 + </p>
220 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
344 344   </div>
345 345   </div>
346 346   </section>
347 -
348 - ## ASSESSMENT CTA
349 - <section class="cta-section" aria-labelledby="assessment-title">
350 - <div class="container">
351 - <h2 id="assessment-title">Request an XWiki upgrade assessment</h2>
352 - <p class="lead">
353 - Not sure how far your instance is from the recommended version?
354 - </p>
355 -
356 - <p class="text-center">
357 - Send your current XWiki version and a short description of your setup.
358 - Agnease will review the situation and provide a practical upgrade recommendation.
359 - </p>
360 -
361 - <div class="widgets">
362 - <article class="widget">
363 - <div class="icon" aria-hidden="true">
364 - <i class="fa fa-list"></i>
365 - <h4>The assessment can include</h4>
366 - </div>
367 - <p>
368 - Recommended target version, estimated upgrade effort, security and stability reasons to upgrade,
369 - infrastructure considerations, extension risks, customization risks, and suggested next steps.
370 - </p>
371 - </article>
372 - </div>
373 -
374 - <p class="text-center contact-inline">
375 - <a href="mailto:alex@agnease.com?subject=XWiki%20Upgrade%20Assessment">Request an upgrade assessment</a>
376 - </p>
377 - </div>
378 - </section>
379 -
380 - ## RELATED SERVICES
381 - <section aria-labelledby="related-title">
382 - <div class="container">
383 - <h2 id="related-title">Related Agnease services</h2>
384 - <p class="lead">
385 - XWiki upgrades are often connected to maintenance, security, development, and integration work.
386 - </p>
387 -
388 - <ul class="benefits">
389 - <li>Maintenance & support</li>
390 - <li>Security review</li>
391 - <li>Custom development</li>
392 - <li>Integrations</li>
393 - <li>Migrations</li>
394 - </ul>
395 - </div>
396 - </section>
397 397  {{/html}}
398 398  {{/velocity}}
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,0 +1,1 @@
1 +Safe XWiki upgrade services for production instances, including LTS upgrade planning, extension compatibility, backups, rollback strategy and validation.
metaTitle
... ... @@ -1,0 +1,1 @@
1 +Safe XWiki Upgrade Services for Production Instances | Agnease