Skip to Content
Last modified by Agnease on 2026/07/03 12:22
From version 1.1
edited by Agnease
on 2026/07/03 11:08
Change comment: There is no comment for this version
To version 4.8
edited by Agnease
on 2026/07/03 12:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,0 +1,772 @@
1 +{{velocity}}
2 +#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 +
4 +#set ($summaryCards = [{
5 + 'icon': 'book',
6 + 'title': 'Use XWiki for trusted knowledge',
7 + 'content': 'Move official documentation, policies, procedures, decisions, meeting outcomes, working group spaces and maintained knowledge into XWiki.'
8 +},{
9 + 'icon': 'pencil',
10 + 'title': 'Keep specialist tools where needed',
11 + 'content': 'Do not force XWiki to replace email, calendar, video calls, chat, desktop file sync, complex spreadsheets or presentation editing.'
12 +},{
13 + 'icon': 'road',
14 + 'title': 'Transition gradually',
15 + 'content': 'Start with one useful pilot space, define templates and ownership rules, then expand once users see XWiki as the trusted source.'
16 +}])
17 +
18 +#set ($xwikiFitCards = [{
19 + 'icon': 'sitemap',
20 + 'title': 'Structured knowledge spaces',
21 + 'content': 'Create clear spaces for teams, working groups, committees, projects, departments or public documentation areas.'
22 +},{
23 + 'icon': 'file-text-o',
24 + 'title': 'Official pages and procedures',
25 + 'content': 'Turn important documents into maintained wiki pages with history, ownership, review dates and clear navigation.'
26 +},{
27 + 'icon': 'check-square-o',
28 + 'title': 'Decision records',
29 + 'content': 'Capture decisions separately from chats, meetings and drafts so users can understand why something was agreed later.'
30 +},{
31 + 'icon': 'users',
32 + 'title': 'Working group collaboration',
33 + 'content': 'Provide each group with a homepage, meeting notes, decisions, files, responsibilities and links to external tools.'
34 +},{
35 + 'icon': 'database',
36 + 'title': 'Lightweight structured apps',
37 + 'content': 'Replace some spreadsheet-based lists with XWiki applications when the data has stable fields, owners and lifecycle rules.'
38 +},{
39 + 'icon': 'shield',
40 + 'title': 'Governed access',
41 + 'content': 'Use XWiki groups, rights and page hierarchy to create a more explicit model for internal, restricted and public knowledge.'
42 +}])
43 +
44 +#set ($notXWikiCards = [{
45 + 'icon': 'envelope-o',
46 + 'title': 'Email and calendar',
47 + 'content': 'XWiki is not a mail or scheduling platform. Keep the existing groupware or evaluate tools such as Nextcloud Groupware for calendar and contacts.'
48 +},{
49 + 'icon': 'comments-o',
50 + 'title': 'Real-time chat',
51 + 'content': 'XWiki comments and notifications do not replace chat. Use Matrix/Element, Mattermost, Nextcloud Talk or another dedicated messaging tool.'
52 +},{
53 + 'icon': 'video-camera',
54 + 'title': 'Video meetings',
55 + 'content': 'XWiki can store agendas and notes, but it should not host meetings. Use Jitsi, Nextcloud Talk or another video conferencing solution.'
56 +},{
57 + 'icon': 'cloud',
58 + 'title': 'Large file sync',
59 + 'content': 'XWiki attachments are useful around pages, but XWiki is not a desktop file synchronization platform. Use Nextcloud Files for that role.'
60 +},{
61 + 'icon': 'table',
62 + 'title': 'Complex spreadsheets',
63 + 'content': 'Budgets, calculations, pivot tables and reporting workbooks should remain in office tools such as LibreOffice, ONLYOFFICE or Collabora.'
64 +},{
65 + 'icon': 'desktop',
66 + 'title': 'Presentation editing',
67 + 'content': 'XWiki can store final decks and document the reusable knowledge behind them, but presentation authoring belongs in an office suite.'
68 +}])
69 +
70 +#set ($roadmapSteps = [{
71 + 'title': '1. Define the role of XWiki',
72 + 'content': 'Agree that XWiki is the trusted knowledge and governance layer, not a clone of Google Workspace.'
73 +},{
74 + 'title': '2. Select high-value content',
75 + 'content': 'Start with policies, procedures, decisions, working group documents, onboarding guides and maintained knowledge.'
76 +},{
77 + 'title': '3. Create templates',
78 + 'content': 'Prepare templates for working group homepages, meeting notes, decision records, policies, procedures and FAQs.'
79 +},{
80 + 'title': '4. Design permissions',
81 + 'content': 'Define public, internal, restricted and external collaboration areas before migrating content.'
82 +},{
83 + 'title': '5. Reduce login friction',
84 + 'content': 'Connect XWiki to the organization identity provider through OIDC, SAML, LDAP or another SSO approach.'
85 +},{
86 + 'title': '6. Migrate into structure',
87 + 'content': 'Do not only copy files. Give each page an owner, location, purpose, access model and review expectation.'
88 +},{
89 + 'title': '7. Expand after a pilot',
90 + 'content': 'Start with one working group or department, collect feedback, improve the structure, then repeat with more teams.'
91 +}])
92 +
93 +#set ($pilotCards = [{
94 + 'icon': 'home',
95 + 'title': 'Working group homepage',
96 + 'content': 'Purpose, scope, members, priorities, important links and current responsibilities.'
97 +},{
98 + 'icon': 'calendar',
99 + 'title': 'Meeting notes',
100 + 'content': 'Consistent notes with agenda, participants, decisions, actions and links to related pages.'
101 +},{
102 + 'icon': 'check',
103 + 'title': 'Decisions',
104 + 'content': 'Short decision records with context, options considered, decision, owner and date.'
105 +},{
106 + 'icon': 'folder-open-o',
107 + 'title': 'Documents and files',
108 + 'content': 'Important documents converted to pages when possible, with attachments or external links where needed.'
109 +},{
110 + 'icon': 'question-circle',
111 + 'title': 'Open questions',
112 + 'content': 'A visible place for unresolved topics instead of hiding them in chat or email.'
113 +},{
114 + 'icon': 'link',
115 + 'title': 'External tool links',
116 + 'content': 'Clear bridges to Drive, Nextcloud, office editors, issue trackers, chat or other tools still in use.'
117 +}])
118 +
119 +#set ($implementationItems = [
120 + 'Single sign-on with OIDC, SAML, LDAP or another identity provider.',
121 + 'A simple space model for departments, working groups, projects and public documentation.',
122 + 'Page templates for recurring content types such as meeting notes, decisions, policies and procedures.',
123 + 'Metadata fields such as owner, status, review date, audience and document type.',
124 + 'Clear group and permission model for public, internal, restricted and external collaboration areas.',
125 + 'Notifications and watch rules so users know when important pages change.',
126 + 'Structured applications for lists, registers and lightweight internal processes.',
127 + 'Optional office document integration when page-based content is not enough.',
128 + 'A migration dashboard showing selected content, owners, status and unresolved questions.'
129 +])
130 +
131 +{{html clean="false"}}
132 +
133 + <section class="resource-header" aria-labelledby="hero-title">
134 + <div class="container">
135 + <div class="text-center">
136 + <div class="hero-kicker">
137 + <i class="fa fa-exchange" aria-hidden="true"></i>
138 + XWiki migration and collaboration guidance
139 + </div>
140 + </div>
141 +
142 + <h1 id="hero-title">From Google Workspace to XWiki: a practical transition guide</h1>
143 +
144 + <p class="resource-summary">
145 + A practical guide for moving durable knowledge, documentation and governance from Google Workspace
146 + into XWiki, while keeping the right tools for files, meetings, chat, office editing and communication.
147 + </p>
148 + </div>
149 + </section>
150 +
151 + <section class="resource-page">
152 + <div class="container">
153 + <div class="resource-layout">
154 +
155 + <aside class="resource-sidebar" aria-label="Page summary">
156 + <h4>In this guide</h4>
157 + <ul>
158 + <li><a href="#main-idea">Main idea</a></li>
159 + <li><a href="#quick-view">Quick view</a></li>
160 + <li><a href="#workspace-map">Google Workspace map</a></li>
161 + <li><a href="#replacement-map">Replacement map</a></li>
162 + <li><a href="#what-belongs-in-xwiki">What belongs in XWiki</a></li>
163 + <li><a href="#not-xwiki">What not to replace</a></li>
164 + <li><a href="#open-source-stack">Open-source stack</a></li>
165 + <li><a href="#transition-plan">Transition plan</a></li>
166 + <li><a href="#pilot">Pilot example</a></li>
167 + <li><a href="#adoption">Adoption guidance</a></li>
168 + <li><a href="#implementation">Implementation checklist</a></li>
169 + <li><a href="#related-resources">Related resources</a></li>
170 + <li><a href="#faq">FAQ</a></li>
171 + </ul>
172 + </aside>
173 +
174 + <article class="resource-content services">
175 +
176 + <p>
177 + Moving an organization away from <a href="https://workspace.google.com/" target="_blank" rel="noopener">Google Workspace</a>
178 + is rarely just a software migration. It changes habits, ownership, permissions, document lifecycle and the
179 + way people expect collaboration to happen.
180 + </p>
181 +
182 + <p>
183 + Google Workspace is popular because it combines documents, files, email, calendar, meetings, chat, forms,
184 + sharing and search in one familiar environment. A transition to XWiki should therefore avoid the weak argument
185 + that XWiki can replace everything. It cannot, and it should not try to.
186 + </p>
187 +
188 + <div class="resource-note">
189 + <p>
190 + <strong>The practical position:</strong> XWiki is strongest as the structured knowledge layer. It is the place
191 + for official documentation, maintained knowledge, working group spaces, policies, procedures, decisions,
192 + governance content and organizational memory.
193 + </p>
194 + </div>
195 +
196 + <h2 id="main-idea">The main idea: replace the knowledge problem, not the entire suite</h2>
197 +
198 + <p>
199 + The strongest argument for XWiki is not that it imitates Google Workspace. The strongest argument is that it
200 + solves a problem that often appears inside Google Workspace over time: scattered documents, unclear ownership,
201 + duplicated files, weak navigation, old links, inconsistent permissions and no obvious place for the trusted
202 + version of important knowledge.
203 + </p>
204 +
205 + <div class="resource-note">
206 + <p>
207 + <strong>Summary recommendation:</strong> use XWiki as the trusted knowledge and governance layer. Move official
208 + documentation, procedures, decisions, policies, meeting outcomes and maintained knowledge into XWiki. Keep
209 + real-time office editing, email, calendar, chat, video meetings and large file sync in dedicated tools that
210 + can integrate with or link back to XWiki.
211 + </p>
212 + </div>
213 + <div class="resource-inline-cta">
214 + <p>
215 + <strong>Need help positioning the transition?</strong>
216 + Agnease can help map current Google Workspace usage, identify what should move to XWiki,
217 + define the right open-source alternatives, and prepare a realistic pilot migration.
218 + </p>
219 + <a class="btn btn-secondary" href="$xwiki.getURL('contact.WebHome')">Request a customization review</a>
220 + </div>
221 +
222 + <h2 id="quick-view">Quick view: how to position the transition</h2>
223 +
224 + <div class="services-grid">
225 + #foreach ($entry in $summaryCards)
226 + <article class="service">
227 + <div class="service-icon" aria-hidden="true">
228 + <i class="fa fa-$entry.icon"></i>
229 + </div>
230 + <div class="service-body">
231 + <h4>$entry.title</h4>
232 + <p>$entry.content</p>
233 + </div>
234 + </article>
235 + #end
236 + </div>
237 +
238 + <h2 id="workspace-map">What Google Workspace usually provides</h2>
239 +
240 + <p>
241 + Before proposing a transition, it is useful to explain what people currently get from Google Workspace.
242 + Users are not only using a document editor. They are using a complete collaboration habit.
243 + </p>
244 +
245 + <table class="table table-bordered table-striped">
246 + <thead>
247 + <tr>
248 + <th>Google Workspace area</th>
249 + <th>What users value</th>
250 + <th>Risk over time</th>
251 + </tr>
252 + </thead>
253 + <tbody>
254 + <tr>
255 + <td>Google Docs</td>
256 + <td>Fast writing, real-time editing, comments and suggestions.</td>
257 + <td>Important documents become isolated files instead of maintained knowledge.</td>
258 + </tr>
259 + <tr>
260 + <td>Google Drive</td>
261 + <td>Easy sharing, folders, file ownership and external collaboration.</td>
262 + <td>Folder structures grow organically and become hard to govern.</td>
263 + </tr>
264 + <tr>
265 + <td>Google Sheets</td>
266 + <td>Trackers, lists, budgets, lightweight databases and reports.</td>
267 + <td>Business processes become hidden in spreadsheets.</td>
268 + </tr>
269 + <tr>
270 + <td>Google Slides</td>
271 + <td>Presentation creation and sharing.</td>
272 + <td>Reusable knowledge remains locked in slide decks.</td>
273 + </tr>
274 + <tr>
275 + <td>Google Forms</td>
276 + <td>Quick surveys, registrations and data collection.</td>
277 + <td>Collected data may remain detached from internal processes.</td>
278 + </tr>
279 + <tr>
280 + <td>Google Sites</td>
281 + <td>Simple internal or public pages.</td>
282 + <td>Content can be separated from the wider knowledge base.</td>
283 + </tr>
284 + <tr>
285 + <td>Gmail, Calendar, Meet and Chat</td>
286 + <td>Communication, scheduling, meetings and quick coordination.</td>
287 + <td>Decisions remain scattered in messages, calls and informal conversations.</td>
288 + </tr>
289 + </tbody>
290 + </table>
291 +
292 + <h2 id="replacement-map">What can move to XWiki, and what should move elsewhere</h2>
293 +
294 + <p>
295 + A successful transition separates content by purpose. Some content belongs naturally in XWiki. Some should
296 + remain in office collaboration tools. Some should move to other open-source or self-hostable systems that
297 + complement XWiki.
298 + </p>
299 +
300 + <table class="table table-bordered table-striped">
301 + <thead>
302 + <tr>
303 + <th>Current Google Workspace usage</th>
304 + <th>Recommended destination</th>
305 + <th>Transition guidance</th>
306 + </tr>
307 + </thead>
308 + <tbody>
309 + <tr>
310 + <td>Official documentation in Google Docs</td>
311 + <td>XWiki pages, spaces, page history, comments and permissions.</td>
312 + <td>Move final and maintained documentation into XWiki pages.</td>
313 + </tr>
314 + <tr>
315 + <td>Policies, procedures and governance documents</td>
316 + <td>XWiki pages with templates, metadata, review dates and ownership.</td>
317 + <td>Move to XWiki and add lifecycle rules.</td>
318 + </tr>
319 + <tr>
320 + <td>Meeting notes</td>
321 + <td>XWiki meeting note templates inside team or working group spaces.</td>
322 + <td>Start new meeting notes in XWiki and link older notes only when useful.</td>
323 + </tr>
324 + <tr>
325 + <td>Working group or committee documents</td>
326 + <td>XWiki spaces with homepage, members, notes, decisions and documents.</td>
327 + <td>Create one structured space per group.</td>
328 + </tr>
329 + <tr>
330 + <td>Decision records</td>
331 + <td>XWiki decision page template.</td>
332 + <td>Move decisions out of scattered Docs, email and chat.</td>
333 + </tr>
334 + <tr>
335 + <td>Google Sites pages</td>
336 + <td>XWiki public or private spaces.</td>
337 + <td>Move informational pages that need history, permissions or governance.</td>
338 + </tr>
339 + <tr>
340 + <td>Shared file archive</td>
341 + <td>XWiki attachments for curated files; <a href="https://nextcloud.com/files/" target="_blank" rel="noopener">Nextcloud Files</a> for general file sharing.</td>
342 + <td>Use XWiki for files attached to knowledge pages, not for massive file sync.</td>
343 + </tr>
344 + <tr>
345 + <td>Simple trackers in Google Sheets</td>
346 + <td>XWiki structured applications, <a href="https://extensions.xwiki.org/xwiki/bin/view/Extension/App%20Within%20Minutes%20Application" target="_blank" rel="noopener">App Within Minutes</a> or custom XWiki apps.</td>
347 + <td>Move recurring lists with stable fields and clear ownership.</td>
348 + </tr>
349 + <tr>
350 + <td>Collaborative drafting in Google Docs</td>
351 + <td>XWiki pages for final content; <a href="https://www.onlyoffice.com/docs" target="_blank" rel="noopener">ONLYOFFICE Docs</a> or <a href="https://www.collaboraonline.com/" target="_blank" rel="noopener">Collabora Online</a> for office editing.</td>
352 + <td>Use XWiki for the maintained version, not every draft.</td>
353 + </tr>
354 + <tr>
355 + <td>Forms and surveys</td>
356 + <td>XWiki forms for internal processes; <a href="https://www.limesurvey.org/" target="_blank" rel="noopener">LimeSurvey</a> for advanced surveys.</td>
357 + <td>Use the right tool depending on whether it is workflow data or survey data.</td>
358 + </tr>
359 + </tbody>
360 + </table>
361 +
362 + <h2 id="what-belongs-in-xwiki">What belongs naturally in XWiki</h2>
363 +
364 + <p>
365 + XWiki is a strong destination for information that should be easy to find, maintain, discuss, review and trust
366 + over time.
367 + </p>
368 +
369 + <div class="services-grid">
370 + #foreach ($entry in $xwikiFitCards)
371 + <article class="service">
372 + <div class="service-icon" aria-hidden="true">
373 + <i class="fa fa-$entry.icon"></i>
374 + </div>
375 + <div class="service-body">
376 + <h4>$entry.title</h4>
377 + <p>$entry.content</p>
378 + </div>
379 + </article>
380 + #end
381 + </div>
382 +
383 + <h2 id="not-xwiki">What should not be replaced by XWiki</h2>
384 +
385 + <p>
386 + A credible transition guide should clearly explain where XWiki is not the right tool. This avoids unrealistic
387 + expectations and helps the organization design a better collaboration stack.
388 + </p>
389 +
390 + <div class="services-grid">
391 + #foreach ($entry in $notXWikiCards)
392 + <article class="service">
393 + <div class="service-icon" aria-hidden="true">
394 + <i class="fa fa-$entry.icon"></i>
395 + </div>
396 + <div class="service-body">
397 + <h4>$entry.title</h4>
398 + <p>$entry.content</p>
399 + </div>
400 + </article>
401 + #end
402 + </div>
403 +
404 + <div class="resource-note">
405 + <p>
406 + <strong>In practice:</strong> the goal is not to make XWiki do everything. The goal is to make XWiki the
407 + trusted home for maintained knowledge, while integrating or linking to the right tools for files, office
408 + editing, chat, meetings and identity.
409 + </p>
410 + </div>
411 +
412 + <h2 id="open-source-stack">Open-source alternatives that can complement XWiki</h2>
413 +
414 + <p>
415 + For organizations trying to reduce dependency on Google Workspace, XWiki can become part of a broader
416 + open-source collaboration architecture. The exact stack depends on hosting preferences, support needs,
417 + security requirements and user expectations.
418 + </p>
419 +
420 + <table class="table table-bordered table-striped">
421 + <thead>
422 + <tr>
423 + <th>Need</th>
424 + <th>Possible solution</th>
425 + <th>How it works with XWiki</th>
426 + </tr>
427 + </thead>
428 + <tbody>
429 + <tr>
430 + <td>Structured knowledge base</td>
431 + <td><a href="https://www.xwiki.org/" target="_blank" rel="noopener">XWiki</a></td>
432 + <td>Main platform for documentation, governance, knowledge management and structured content.</td>
433 + </tr>
434 + <tr>
435 + <td>File sync and sharing</td>
436 + <td><a href="https://nextcloud.com/files/" target="_blank" rel="noopener">Nextcloud Files</a></td>
437 + <td>Use for general file storage and sharing; link important files from XWiki pages.</td>
438 + </tr>
439 + <tr>
440 + <td>Office document editing</td>
441 + <td><a href="https://www.onlyoffice.com/docs" target="_blank" rel="noopener">ONLYOFFICE Docs</a> or <a href="https://www.collaboraonline.com/" target="_blank" rel="noopener">Collabora Online</a></td>
442 + <td>Use for documents, spreadsheets and presentations that need office-style editing.</td>
443 + </tr>
444 + <tr>
445 + <td>Chat and team messaging</td>
446 + <td><a href="https://element.io/" target="_blank" rel="noopener">Matrix/Element</a> or <a href="https://mattermost.com/" target="_blank" rel="noopener">Mattermost</a></td>
447 + <td>Use for real-time conversation; move durable decisions and outcomes back into XWiki.</td>
448 + </tr>
449 + <tr>
450 + <td>Video meetings</td>
451 + <td><a href="https://jitsi.org/" target="_blank" rel="noopener">Jitsi</a> or <a href="https://nextcloud.com/talk/" target="_blank" rel="noopener">Nextcloud Talk</a></td>
452 + <td>Use for calls; store agendas, notes and decisions in XWiki.</td>
453 + </tr>
454 + <tr>
455 + <td>Surveys and advanced forms</td>
456 + <td><a href="https://www.limesurvey.org/" target="_blank" rel="noopener">LimeSurvey</a></td>
457 + <td>Use for survey campaigns; publish results, summaries or procedures in XWiki.</td>
458 + </tr>
459 + <tr>
460 + <td>Identity and SSO</td>
461 + <td><a href="https://www.keycloak.org/" target="_blank" rel="noopener">Keycloak</a>, Microsoft Entra ID, Google identity or another OIDC/SAML provider.</td>
462 + <td>Use SSO so users access XWiki without a separate password and with mapped groups where appropriate.</td>
463 + </tr>
464 + </tbody>
465 + </table>
466 +
467 + <h2 id="transition-plan">A practical transition plan</h2>
468 +
469 + <p>
470 + The safest transition is gradual. The organization should not begin by migrating every Google Drive folder.
471 + That approach creates too much noise, too many permission questions and too many low-value documents.
472 + </p>
473 +
474 + <ol class="process-list">
475 + #foreach ($entry in $roadmapSteps)
476 + <li>
477 + <strong>$entry.title</strong>
478 + $entry.content
479 + </li>
480 + #end
481 + </ol>
482 +
483 + <h2 id="pilot">A good pilot: one working group space</h2>
484 +
485 + <p>
486 + A strong pilot is small enough to control but useful enough to prove value. For example, one working group,
487 + committee, project team or community group can move its durable knowledge into XWiki while keeping office
488 + tools for drafting, spreadsheets and presentations when needed.
489 + </p>
490 +
491 + <div class="services-grid">
492 + #foreach ($entry in $pilotCards)
493 + <article class="service">
494 + <div class="service-icon" aria-hidden="true">
495 + <i class="fa fa-$entry.icon"></i>
496 + </div>
497 + <div class="service-body">
498 + <h4>$entry.title</h4>
499 + <p>$entry.content</p>
500 + </div>
501 + </article>
502 + #end
503 + </div>
504 +
505 + <div class="resource-note">
506 + <p>
507 + <strong>Pilot success question:</strong> can members find the current and trusted version of important
508 + information faster than before?
509 + </p>
510 + </div>
511 +
512 + <h2 id="adoption">How to convince the team to use XWiki</h2>
513 +
514 + <p>
515 + People do not usually change collaboration habits because a new platform exists. They change when the new
516 + platform makes an important part of their work easier, clearer or more reliable.
517 + </p>
518 +
519 + <p>
520 + A useful adoption message is:
521 + </p>
522 +
523 + <div class="resource-note">
524 + <p>
525 + <strong>XWiki is not another folder where files disappear. It is the place where the organization keeps
526 + the current version, the owner, the context, the decision and the links around important knowledge.</strong>
527 + </p>
528 + </div>
529 +
530 + <p>
531 + Simple rules help adoption more than abstract platform arguments:
532 + </p>
533 +
534 + <ul class="resource-checklist">
535 + <li>If it is official, maintained or reusable, it belongs in XWiki.</li>
536 + <li>If it is a temporary draft, it can stay in an office editor until it becomes useful knowledge.</li>
537 + <li>If it is a complex spreadsheet, do not force it into XWiki.</li>
538 + <li>If it was decided in a meeting or chat, summarize the decision in XWiki.</li>
539 + <li>If nobody owns it, do not migrate it as current content.</li>
540 + <li>If users need the same answer repeatedly, create or improve an XWiki page.</li>
541 + </ul>
542 +
543 + <h2 id="implementation">Practical XWiki features to implement early</h2>
544 +
545 + <p>
546 + The following improvements can make the transition easier to accept and easier to govern.
547 + </p>
548 +
549 + <ul class="resource-checklist">
550 + #foreach ($item in $implementationItems)
551 + <li>$item</li>
552 + #end
553 + </ul>
554 +
555 + <h2>Example transition scenarios</h2>
556 +
557 + <h3>Scenario 1: Working group documentation</h3>
558 + <p>
559 + A working group has Google Docs for agendas, meeting notes, decisions and reference files. In XWiki, this can
560 + become a structured space with a homepage, meeting note template, decision records, document list, open
561 + questions and links to files that remain in Nextcloud or another storage system.
562 + </p>
563 +
564 + <h3>Scenario 2: Policies and procedures</h3>
565 + <p>
566 + Policies stored as Google Docs can become XWiki pages with owner, review date, status, history and restricted
567 + edit rights. This makes it easier to know which version is current and who is responsible for keeping it updated.
568 + </p>
569 +
570 + <h3>Scenario 3: Spreadsheet tracker</h3>
571 + <p>
572 + A simple Google Sheet used as a list of requests, assets, documents or contacts may become a small XWiki
573 + application when the fields are stable. A complex financial model or reporting workbook should remain in an
574 + office spreadsheet tool.
575 + </p>
576 +
577 + <h2>Recommended target architecture</h2>
578 +
579 + <p>
580 + A realistic architecture does not replace every Google Workspace feature with XWiki. It gives each tool a clear role.
581 + </p>
582 +
583 + <table class="table table-bordered table-striped">
584 + <thead>
585 + <tr>
586 + <th>Layer</th>
587 + <th>Recommended role</th>
588 + </tr>
589 + </thead>
590 + <tbody>
591 + <tr>
592 + <td>XWiki</td>
593 + <td>Structured knowledge, documentation, governance, working group spaces, policies and decisions.</td>
594 + </tr>
595 + <tr>
596 + <td>Nextcloud or equivalent</td>
597 + <td>General file storage, file sharing, sync clients and optional groupware.</td>
598 + </tr>
599 + <tr>
600 + <td>ONLYOFFICE, Collabora or LibreOffice</td>
601 + <td>Office document editing for documents, spreadsheets and presentations.</td>
602 + </tr>
603 + <tr>
604 + <td>Matrix/Element, Mattermost or Nextcloud Talk</td>
605 + <td>Real-time messaging and team coordination.</td>
606 + </tr>
607 + <tr>
608 + <td>Jitsi or another meeting tool</td>
609 + <td>Video meetings and calls.</td>
610 + </tr>
611 + <tr>
612 + <td>Keycloak or existing identity provider</td>
613 + <td>SSO, group mapping and identity lifecycle.</td>
614 + </tr>
615 + </tbody>
616 + </table>
617 +
618 + <div id="related-resources" class="resource-note related-resources">
619 + <p><strong>Related Agnease resources:</strong></p>
620 + <ul>
621 + <li><a href="$xwiki.getURL('services.xwiki-migrations')">XWiki migration services</a></li>
622 + <li><a href="$xwiki.getURL('services.xwiki-authentication-access-control')">Authentication and access control for XWiki</a></li>
623 + <li><a href="$xwiki.getURL('resources.xwiki-custom-development')">How to customize XWiki without creating upgrade problems</a></li>
624 + <li><a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">Why XWiki access rights need a clear governance model</a></li>
625 + <li><a href="$xwiki.getURL('resources.xwiki-security-review')">What an XWiki security review should actually include</a></li>
626 + </ul>
627 + </div>
628 +
629 + <h2 id="faq">FAQ</h2>
630 +
631 + <details class="resource-faq-item" open>
632 + <summary>Can XWiki replace Google Workspace completely?</summary>
633 + <p>
634 + Not realistically. XWiki should not be presented as a full replacement for email, calendar, video meetings,
635 + chat, file sync, spreadsheets and presentation editing. It is much better positioned as the structured
636 + knowledge and documentation layer.
637 + </p>
638 + </details>
639 +
640 + <details class="resource-faq-item">
641 + <summary>Can XWiki replace Google Docs?</summary>
642 + <p>
643 + It can replace many Google Docs that are actually long-term documentation: policies, procedures, notes,
644 + decisions, guides and knowledge base articles. For fast real-time drafting or complex office formatting,
645 + an office editor such as ONLYOFFICE or Collabora may still be useful.
646 + </p>
647 + </details>
648 +
649 + <details class="resource-faq-item">
650 + <summary>Can XWiki replace Google Drive?</summary>
651 + <p>
652 + Partially. XWiki can manage attachments around knowledge pages and can support file-oriented applications,
653 + but it should not be treated as a full desktop file sync and sharing platform. Nextcloud is usually a better
654 + fit for that role.
655 + </p>
656 + </details>
657 +
658 + <details class="resource-faq-item">
659 + <summary>What is the best first step?</summary>
660 + <p>
661 + Start with one high-value pilot: a working group, committee, department or project that has real
662 + documentation pain. Create the structure, templates, permissions and migration rules for that pilot before
663 + expanding.
664 + </p>
665 + </details>
666 +
667 + <details class="resource-faq-item">
668 + <summary>How do you convince users to try XWiki?</summary>
669 + <p>
670 + Do not start by saying that XWiki is replacing everything. Start by showing that XWiki gives users a clearer,
671 + more reliable place for trusted knowledge: the current document, the owner, the status, the related decisions
672 + and the wider context.
673 + </p>
674 + </details>
675 +
676 + <details class="resource-faq-item">
677 + <summary>What should remain outside XWiki during transition?</summary>
678 + <p>
679 + Temporary drafts, complex spreadsheets, presentation working files, ongoing external collaborations and
680 + anything without a clear owner can remain outside XWiki until the organization has a reason to migrate or
681 + replace that workflow.
682 + </p>
683 + </details>
684 +
685 + </article>
686 + </div>
687 + </div>
688 + </section>
689 +
690 + <section class="cta-section" aria-labelledby="google-workspace-xwiki-cta-title">
691 + <div class="container">
692 + <div class="cta-panel">
693 + <h2 id="google-workspace-xwiki-cta-title">Planning a transition from Google Workspace to XWiki?</h2>
694 + <p>
695 + Agnease can help evaluate what should move to XWiki, what should remain in office collaboration tools,
696 + and how to design the right structure, permissions, templates, SSO and migration approach.
697 + </p>
698 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request a consultation</a>
699 + </div>
700 + </div>
701 + </section>
702 +
703 + <script type="application/ld+json">
704 + {
705 + "@context": "https://schema.org",
706 + "@type": "TechArticle",
707 + "headline": "From Google Workspace to XWiki: a practical transition guide",
708 + "description": "Practical guide for moving durable knowledge from Google Workspace to XWiki, with replacement mapping, open-source alternatives, migration steps and tool limits.",
709 + "author": {
710 + "@type": "Organization",
711 + "name": "Agnease"
712 + },
713 + "publisher": {
714 + "@type": "Organization",
715 + "name": "Agnease",
716 + "url": "https://agnease.com/"
717 + },
718 + "mainEntityOfPage": "https://agnease.com/bin/resources/from-google-workspace-to-xwiki"
719 + }
720 + </script>
721 +
722 + <script type="application/ld+json">
723 + {
724 + "@context": "https://schema.org",
725 + "@type": "FAQPage",
726 + "mainEntity": [
727 + {
728 + "@type": "Question",
729 + "name": "Can XWiki replace Google Workspace completely?",
730 + "acceptedAnswer": {
731 + "@type": "Answer",
732 + "text": "Not realistically. XWiki should not be presented as a full replacement for email, calendar, video meetings, chat, file sync, spreadsheets and presentation editing. It is better positioned as the structured knowledge and documentation layer."
733 + }
734 + },
735 + {
736 + "@type": "Question",
737 + "name": "Can XWiki replace Google Docs?",
738 + "acceptedAnswer": {
739 + "@type": "Answer",
740 + "text": "XWiki can replace many Google Docs that are actually long-term documentation, such as policies, procedures, notes, decisions, guides and knowledge base articles. For fast real-time drafting or complex office formatting, an office editor such as ONLYOFFICE or Collabora may still be useful."
741 + }
742 + },
743 + {
744 + "@type": "Question",
745 + "name": "Can XWiki replace Google Drive?",
746 + "acceptedAnswer": {
747 + "@type": "Answer",
748 + "text": "Partially. XWiki can manage attachments around knowledge pages and can support file-oriented applications, but it should not be treated as a full desktop file sync and sharing platform. Nextcloud is usually a better fit for that role."
749 + }
750 + },
751 + {
752 + "@type": "Question",
753 + "name": "What is the best first step when moving from Google Workspace to XWiki?",
754 + "acceptedAnswer": {
755 + "@type": "Answer",
756 + "text": "Start with one high-value pilot, such as a working group, committee, department or project that has real documentation pain. Create the structure, templates, permissions and migration rules for that pilot before expanding."
757 + }
758 + },
759 + {
760 + "@type": "Question",
761 + "name": "What should remain outside XWiki during transition?",
762 + "acceptedAnswer": {
763 + "@type": "Answer",
764 + "text": "Temporary drafts, complex spreadsheets, presentation working files, ongoing external collaborations and anything without a clear owner can remain outside XWiki until the organization has a reason to migrate or replace that workflow."
765 + }
766 + }
767 + ]
768 + }
769 + </script>
770 +
771 +{{/html}}
772 +{{/velocity}}
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,0 +1,1 @@
1 +Practical guide for moving durable knowledge from Google Workspace to XWiki, with replacement mapping, open-source alternatives, migration steps and tool limits.
metaTitle
... ... @@ -1,0 +1,1 @@
1 +Google Workspace to XWiki: Open Source Collaboration Migration Guide | Agnease