Skip to Content

Changes for page XWiki Upgrade Services

Last modified by Agnease on 2026/05/25 16:11
From version 9.6
edited by Agnease
on 2026/05/25 16:11
Change comment: There is no comment for this version
To version 9.3
edited by Agnease
on 2026/05/22 14:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,18 +1,22 @@
1 1  {{velocity}}
2 2  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 3  {{html clean="false"}}
4 +
4 4   ## PAGE HEADER
5 - <section class="hero hero-centered" aria-labelledby="hero-title">
6 + <section class="hero hero-centered service-hero" aria-labelledby="hero-title">
6 6   <div class="container hero-inner">
7 7   <div class="hero-kicker">
8 8   <i class="fa fa-refresh" aria-hidden="true"></i>
9 9   XWiki upgrade services
10 10   </div>
12 +
11 11   <h1 id="hero-title">Safe XWiki LTS upgrades for production environments</h1>
14 +
12 12   <p class="lead">
13 13   Upgrade XWiki safely with a clear plan, compatibility checks and reduced production risk,
14 14   even for instances with custom extensions, integrations and workflows.
15 15   </p>
19 +
16 16   <div class="hero-actions">
17 17   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
18 18   <a class="btn btn-secondary" href="#upgrade-process">See the upgrade approach</a>
... ... @@ -19,140 +19,165 @@
19 19   </div>
20 20   </div>
21 21   </section>
26 +
22 22   ## WHY UPGRADES MATTER
23 - #set ($upgradeReasonItems = [{
24 - 'title': 'Reduce security exposure',
25 - 'icon': 'shield',
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 - ]
32 - },{
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 - ]
41 - },{
42 - 'title': 'Improve maintainability',
43 - 'icon': 'line-chart',
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 - ]
50 - }])
51 51   <section aria-labelledby="why-upgrade-title">
52 52   <div class="container">
53 53   <h2 id="why-upgrade-title">Why regular XWiki upgrades matter</h2>
31 +
54 54   <p class="section-intro">
55 55   An outdated XWiki instance can become harder to maintain over time. Security fixes, browser compatibility,
56 56   extension updates, platform changes and infrastructure requirements continue to evolve, while older versions
57 57   become more difficult and risky to upgrade.
58 58   </p>
37 +
59 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>
67 - </div>
39 + <article class="pathway-card">
40 + <div class="pathway-icon">
41 + <i class="fa fa-shield" aria-hidden="true"></i>
42 + </div>
43 + <h3>Reduce security exposure</h3>
44 + <p>
45 + Staying close to supported XWiki versions helps reduce exposure to known vulnerabilities and missing fixes.
46 + </p>
47 + <ul>
48 + <li>Review current version exposure</li>
49 + <li>Plan upgrade to a supported version</li>
50 + <li>Validate security-sensitive features</li>
51 + </ul>
52 + </article>
68 68  
69 - <p>$entry.content</p>
54 + <article class="pathway-card">
55 + <div class="pathway-icon">
56 + <i class="fa fa-cogs" aria-hidden="true"></i>
57 + </div>
58 + <h3>Preserve compatibility</h3>
59 + <p>
60 + Extensions, custom applications, authentication systems and infrastructure components need to remain compatible.
61 + </p>
62 + <ul>
63 + <li>Check installed extensions</li>
64 + <li>Review custom code and scripts</li>
65 + <li>Validate integrations after upgrade</li>
66 + </ul>
67 + </article>
70 70  
71 - <ul>
72 - #foreach ($item in $entry.items)
73 - <li>$item</li>
74 - #end
75 - </ul>
76 - </article>
77 - #end
69 + <article class="pathway-card">
70 + <div class="pathway-icon">
71 + <i class="fa fa-line-chart" aria-hidden="true"></i>
72 + </div>
73 + <h3>Improve maintainability</h3>
74 + <p>
75 + Smaller, regular upgrades are usually easier to control than large jumps after years of accumulated changes.
76 + </p>
77 + <ul>
78 + <li>Avoid long upgrade gaps</li>
79 + <li>Document the current platform state</li>
80 + <li>Prepare future upgrade cycles</li>
81 + </ul>
82 + </article>
78 78   </div>
79 79   </div>
80 80   </section>
86 +
81 81   ## COMMON SITUATIONS
82 - #set ($upgradeSituationItems = [{
83 - 'title': 'Old XWiki versions',
84 - 'icon': 'clock-o',
85 - 'content': 'Instances that have not been upgraded for several months or years and require a careful upgrade path.'
86 - },{
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.'
90 - },{
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.'
94 - },{
95 - 'title': 'Infrastructure changes',
96 - 'icon': 'server',
97 - 'content': 'Java, Tomcat, database, Docker, filesystem, reverse proxy or hosting changes required by newer versions.'
98 - },{
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.'
102 - },{
103 - 'title': 'Low-downtime rollout',
104 - 'icon': 'warning',
105 - 'content': 'Upgrade planning with backups, testing, rollback options and a controlled production deployment window.'
106 - }])
107 107   <section class="services" aria-labelledby="situations-title">
108 108   <div class="container">
109 109   <h2 id="situations-title">Common situations we handle</h2>
91 +
110 110   <p class="section-intro">
111 111   XWiki upgrades are often simple in clean environments, but production instances usually include additional
112 112   constraints that need to be understood before touching the live system.
113 113   </p>
96 +
114 114   <div class="services-grid">
115 - #foreach ($entry in $upgradeSituationItems)
116 - <article class="service">
117 - <div class="service-icon" aria-hidden="true">
118 - <i class="fa fa-$entry.icon"></i>
119 - </div>
98 + <article class="service">
99 + <div class="service-icon" aria-hidden="true">
100 + <i class="fa fa-clock-o"></i>
101 + </div>
102 + <div class="service-body">
103 + <h4>Old XWiki versions</h4>
104 + <p>
105 + Instances that have not been upgraded for several months or years and require a careful upgrade path.
106 + </p>
107 + </div>
108 + </article>
120 120  
121 - <div class="service-body">
122 - <h4>$entry.title</h4>
123 - <p>$entry.content</p>
124 - </div>
125 - </article>
126 - #end
110 + <article class="service">
111 + <div class="service-icon" aria-hidden="true">
112 + <i class="fa fa-puzzle-piece"></i>
113 + </div>
114 + <div class="service-body">
115 + <h4>Custom extensions and scripts</h4>
116 + <p>
117 + Wikis with custom applications, Velocity scripts, macros, UI extensions, rights logic or business workflows.
118 + </p>
119 + </div>
120 + </article>
121 +
122 + <article class="service">
123 + <div class="service-icon" aria-hidden="true">
124 + <i class="fa fa-lock"></i>
125 + </div>
126 + <div class="service-body">
127 + <h4>Authentication integrations</h4>
128 + <p>
129 + LDAP, Active Directory, SSO, OIDC, SAML, MFA or custom login setups that must keep working after upgrade.
130 + </p>
131 + </div>
132 + </article>
133 +
134 + <article class="service">
135 + <div class="service-icon" aria-hidden="true">
136 + <i class="fa fa-server"></i>
137 + </div>
138 + <div class="service-body">
139 + <h4>Infrastructure changes</h4>
140 + <p>
141 + Java, Tomcat, database, Docker, filesystem, reverse proxy or hosting changes required by newer versions.
142 + </p>
143 + </div>
144 + </article>
145 +
146 + <article class="service">
147 + <div class="service-icon" aria-hidden="true">
148 + <i class="fa fa-file-pdf-o"></i>
149 + </div>
150 + <div class="service-body">
151 + <h4>Business-critical features</h4>
152 + <p>
153 + PDF exports, dashboards, structured data, templates, permissions, notifications and workflows that need validation.
154 + </p>
155 + </div>
156 + </article>
157 +
158 + <article class="service">
159 + <div class="service-icon" aria-hidden="true">
160 + <i class="fa fa-warning"></i>
161 + </div>
162 + <div class="service-body">
163 + <h4>Low-downtime rollout</h4>
164 + <p>
165 + Upgrade planning with backups, testing, rollback options and a controlled production deployment window.
166 + </p>
167 + </div>
168 + </article>
127 127   </div>
128 128   </div>
129 129   </section>
172 +
130 130   ## PROCESS
131 - #set ($upgradeProcessItems = [{
132 - 'title': 'Review the current instance',
133 - 'content': 'Version, extensions, database, filesystem, authentication, custom code, logs and infrastructure constraints.'
134 - },{
135 - 'title': 'Define the upgrade path',
136 - 'content': 'Target version, intermediate steps if needed, compatibility risks, expected downtime and rollback options.'
137 - },{
138 - 'title': 'Prepare and validate',
139 - 'content': 'Backups, test upgrade when needed, extension checks and validation of critical XWiki features.'
140 - },{
141 - 'title': 'Upgrade production',
142 - 'content': 'Controlled execution, post-upgrade checks, issue resolution and confirmation that key features still work.'
143 - },{
144 - 'title': 'Document next steps',
145 - 'content': 'Upgrade notes, observed risks, remaining recommendations and future maintenance guidance.'
146 - }])
147 147   <section id="upgrade-process" class="split-section" aria-labelledby="process-title">
148 148   <div class="container">
149 149   <div class="split-grid">
150 150   <div class="split-copy">
151 151   <h2 id="process-title">A practical upgrade approach</h2>
179 +
152 152   <p>
153 153   The goal is not only to install a newer version. The goal is to move your XWiki instance forward
154 154   while protecting the data, configuration, customizations and business processes that already depend on it.
155 155   </p>
184 +
156 156   <p>
157 157   The upgrade is always prepared outside production first, using a staging environment or a temporary clone
158 158   of the live instance. This allows compatibility issues, extension problems, authentication changes and
... ... @@ -159,67 +159,102 @@
159 159   custom features to be validated before the controlled production rollout.
160 160   </p>
161 161   </div>
191 +
162 162   <ol class="process-list">
163 - #foreach ($entry in $upgradeProcessItems)
164 - <li>
165 - <strong>$entry.title</strong>
166 - $entry.content
167 - </li>
168 - #end
193 + <li>
194 + <strong>Review the current instance</strong>
195 + Version, extensions, database, filesystem, authentication, custom code, logs and infrastructure constraints.
196 + </li>
197 + <li>
198 + <strong>Define the upgrade path</strong>
199 + Target version, intermediate steps if needed, compatibility risks, expected downtime and rollback options.
200 + </li>
201 + <li>
202 + <strong>Prepare and validate</strong>
203 + Backups, test upgrade when needed, extension checks and validation of critical XWiki features.
204 + </li>
205 + <li>
206 + <strong>Upgrade production</strong>
207 + Controlled execution, post-upgrade checks, issue resolution and confirmation that key features still work.
208 + </li>
209 + <li>
210 + <strong>Document next steps</strong>
211 + Upgrade notes, observed risks, remaining recommendations and future maintenance guidance.
212 + </li>
169 169   </ol>
170 170   </div>
171 171   </div>
172 172   </section>
217 +
173 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.'
178 - },{
179 - 'title': 'Upgrade plan',
180 - 'icon': 'map',
181 - 'content': 'Recommended target version, risk areas, validation checklist, downtime expectations and rollback approach.'
182 - },{
183 - 'title': 'Post-upgrade validation',
184 - 'icon': 'check-circle',
185 - 'content': 'Verification of key pages, rights, authentication, extensions, jobs, PDFs, dashboards and custom applications.'
186 - },{
187 - 'title': 'Upgrade notes',
188 - 'icon': 'file-text-o',
189 - 'content': 'Practical documentation of the performed work, important decisions and recommended follow-up actions.'
190 - }])
191 191   <section aria-labelledby="deliverables-title">
192 192   <div class="container">
193 193   <h2 id="deliverables-title">What you can expect</h2>
222 +
194 194   <p class="section-intro">
195 195   The exact scope depends on your XWiki version, hosting setup and customizations, but an upgrade engagement
196 196   usually includes a clear technical review, a controlled upgrade plan and post-upgrade validation.
197 197   </p>
227 +
198 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>
203 - <h4>$entry.title</h4>
204 - </div>
205 - <p>$entry.content</p>
206 - </article>
207 - #end
229 + <article class="widget">
230 + <div class="icon" aria-hidden="true">
231 + <i class="fa fa-search"></i>
232 + <h4>Upgrade review</h4>
233 + </div>
234 + <p>
235 + Review of the current version, installed extensions, customizations, authentication and hosting constraints.
236 + </p>
237 + </article>
238 +
239 + <article class="widget">
240 + <div class="icon" aria-hidden="true">
241 + <i class="fa fa-map"></i>
242 + <h4>Upgrade plan</h4>
243 + </div>
244 + <p>
245 + Recommended target version, risk areas, validation checklist, downtime expectations and rollback approach.
246 + </p>
247 + </article>
248 +
249 + <article class="widget">
250 + <div class="icon" aria-hidden="true">
251 + <i class="fa fa-check-circle"></i>
252 + <h4>Post-upgrade validation</h4>
253 + </div>
254 + <p>
255 + Verification of key pages, rights, authentication, extensions, jobs, PDFs, dashboards and custom applications.
256 + </p>
257 + </article>
258 +
259 + <article class="widget">
260 + <div class="icon" aria-hidden="true">
261 + <i class="fa fa-file-text-o"></i>
262 + <h4>Upgrade notes</h4>
263 + </div>
264 + <p>
265 + Practical documentation of the performed work, important decisions and recommended follow-up actions.
266 + </p>
267 + </article>
208 208   </div>
209 209   </div>
210 210   </section>
271 +
211 211   ## CTA
212 212   <section class="cta-section" aria-labelledby="cta-title">
213 213   <div class="container">
214 214   <div class="cta-panel">
215 215   <h2 id="cta-title">Planning an XWiki upgrade?</h2>
277 +
216 216   <p>
217 217   Send your current XWiki version, target version if known, hosting setup and any custom extensions or integrations
218 218   that may affect the upgrade. A short description is enough to start with.
219 219   </p>
282 +
220 220   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
221 221   </div>
222 222   </div>
223 223   </section>
287 +
224 224  {{/html}}
225 225  {{/velocity}}