Skip to Content

Wiki source code of XWiki Upgrade Services

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