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

Summary

Details

Page properties
Content
... ... @@ -1,777 +1,0 @@
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">
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 -
214 - <div class="cta-panel">
215 - <h2>Need help positioning the transition?</h2>
216 - <p>
217 - Agnease can help map current Google Workspace usage, identify what should move to XWiki,
218 - define the right open-source alternatives, and prepare a realistic pilot migration.
219 - </p>
220 - <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss your transition</a>
221 - </div>
222 -
223 - <h2 id="quick-view">Quick view: how to position the transition</h2>
224 -
225 - <div class="services-grid">
226 - #foreach ($entry in $summaryCards)
227 - <article class="service">
228 - <div class="service-icon" aria-hidden="true">
229 - <i class="fa fa-$entry.icon"></i>
230 - </div>
231 -
232 - <div class="service-body">
233 - <h4>$entry.title</h4>
234 - <p>$entry.content</p>
235 - </div>
236 - </article>
237 - #end
238 - </div>
239 -
240 - <h2 id="workspace-map">What Google Workspace usually provides</h2>
241 -
242 - <p>
243 - Before proposing a transition, it is useful to explain what people currently get from Google Workspace.
244 - Users are not only using a document editor. They are using a complete collaboration habit.
245 - </p>
246 -
247 - <table class="table table-bordered table-striped">
248 - <thead>
249 - <tr>
250 - <th>Google Workspace area</th>
251 - <th>What users value</th>
252 - <th>Risk over time</th>
253 - </tr>
254 - </thead>
255 - <tbody>
256 - <tr>
257 - <td>Google Docs</td>
258 - <td>Fast writing, real-time editing, comments and suggestions.</td>
259 - <td>Important documents become isolated files instead of maintained knowledge.</td>
260 - </tr>
261 - <tr>
262 - <td>Google Drive</td>
263 - <td>Easy sharing, folders, file ownership and external collaboration.</td>
264 - <td>Folder structures grow organically and become hard to govern.</td>
265 - </tr>
266 - <tr>
267 - <td>Google Sheets</td>
268 - <td>Trackers, lists, budgets, lightweight databases and reports.</td>
269 - <td>Business processes become hidden in spreadsheets.</td>
270 - </tr>
271 - <tr>
272 - <td>Google Slides</td>
273 - <td>Presentation creation and sharing.</td>
274 - <td>Reusable knowledge remains locked in slide decks.</td>
275 - </tr>
276 - <tr>
277 - <td>Google Forms</td>
278 - <td>Quick surveys, registrations and data collection.</td>
279 - <td>Collected data may remain detached from internal processes.</td>
280 - </tr>
281 - <tr>
282 - <td>Google Sites</td>
283 - <td>Simple internal or public pages.</td>
284 - <td>Content can be separated from the wider knowledge base.</td>
285 - </tr>
286 - <tr>
287 - <td>Gmail, Calendar, Meet and Chat</td>
288 - <td>Communication, scheduling, meetings and quick coordination.</td>
289 - <td>Decisions remain scattered in messages, calls and informal conversations.</td>
290 - </tr>
291 - </tbody>
292 - </table>
293 -
294 - <h2 id="replacement-map">What can move to XWiki, and what should move elsewhere</h2>
295 -
296 - <p>
297 - A successful transition separates content by purpose. Some content belongs naturally in XWiki. Some should
298 - remain in office collaboration tools. Some should move to other open-source or self-hostable systems that
299 - complement XWiki.
300 - </p>
301 -
302 - <table class="table table-bordered table-striped">
303 - <thead>
304 - <tr>
305 - <th>Current Google Workspace usage</th>
306 - <th>Recommended destination</th>
307 - <th>Transition guidance</th>
308 - </tr>
309 - </thead>
310 - <tbody>
311 - <tr>
312 - <td>Official documentation in Google Docs</td>
313 - <td>XWiki pages, spaces, page history, comments and permissions.</td>
314 - <td>Move final and maintained documentation into XWiki pages.</td>
315 - </tr>
316 - <tr>
317 - <td>Policies, procedures and governance documents</td>
318 - <td>XWiki pages with templates, metadata, review dates and ownership.</td>
319 - <td>Move to XWiki and add lifecycle rules.</td>
320 - </tr>
321 - <tr>
322 - <td>Meeting notes</td>
323 - <td>XWiki meeting note templates inside team or working group spaces.</td>
324 - <td>Start new meeting notes in XWiki and link older notes only when useful.</td>
325 - </tr>
326 - <tr>
327 - <td>Working group or committee documents</td>
328 - <td>XWiki spaces with homepage, members, notes, decisions and documents.</td>
329 - <td>Create one structured space per group.</td>
330 - </tr>
331 - <tr>
332 - <td>Decision records</td>
333 - <td>XWiki decision page template.</td>
334 - <td>Move decisions out of scattered Docs, email and chat.</td>
335 - </tr>
336 - <tr>
337 - <td>Google Sites pages</td>
338 - <td>XWiki public or private spaces.</td>
339 - <td>Move informational pages that need history, permissions or governance.</td>
340 - </tr>
341 - <tr>
342 - <td>Shared file archive</td>
343 - <td>XWiki attachments for curated files; <a href="https://nextcloud.com/files/" target="_blank" rel="noopener">Nextcloud Files</a> for general file sharing.</td>
344 - <td>Use XWiki for files attached to knowledge pages, not for massive file sync.</td>
345 - </tr>
346 - <tr>
347 - <td>Simple trackers in Google Sheets</td>
348 - <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>
349 - <td>Move recurring lists with stable fields and clear ownership.</td>
350 - </tr>
351 - <tr>
352 - <td>Collaborative drafting in Google Docs</td>
353 - <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>
354 - <td>Use XWiki for the maintained version, not every draft.</td>
355 - </tr>
356 - <tr>
357 - <td>Forms and surveys</td>
358 - <td>XWiki forms for internal processes; <a href="https://www.limesurvey.org/" target="_blank" rel="noopener">LimeSurvey</a> for advanced surveys.</td>
359 - <td>Use the right tool depending on whether it is workflow data or survey data.</td>
360 - </tr>
361 - </tbody>
362 - </table>
363 -
364 - <h2 id="what-belongs-in-xwiki">What belongs naturally in XWiki</h2>
365 -
366 - <p>
367 - XWiki is a strong destination for information that should be easy to find, maintain, discuss, review and trust
368 - over time.
369 - </p>
370 -
371 - <div class="services-grid">
372 - #foreach ($entry in $xwikiFitCards)
373 - <article class="service">
374 - <div class="service-icon" aria-hidden="true">
375 - <i class="fa fa-$entry.icon"></i>
376 - </div>
377 -
378 - <div class="service-body">
379 - <h4>$entry.title</h4>
380 - <p>$entry.content</p>
381 - </div>
382 - </article>
383 - #end
384 - </div>
385 -
386 - <h2 id="not-xwiki">What should not be replaced by XWiki</h2>
387 -
388 - <p>
389 - A credible transition guide should clearly explain where XWiki is not the right tool. This avoids unrealistic
390 - expectations and helps the organization design a better collaboration stack.
391 - </p>
392 -
393 - <div class="services-grid">
394 - #foreach ($entry in $notXWikiCards)
395 - <article class="service">
396 - <div class="service-icon" aria-hidden="true">
397 - <i class="fa fa-$entry.icon"></i>
398 - </div>
399 -
400 - <div class="service-body">
401 - <h4>$entry.title</h4>
402 - <p>$entry.content</p>
403 - </div>
404 - </article>
405 - #end
406 - </div>
407 -
408 - <div class="resource-note">
409 - <p>
410 - <strong>In practice:</strong> the goal is not to make XWiki do everything. The goal is to make XWiki the
411 - trusted home for maintained knowledge, while integrating or linking to the right tools for files, office
412 - editing, chat, meetings and identity.
413 - </p>
414 - </div>
415 -
416 - <h2 id="open-source-stack">Open-source alternatives that can complement XWiki</h2>
417 -
418 - <p>
419 - For organizations trying to reduce dependency on Google Workspace, XWiki can become part of a broader
420 - open-source collaboration architecture. The exact stack depends on hosting preferences, support needs,
421 - security requirements and user expectations.
422 - </p>
423 -
424 - <table class="table table-bordered table-striped">
425 - <thead>
426 - <tr>
427 - <th>Need</th>
428 - <th>Possible solution</th>
429 - <th>How it works with XWiki</th>
430 - </tr>
431 - </thead>
432 - <tbody>
433 - <tr>
434 - <td>Structured knowledge base</td>
435 - <td><a href="https://www.xwiki.org/" target="_blank" rel="noopener">XWiki</a></td>
436 - <td>Main platform for documentation, governance, knowledge management and structured content.</td>
437 - </tr>
438 - <tr>
439 - <td>File sync and sharing</td>
440 - <td><a href="https://nextcloud.com/files/" target="_blank" rel="noopener">Nextcloud Files</a></td>
441 - <td>Use for general file storage and sharing; link important files from XWiki pages.</td>
442 - </tr>
443 - <tr>
444 - <td>Office document editing</td>
445 - <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>
446 - <td>Use for documents, spreadsheets and presentations that need office-style editing.</td>
447 - </tr>
448 - <tr>
449 - <td>Chat and team messaging</td>
450 - <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>
451 - <td>Use for real-time conversation; move durable decisions and outcomes back into XWiki.</td>
452 - </tr>
453 - <tr>
454 - <td>Video meetings</td>
455 - <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>
456 - <td>Use for calls; store agendas, notes and decisions in XWiki.</td>
457 - </tr>
458 - <tr>
459 - <td>Surveys and advanced forms</td>
460 - <td><a href="https://www.limesurvey.org/" target="_blank" rel="noopener">LimeSurvey</a></td>
461 - <td>Use for survey campaigns; publish results, summaries or procedures in XWiki.</td>
462 - </tr>
463 - <tr>
464 - <td>Identity and SSO</td>
465 - <td><a href="https://www.keycloak.org/" target="_blank" rel="noopener">Keycloak</a>, Microsoft Entra ID, Google identity or another OIDC/SAML provider.</td>
466 - <td>Use SSO so users access XWiki without a separate password and with mapped groups where appropriate.</td>
467 - </tr>
468 - </tbody>
469 - </table>
470 -
471 - <h2 id="transition-plan">A practical transition plan</h2>
472 -
473 - <p>
474 - The safest transition is gradual. The organization should not begin by migrating every Google Drive folder.
475 - That approach creates too much noise, too many permission questions and too many low-value documents.
476 - </p>
477 -
478 - <ol class="process-list">
479 - #foreach ($entry in $roadmapSteps)
480 - <li>
481 - <strong>$entry.title</strong>
482 - $entry.content
483 - </li>
484 - #end
485 - </ol>
486 -
487 - <h2 id="pilot">A good pilot: one working group space</h2>
488 -
489 - <p>
490 - A strong pilot is small enough to control but useful enough to prove value. For example, one working group,
491 - committee, project team or community group can move its durable knowledge into XWiki while keeping office
492 - tools for drafting, spreadsheets and presentations when needed.
493 - </p>
494 -
495 - <div class="services-grid">
496 - #foreach ($entry in $pilotCards)
497 - <article class="service">
498 - <div class="service-icon" aria-hidden="true">
499 - <i class="fa fa-$entry.icon"></i>
500 - </div>
501 -
502 - <div class="service-body">
503 - <h4>$entry.title</h4>
504 - <p>$entry.content</p>
505 - </div>
506 - </article>
507 - #end
508 - </div>
509 -
510 - <div class="resource-note">
511 - <p>
512 - <strong>Pilot success question:</strong> can members find the current and trusted version of important
513 - information faster than before?
514 - </p>
515 - </div>
516 -
517 - <h2 id="adoption">How to convince the team to use XWiki</h2>
518 -
519 - <p>
520 - People do not usually change collaboration habits because a new platform exists. They change when the new
521 - platform makes an important part of their work easier, clearer or more reliable.
522 - </p>
523 -
524 - <p>
525 - A useful adoption message is:
526 - </p>
527 -
528 - <div class="resource-note">
529 - <p>
530 - <strong>XWiki is not another folder where files disappear. It is the place where the organization keeps
531 - the current version, the owner, the context, the decision and the links around important knowledge.</strong>
532 - </p>
533 - </div>
534 -
535 - <p>
536 - Simple rules help adoption more than abstract platform arguments:
537 - </p>
538 -
539 - <ul class="resource-checklist">
540 - <li>If it is official, maintained or reusable, it belongs in XWiki.</li>
541 - <li>If it is a temporary draft, it can stay in an office editor until it becomes useful knowledge.</li>
542 - <li>If it is a complex spreadsheet, do not force it into XWiki.</li>
543 - <li>If it was decided in a meeting or chat, summarize the decision in XWiki.</li>
544 - <li>If nobody owns it, do not migrate it as current content.</li>
545 - <li>If users need the same answer repeatedly, create or improve an XWiki page.</li>
546 - </ul>
547 -
548 - <h2 id="implementation">Practical XWiki features to implement early</h2>
549 -
550 - <p>
551 - The following improvements can make the transition easier to accept and easier to govern.
552 - </p>
553 -
554 - <ul class="resource-checklist">
555 - #foreach ($item in $implementationItems)
556 - <li>$item</li>
557 - #end
558 - </ul>
559 -
560 - <h2>Example transition scenarios</h2>
561 -
562 - <h3>Scenario 1: Working group documentation</h3>
563 - <p>
564 - A working group has Google Docs for agendas, meeting notes, decisions and reference files. In XWiki, this can
565 - become a structured space with a homepage, meeting note template, decision records, document list, open
566 - questions and links to files that remain in Nextcloud or another storage system.
567 - </p>
568 -
569 - <h3>Scenario 2: Policies and procedures</h3>
570 - <p>
571 - Policies stored as Google Docs can become XWiki pages with owner, review date, status, history and restricted
572 - edit rights. This makes it easier to know which version is current and who is responsible for keeping it updated.
573 - </p>
574 -
575 - <h3>Scenario 3: Spreadsheet tracker</h3>
576 - <p>
577 - A simple Google Sheet used as a list of requests, assets, documents or contacts may become a small XWiki
578 - application when the fields are stable. A complex financial model or reporting workbook should remain in an
579 - office spreadsheet tool.
580 - </p>
581 -
582 - <h2>Recommended target architecture</h2>
583 -
584 - <p>
585 - A realistic architecture does not replace every Google Workspace feature with XWiki. It gives each tool a clear role.
586 - </p>
587 -
588 - <table class="table table-bordered table-striped">
589 - <thead>
590 - <tr>
591 - <th>Layer</th>
592 - <th>Recommended role</th>
593 - </tr>
594 - </thead>
595 - <tbody>
596 - <tr>
597 - <td>XWiki</td>
598 - <td>Structured knowledge, documentation, governance, working group spaces, policies and decisions.</td>
599 - </tr>
600 - <tr>
601 - <td>Nextcloud or equivalent</td>
602 - <td>General file storage, file sharing, sync clients and optional groupware.</td>
603 - </tr>
604 - <tr>
605 - <td>ONLYOFFICE, Collabora or LibreOffice</td>
606 - <td>Office document editing for documents, spreadsheets and presentations.</td>
607 - </tr>
608 - <tr>
609 - <td>Matrix/Element, Mattermost or Nextcloud Talk</td>
610 - <td>Real-time messaging and team coordination.</td>
611 - </tr>
612 - <tr>
613 - <td>Jitsi or another meeting tool</td>
614 - <td>Video meetings and calls.</td>
615 - </tr>
616 - <tr>
617 - <td>Keycloak or existing identity provider</td>
618 - <td>SSO, group mapping and identity lifecycle.</td>
619 - </tr>
620 - </tbody>
621 - </table>
622 -
623 - <div id="related-resources" class="resource-note related-resources">
624 - <p><strong>Related Agnease resources:</strong></p>
625 - <ul>
626 - <li><a href="$xwiki.getURL('services.xwiki-migrations')">XWiki migration services</a></li>
627 - <li><a href="$xwiki.getURL('services.xwiki-authentication-access-control')">Authentication and access control for XWiki</a></li>
628 - <li><a href="$xwiki.getURL('resources.xwiki-custom-development')">How to customize XWiki without creating upgrade problems</a></li>
629 - <li><a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">Why XWiki access rights need a clear governance model</a></li>
630 - <li><a href="$xwiki.getURL('resources.xwiki-security-review')">What an XWiki security review should actually include</a></li>
631 - </ul>
632 - </div>
633 -
634 - <h2 id="faq">FAQ</h2>
635 -
636 - <details class="resource-faq-item" open>
637 - <summary>Can XWiki replace Google Workspace completely?</summary>
638 - <p>
639 - Not realistically. XWiki should not be presented as a full replacement for email, calendar, video meetings,
640 - chat, file sync, spreadsheets and presentation editing. It is much better positioned as the structured
641 - knowledge and documentation layer.
642 - </p>
643 - </details>
644 -
645 - <details class="resource-faq-item">
646 - <summary>Can XWiki replace Google Docs?</summary>
647 - <p>
648 - It can replace many Google Docs that are actually long-term documentation: policies, procedures, notes,
649 - decisions, guides and knowledge base articles. For fast real-time drafting or complex office formatting,
650 - an office editor such as ONLYOFFICE or Collabora may still be useful.
651 - </p>
652 - </details>
653 -
654 - <details class="resource-faq-item">
655 - <summary>Can XWiki replace Google Drive?</summary>
656 - <p>
657 - Partially. XWiki can manage attachments around knowledge pages and can support file-oriented applications,
658 - but it should not be treated as a full desktop file sync and sharing platform. Nextcloud is usually a better
659 - fit for that role.
660 - </p>
661 - </details>
662 -
663 - <details class="resource-faq-item">
664 - <summary>What is the best first step?</summary>
665 - <p>
666 - Start with one high-value pilot: a working group, committee, department or project that has real
667 - documentation pain. Create the structure, templates, permissions and migration rules for that pilot before
668 - expanding.
669 - </p>
670 - </details>
671 -
672 - <details class="resource-faq-item">
673 - <summary>How do you convince users to try XWiki?</summary>
674 - <p>
675 - Do not start by saying that XWiki is replacing everything. Start by showing that XWiki gives users a clearer,
676 - more reliable place for trusted knowledge: the current document, the owner, the status, the related decisions
677 - and the wider context.
678 - </p>
679 - </details>
680 -
681 - <details class="resource-faq-item">
682 - <summary>What should remain outside XWiki during transition?</summary>
683 - <p>
684 - Temporary drafts, complex spreadsheets, presentation working files, ongoing external collaborations and
685 - anything without a clear owner can remain outside XWiki until the organization has a reason to migrate or
686 - replace that workflow.
687 - </p>
688 - </details>
689 -
690 - </article>
691 - </div>
692 - </div>
693 - </section>
694 -
695 - <section class="cta-section" aria-labelledby="google-workspace-xwiki-cta-title">
696 - <div class="container">
697 - <div class="cta-panel">
698 - <h2 id="google-workspace-xwiki-cta-title">Planning a transition from Google Workspace to XWiki?</h2>
699 - <p>
700 - Agnease can help evaluate what should move to XWiki, what should remain in office collaboration tools,
701 - and how to design the right structure, permissions, templates, SSO and migration approach.
702 - </p>
703 - <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request a consultation</a>
704 - </div>
705 - </div>
706 - </section>
707 -
708 - <script type="application/ld+json">
709 - {
710 - "@context": "https://schema.org",
711 - "@type": "TechArticle",
712 - "headline": "From Google Workspace to XWiki: a practical transition guide",
713 - "description": "Practical guide for moving durable knowledge from Google Workspace to XWiki, with replacement mapping, open-source alternatives, migration steps and tool limits.",
714 - "author": {
715 - "@type": "Organization",
716 - "name": "Agnease"
717 - },
718 - "publisher": {
719 - "@type": "Organization",
720 - "name": "Agnease",
721 - "url": "https://agnease.com/"
722 - },
723 - "mainEntityOfPage": "https://agnease.com/bin/resources/from-google-workspace-to-xwiki"
724 - }
725 - </script>
726 -
727 - <script type="application/ld+json">
728 - {
729 - "@context": "https://schema.org",
730 - "@type": "FAQPage",
731 - "mainEntity": [
732 - {
733 - "@type": "Question",
734 - "name": "Can XWiki replace Google Workspace completely?",
735 - "acceptedAnswer": {
736 - "@type": "Answer",
737 - "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."
738 - }
739 - },
740 - {
741 - "@type": "Question",
742 - "name": "Can XWiki replace Google Docs?",
743 - "acceptedAnswer": {
744 - "@type": "Answer",
745 - "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."
746 - }
747 - },
748 - {
749 - "@type": "Question",
750 - "name": "Can XWiki replace Google Drive?",
751 - "acceptedAnswer": {
752 - "@type": "Answer",
753 - "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."
754 - }
755 - },
756 - {
757 - "@type": "Question",
758 - "name": "What is the best first step when moving from Google Workspace to XWiki?",
759 - "acceptedAnswer": {
760 - "@type": "Answer",
761 - "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."
762 - }
763 - },
764 - {
765 - "@type": "Question",
766 - "name": "What should remain outside XWiki during transition?",
767 - "acceptedAnswer": {
768 - "@type": "Answer",
769 - "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."
770 - }
771 - }
772 - ]
773 - }
774 - </script>
775 -
776 -{{/html}}
777 -{{/velocity}}
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,1 +1,0 @@
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,1 +1,0 @@
1 -Google Workspace to XWiki: Open Source Collaboration Migration Guide | Agnease