Changes for page From Google Workspace to XWiki: A Practical Transition Guide

Last modified by Agnease on 2026/07/03 12:22

Manage
- Copy
Actions
- Export
- Print Preview
Viewers
- Source
- Siblings
- Content
- Comments
- Attachments
- History
- Information
- Likes

From 1.3 to 1.4

From version 1.1

edited by Agnease
on 2026/07/03 11:08

Change comment: There is no comment for this version

To version 1.3

edited by Agnease
on 2026/07/03 11:08

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -1,0 +1,873 @@
++{{velocity}}
++#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
++{{html clean="false"}}
++
++  <section class="resource-header" aria-labelledby="hero-title">
++    <div class="container">
++      <div class="text-center">
++        <div class="hero-kicker">
++          <i class="fa fa-exchange" aria-hidden="true"></i>
++          XWiki migration guidance
++        </div>
++      </div>
++
++      <h1 id="hero-title">From Google Workspace to XWiki: a practical transition guide</h1>
++
++      <p class="resource-summary">
++        A straightforward guide for organizations that want to move durable knowledge, documentation and governance
++        from Google Workspace into XWiki, without pretending that XWiki should replace every collaboration tool.
++      </p>
++    </div>
++  </section>
++
++  <section class="resource-page">
++    <div class="container">
++      <div class="resource-layout">
++
++        <aside class="resource-sidebar" aria-label="Page summary">
++          <h4>In this guide</h4>
++          <ul>
++            <li><a href="#main-idea">Main idea</a></li>
++            <li><a href="#workspace-map">What Google Workspace covers</a></li>
++            <li><a href="#replacement-map">What can move to XWiki</a></li>
++            <li><a href="#not-xwiki">What should not move to XWiki</a></li>
++            <li><a href="#open-source-stack">Open-source alternatives</a></li>
++            <li><a href="#transition-plan">Transition plan</a></li>
++            <li><a href="#pilot">Pilot example</a></li>
++            <li><a href="#adoption">Adoption guidance</a></li>
++            <li><a href="#faq">FAQ</a></li>
++          </ul>
++        </aside>
++
++        <article class="resource-content">
++
++          <p>
++            Moving an organization away from Google Workspace is rarely just a software migration. It is also a change in
++            habits, ownership, permissions, document lifecycle and the way people expect collaboration to happen.
++          </p>
++
++          <p>
++            Google Workspace is often successful because it is the default place where people write documents, share files,
++            collaborate in real time, collect information, meet, chat and search. This makes any transition feel difficult,
++            especially when users are already comfortable with the existing tools.
++          </p>
++
++          <div class="resource-note">
++            <p>
++              <strong>The practical position:</strong> XWiki should not be presented as a full one-to-one replacement for
++              Google Workspace. XWiki is strongest as the structured knowledge layer: official documentation, working group
++              spaces, policies, procedures, meeting notes, decisions, knowledge bases, governance content and maintained
++              organizational memory.
++            </p>
++          </div>
++
++          <p>
++            A realistic transition does not start by moving everything out of Google Drive. It starts by deciding what kind
++            of information should become durable, structured and maintained in XWiki, and what kind of work should remain
++            in office, file-sharing, communication or meeting tools.
++          </p>
++
++          <h2 id="main-idea">The main idea: do not replace the suite, replace the knowledge problem</h2>
++
++          <p>
++            The strongest argument for XWiki is not that it can imitate Google Workspace. The strongest argument is that
++            it can solve a problem that often appears inside Google Workspace over time: scattered documents, unclear
++            ownership, duplicated files, weak navigation, old links, inconsistent permissions and no obvious place for
++            the trusted version of important knowledge.
++          </p>
++
++          <p>
++            A useful message for an organization is:
++          </p>
++
++          <div class="resource-note">
++            <p>
++              <strong>Use Google-style office tools for fast drafting and real-time editing when needed. Use XWiki for
++              trusted, maintained, structured knowledge that people need to find and rely on later.</strong>
++            </p>
++          </div>
++
++          <h2 id="workspace-map">What Google Workspace usually provides</h2>
++
++          <p>
++            Before proposing a transition, it is important to understand why users are attached to Google Workspace.
++            They are not only attached to a document editor. They are attached to an entire collaboration habit.
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Google Workspace area</th>
++                <th>What users usually value</th>
++                <th>Typical organizational risk over time</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Google Docs</td>
++                <td>Fast writing, real-time editing, comments and suggestions.</td>
++                <td>Documents become isolated files instead of part of a maintained knowledge structure.</td>
++              </tr>
++              <tr>
++                <td>Google Drive</td>
++                <td>Easy file sharing, folders, ownership and external collaboration.</td>
++                <td>Folder structures grow organically and become difficult to clean up or govern.</td>
++              </tr>
++              <tr>
++                <td>Google Sheets</td>
++                <td>Simple trackers, lists, budgets, lightweight databases and reports.</td>
++                <td>Business processes become hidden in spreadsheets without clear ownership or validation.</td>
++              </tr>
++              <tr>
++                <td>Google Slides</td>
++                <td>Presentation creation and sharing.</td>
++                <td>Final knowledge remains locked in presentation files instead of reusable documentation.</td>
++              </tr>
++              <tr>
++                <td>Google Forms</td>
++                <td>Quick surveys, registration forms and internal data collection.</td>
++                <td>Collected data may not become part of a structured internal process.</td>
++              </tr>
++              <tr>
++                <td>Google Sites</td>
++                <td>Simple internal or public pages.</td>
++                <td>Content may be separated from the broader knowledge base and governance model.</td>
++              </tr>
++              <tr>
++                <td>Gmail, Calendar, Meet and Chat</td>
++                <td>Communication, scheduling, meetings and quick coordination.</td>
++                <td>Decisions and knowledge remain scattered in messages, meetings and informal conversations.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h2 id="replacement-map">What can move to XWiki, and what should only partially move</h2>
++
++          <p>
++            A good transition separates content by purpose. Some content belongs naturally in XWiki. Some content should
++            remain in office collaboration tools. Some content should be moved to other open-source or self-hostable
++            systems that complement XWiki.
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Current Google Workspace usage</th>
++                <th>XWiki replacement or equivalent</th>
++                <th>Fit</th>
++                <th>Recommended transition</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Official documentation in Google Docs</td>
++                <td>XWiki pages, spaces, navigation, page history, comments and permissions.</td>
++                <td>Excellent</td>
++                <td>Move final and maintained documentation to XWiki pages.</td>
++              </tr>
++              <tr>
++                <td>Policies, procedures and governance documents</td>
++                <td>XWiki pages with templates, metadata, review dates, ownership and approval workflows.</td>
++                <td>Excellent</td>
++                <td>Move to XWiki and add lifecycle rules.</td>
++              </tr>
++              <tr>
++                <td>Meeting notes</td>
++                <td>XWiki meeting note templates inside team or working group spaces.</td>
++                <td>Excellent</td>
++                <td>Start new meeting notes in XWiki and link older notes when useful.</td>
++              </tr>
++              <tr>
++                <td>Working group or committee documents</td>
++                <td>XWiki spaces with homepage, members, notes, decisions, documents and tasks.</td>
++                <td>Excellent</td>
++                <td>Create one structured space per group.</td>
++              </tr>
++              <tr>
++                <td>Decision records</td>
++                <td>XWiki decision page template with context, options, decision, owner and date.</td>
++                <td>Excellent</td>
++                <td>Move decisions out of scattered Docs, email and chat.</td>
++              </tr>
++              <tr>
++                <td>Google Sites pages</td>
++                <td>XWiki spaces and pages, public or private depending on rights.</td>
++                <td>Very good</td>
++                <td>Move informational pages to XWiki when they need structure, history or governance.</td>
++              </tr>
++              <tr>
++                <td>Shared file archive</td>
++                <td>XWiki attachments, File Manager-style applications or linked external storage.</td>
++                <td>Good, with limits</td>
++                <td>Use XWiki for curated files attached to knowledge pages, not for massive file sync.</td>
++              </tr>
++              <tr>
++                <td>Simple trackers in Google Sheets</td>
++                <td>XWiki structured applications, App Within Minutes or custom XWiki apps.</td>
++                <td>Good for structured records</td>
++                <td>Move recurring lists with stable fields; keep complex spreadsheets elsewhere.</td>
++              </tr>
++              <tr>
++                <td>Collaborative drafting in Google Docs</td>
++                <td>XWiki real-time editing or office document integrations such as ONLYOFFICE or Collabora.</td>
++                <td>Partial</td>
++                <td>Use XWiki for final content; test collaborative editing needs separately.</td>
++              </tr>
++              <tr>
++                <td>Forms and surveys</td>
++                <td>XWiki forms for internal structured data; LimeSurvey or similar tools for advanced surveys.</td>
++                <td>Partial</td>
++                <td>Use XWiki for workflow forms, not necessarily for all survey campaigns.</td>
++              </tr>
++              <tr>
++                <td>Slides and presentation decks</td>
++                <td>XWiki pages for the reusable knowledge behind the presentation.</td>
++                <td>Limited</td>
++                <td>Store final slides as attachments if needed, but document the core knowledge in XWiki.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h2 id="what-belongs-in-xwiki">What belongs naturally in XWiki</h2>
++
++          <p>
++            XWiki is a strong destination for information that should be easy to find, maintain, discuss, review and trust
++            over time.
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Content type</th>
++                <th>Example</th>
++                <th>Why XWiki is a good fit</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Organizational knowledge</td>
++                <td>How the organization works, who owns what, internal processes.</td>
++                <td>Structured spaces, navigation, search and page history make the knowledge easier to maintain.</td>
++              </tr>
++              <tr>
++                <td>Working group spaces</td>
++                <td>Homepage, members, meetings, decisions, documents and open questions.</td>
++                <td>Each group gets a stable knowledge home instead of a folder full of unrelated files.</td>
++              </tr>
++              <tr>
++                <td>Policies and procedures</td>
++                <td>Security policy, onboarding procedure, publication process, governance rules.</td>
++                <td>Ownership, review date, approval state and history can be made explicit.</td>
++              </tr>
++              <tr>
++                <td>Decision records</td>
++                <td>Why a tool was selected, why a policy changed, why a migration approach was chosen.</td>
++                <td>Decisions become searchable and linked to related documentation.</td>
++              </tr>
++              <tr>
++                <td>Community documentation</td>
++                <td>Member guides, contribution guides, public project pages, FAQs.</td>
++                <td>XWiki can support public and private content with a consistent structure.</td>
++              </tr>
++              <tr>
++                <td>Structured internal apps</td>
++                <td>Registers, inventories, simple approval requests, directories, lists.</td>
++                <td>XWiki can model structured data instead of leaving every process in a spreadsheet.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h2 id="not-xwiki">What should not be replaced by XWiki</h2>
++
++          <p>
++            A credible transition guide should clearly explain where XWiki is not the right tool. This avoids unrealistic
++            expectations and helps the organization design a better open collaboration stack.
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Need</th>
++                <th>Why XWiki is not the best replacement</th>
++                <th>Better direction</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Email</td>
++                <td>XWiki is not an email platform.</td>
++                <td>Keep the existing mail system or evaluate dedicated mail/groupware solutions.</td>
++              </tr>
++              <tr>
++                <td>Calendar and scheduling</td>
++                <td>XWiki can display or manage calendar-like information, but it is not a full scheduling suite.</td>
++                <td>Use a groupware platform such as Nextcloud Groupware or keep the existing calendar system.</td>
++              </tr>
++              <tr>
++                <td>Video meetings</td>
++                <td>XWiki is not a video conferencing system.</td>
++                <td>Use Jitsi, Nextcloud Talk or another dedicated meeting tool.</td>
++              </tr>
++              <tr>
++                <td>Instant messaging and chat</td>
++                <td>XWiki comments and notifications do not replace real-time chat.</td>
++                <td>Use Matrix/Element, Mattermost, Nextcloud Talk or another chat platform.</td>
++              </tr>
++              <tr>
++                <td>General file sync and desktop folder replacement</td>
++                <td>XWiki attachments are useful around pages, but XWiki is not designed as a Dropbox or Drive sync client.</td>
++                <td>Use Nextcloud Files or another file sync and sharing platform.</td>
++              </tr>
++              <tr>
++                <td>Heavy spreadsheets</td>
++                <td>Complex formulas, pivot tables, financial models and large spreadsheet workflows are not XWiki's role.</td>
++                <td>Use ONLYOFFICE, Collabora, LibreOffice or another office suite.</td>
++              </tr>
++              <tr>
++                <td>Presentation authoring</td>
++                <td>XWiki can document knowledge and store final files, but it is not a presentation editor.</td>
++                <td>Use ONLYOFFICE, Collabora, LibreOffice Impress or another presentation tool.</td>
++              </tr>
++              <tr>
++                <td>Large survey campaigns</td>
++                <td>XWiki can collect structured data, but advanced surveys need branching, reporting and respondent management.</td>
++                <td>Use LimeSurvey or another survey platform.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <div class="resource-note">
++            <p>
++              <strong>In practice:</strong> the goal is not to make XWiki do everything. The goal is to make XWiki the
++              trusted home for maintained knowledge, while integrating or linking to the right tools for files, office
++              editing, chat, meetings and identity.
++            </p>
++          </div>
++
++          <h2 id="open-source-stack">Open-source alternatives that can complement XWiki</h2>
++
++          <p>
++            For organizations trying to reduce dependency on Google Workspace, XWiki can be part of a broader open-source
++            collaboration architecture. The exact stack depends on hosting preferences, support needs, security requirements
++            and user expectations.
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Collaboration need</th>
++                <th>Possible open-source or self-hostable contender</th>
++                <th>How it works with XWiki</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Structured knowledge base</td>
++                <td>XWiki</td>
++                <td>Main platform for documentation, governance, knowledge management and structured pages.</td>
++              </tr>
++              <tr>
++                <td>File sync and file sharing</td>
++                <td>Nextcloud Files</td>
++                <td>Use for general file storage and sharing; link important files from XWiki pages when needed.</td>
++              </tr>
++              <tr>
++                <td>Office document editing</td>
++                <td>ONLYOFFICE Docs or Collabora Online</td>
++                <td>Use for documents, spreadsheets and presentations; integrate with XWiki where office attachments must be edited directly.</td>
++              </tr>
++              <tr>
++                <td>Chat and team messaging</td>
++                <td>Matrix/Element, Mattermost or Nextcloud Talk</td>
++                <td>Use for real-time conversations; move durable decisions and outcomes back into XWiki.</td>
++              </tr>
++              <tr>
++                <td>Video meetings</td>
++                <td>Jitsi or Nextcloud Talk</td>
++                <td>Use for calls; store agendas, notes and decisions in XWiki.</td>
++              </tr>
++              <tr>
++                <td>Surveys and advanced forms</td>
++                <td>LimeSurvey</td>
++                <td>Use for survey campaigns; publish results or documentation in XWiki.</td>
++              </tr>
++              <tr>
++                <td>Identity and SSO</td>
++                <td>Keycloak, existing Google identity, Microsoft Entra ID or another OIDC/SAML provider</td>
++                <td>Use SSO so users access XWiki without a separate password and with mapped groups where appropriate.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h2 id="transition-plan">A practical transition plan</h2>
++
++          <p>
++            The safest transition is gradual. The organization should not begin by migrating every Google Drive folder.
++            That approach creates too much noise, too many permission questions and too many low-value documents.
++          </p>
++
++          <h3>1. Define the role of XWiki</h3>
++
++          <p>
++            Start with a clear rule:
++          </p>
++
++          <div class="resource-note">
++            <p>
++              <strong>XWiki is the place for official, maintained and reusable knowledge. Office tools are for temporary
++              drafting, spreadsheets, presentations and real-time editing when they are truly needed.</strong>
++            </p>
++          </div>
++
++          <p>
++            This prevents users from seeing XWiki as just another storage location. It gives XWiki a distinct purpose.
++          </p>
++
++          <h3>2. Identify high-value content first</h3>
++
++          <p>
++            Do not migrate by volume. Migrate by value.
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Move early</th>
++                <th>Move later or archive</th>
++                <th>Usually do not move</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Policies, procedures, onboarding guides, public docs, working group pages, decision records.</td>
++                <td>Older project files, historical meeting notes, reference documents with unclear ownership.</td>
++                <td>Draft files, personal documents, complex spreadsheets, presentation working files, temporary collaboration docs.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h3>3. Create templates before asking people to write</h3>
++
++          <p>
++            Empty wiki pages slow adoption. Users should not have to decide the structure every time.
++          </p>
++
++          <p>
++            Useful starting templates include:
++          </p>
++
++          <ul>
++            <li>Working group homepage</li>
++            <li>Meeting notes</li>
++            <li>Decision record</li>
++            <li>Policy or procedure</li>
++            <li>Project homepage</li>
++            <li>FAQ page</li>
++            <li>Onboarding page</li>
++            <li>External collaboration page</li>
++          </ul>
++
++          <h3>4. Reduce login friction with SSO</h3>
++
++          <p>
++            If users need another account and another password, adoption becomes harder. XWiki should be connected to the
++            organization's identity provider where possible. This can also support cleaner group mapping and a better
++            external collaborator lifecycle.
++          </p>
++
++          <h3>5. Define permissions and ownership rules</h3>
++
++          <p>
++            Access rights should be designed before content is migrated. A common model is:
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Area</th>
++                <th>Recommended ownership</th>
++                <th>Typical access</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Public documentation</td>
++                <td>Documentation or communication owner</td>
++                <td>Public view, restricted edit.</td>
++              </tr>
++              <tr>
++                <td>Internal knowledge base</td>
++                <td>Operations, staff or knowledge management owner</td>
++                <td>Authenticated view, controlled edit.</td>
++              </tr>
++              <tr>
++                <td>Working group space</td>
++                <td>Working group chair or coordinator</td>
++                <td>Group members edit, others view depending on sensitivity.</td>
++              </tr>
++              <tr>
++                <td>Board or restricted area</td>
++                <td>Named administrative owner</td>
++                <td>Explicit restricted group access.</td>
++              </tr>
++              <tr>
++                <td>External collaboration area</td>
++                <td>Internal sponsor</td>
++                <td>Limited groups, expiration or periodic review.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h3>6. Migrate content into structure, not just into pages</h3>
++
++          <p>
++            A migration that only copies Google Docs into XWiki pages may reproduce the same confusion in a different
++            platform. Each migrated page should have a place, an owner and a reason to exist.
++          </p>
++
++          <p>
++            For each migrated document, decide:
++          </p>
++
++          <ul>
++            <li>Who owns this page?</li>
++            <li>Is it current, historical or archived?</li>
++            <li>Who can view it?</li>
++            <li>Who can edit it?</li>
++            <li>Does it need a review date?</li>
++            <li>Should it remain as an attachment instead of becoming a wiki page?</li>
++            <li>What related pages should link to it?</li>
++          </ul>
++
++          <h3>7. Keep a transition dashboard</h3>
++
++          <p>
++            A simple XWiki dashboard can make the transition visible and manageable.
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Dashboard section</th>
++                <th>Purpose</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Content selected for migration</td>
++                <td>Shows the high-value documents that are being moved first.</td>
++              </tr>
++              <tr>
++                <td>Content needing an owner</td>
++                <td>Prevents orphan pages from entering the new system.</td>
++              </tr>
++              <tr>
++                <td>Content to keep in Google or office tools</td>
++                <td>Makes it clear that not everything must move.</td>
++              </tr>
++              <tr>
++                <td>External access review</td>
++                <td>Tracks documents or spaces shared with people outside the organization.</td>
++              </tr>
++              <tr>
++                <td>Recently migrated pages</td>
++                <td>Helps users see progress and discover the new structure.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h2 id="pilot">A good pilot: one working group space</h2>
++
++          <p>
++            A strong pilot is small enough to control but useful enough to prove value. For example, one working group,
++            committee, project team or community group can move its durable knowledge into XWiki while keeping office
++            tools for drafting and spreadsheets when needed.
++          </p>
++
++          <p>
++            A pilot space could include:
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Page or section</th>
++                <th>Purpose</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>Working group homepage</td>
++                <td>Explains the purpose, scope, members, links and current priorities.</td>
++              </tr>
++              <tr>
++                <td>Meeting notes</td>
++                <td>Uses a consistent template so notes are easy to scan and search.</td>
++              </tr>
++              <tr>
++                <td>Decisions</td>
++                <td>Captures important decisions separately from long meeting notes.</td>
++              </tr>
++              <tr>
++                <td>Documents</td>
++                <td>Links official documents, policies and important files.</td>
++              </tr>
++              <tr>
++                <td>Open questions</td>
++                <td>Tracks unresolved topics without hiding them in chat or email.</td>
++              </tr>
++              <tr>
++                <td>FAQ</td>
++                <td>Collects recurring questions from the community.</td>
++              </tr>
++              <tr>
++                <td>External links</td>
++                <td>Provides a bridge to Google Drive, Nextcloud, issue trackers or other systems still in use.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <div class="resource-note">
++            <p>
++              <strong>Pilot success question:</strong> Can members find the current and trusted version of important
++              information faster than before?
++            </p>
++          </div>
++
++          <h2 id="adoption">How to encourage adoption</h2>
++
++          <p>
++            People do not usually change collaboration habits because a new platform exists. They change when the new
++            platform makes an important part of their work easier, clearer or more reliable.
++          </p>
++
++          <h3>Use simple rules</h3>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Rule</th>
++                <th>Example</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>If it is official, it belongs in XWiki.</td>
++                <td>Policies, procedures, final decisions, project documentation.</td>
++              </tr>
++              <tr>
++                <td>If it is temporary drafting, it can stay in an office editor.</td>
++                <td>Collaborative draft document, presentation working file.</td>
++              </tr>
++              <tr>
++                <td>If it is a complex spreadsheet, do not force it into XWiki.</td>
++                <td>Budget model, calculations, reporting workbook.</td>
++              </tr>
++              <tr>
++                <td>If it was decided in a meeting or chat, summarize it in XWiki.</td>
++                <td>Decision record linked from meeting notes.</td>
++              </tr>
++              <tr>
++                <td>If nobody owns it, do not migrate it as current content.</td>
++                <td>Mark as archive or leave in the old system until reviewed.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h3>Make leadership use the new structure</h3>
++
++          <p>
++            Adoption is much harder if important announcements and decisions still point only to Google Docs or Drive
++            folders. When leadership links to XWiki as the trusted source, the platform becomes part of the organization’s
++            daily rhythm.
++          </p>
++
++          <h3>Start with visible wins</h3>
++
++          <p>
++            The first XWiki spaces should be better organized than the Google Drive folders they replace. They should have
++            navigation, page templates, useful links, ownership, clear permissions and recent activity. Users need to feel
++            that XWiki is not just another repository, but a better way to understand the organization.
++          </p>
++
++          <h2 id="implementation">Practical XWiki features to implement early</h2>
++
++          <p>
++            The following XWiki improvements can make a Google Workspace transition easier to accept:
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>XWiki feature</th>
++                <th>Why it helps adoption</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>SSO with OIDC, SAML or LDAP</td>
++                <td>Reduces login friction and aligns XWiki with the organization’s identity system.</td>
++              </tr>
++              <tr>
++                <td>Page templates</td>
++                <td>Prevents blank-page confusion and creates consistent documentation habits.</td>
++              </tr>
++              <tr>
++                <td>Working group space model</td>
++                <td>Gives each team or community group a clear home.</td>
++              </tr>
++              <tr>
++                <td>Metadata fields</td>
++                <td>Adds owner, status, review date, audience and document type.</td>
++              </tr>
++              <tr>
++                <td>Comments and annotations</td>
++                <td>Supports discussion around pages without losing context.</td>
++              </tr>
++              <tr>
++                <td>Notifications</td>
++                <td>Keeps users aware of changes in the spaces they follow.</td>
++              </tr>
++              <tr>
++                <td>Structured applications</td>
++                <td>Replaces some spreadsheet-based lists with maintainable data-driven apps.</td>
++              </tr>
++              <tr>
++                <td>Approval workflows or change requests</td>
++                <td>Supports governance for official documents and sensitive content.</td>
++              </tr>
++              <tr>
++                <td>Office document integration</td>
++                <td>Allows attached office documents to be edited when page-based content is not enough.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h2 id="example-architecture">Example collaboration architecture</h2>
++
++          <p>
++            A realistic open collaboration architecture may look like this:
++          </p>
++
++          <table class="table table-bordered table-striped">
++            <thead>
++              <tr>
++                <th>Layer</th>
++                <th>Recommended role</th>
++              </tr>
++            </thead>
++            <tbody>
++              <tr>
++                <td>XWiki</td>
++                <td>Structured knowledge, documentation, governance, working group spaces, policies and decisions.</td>
++              </tr>
++              <tr>
++                <td>Nextcloud</td>
++                <td>General file storage, file sharing, sync clients and optional groupware.</td>
++              </tr>
++              <tr>
++                <td>ONLYOFFICE or Collabora</td>
++                <td>Office document editing for documents, spreadsheets and presentations.</td>
++              </tr>
++              <tr>
++                <td>Matrix/Element or Mattermost</td>
++                <td>Real-time messaging and team coordination.</td>
++              </tr>
++              <tr>
++                <td>Jitsi or Nextcloud Talk</td>
++                <td>Video meetings and calls.</td>
++              </tr>
++              <tr>
++                <td>Keycloak or existing identity provider</td>
++                <td>SSO, group mapping and identity lifecycle.</td>
++              </tr>
++              <tr>
++                <td>LimeSurvey</td>
++                <td>Advanced surveys and research-style data collection.</td>
++              </tr>
++            </tbody>
++          </table>
++
++          <h2 id="faq">FAQ</h2>
++
++          <h3>Can XWiki replace Google Workspace completely?</h3>
++          <p>
++            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 much better positioned as the structured
++            knowledge and documentation layer.
++          </p>
++
++          <h3>Can XWiki replace Google Docs?</h3>
++          <p>
++            It can replace many Google Docs that are actually long-term documentation: 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.
++          </p>
++
++          <h3>Can XWiki replace Google Drive?</h3>
++          <p>
++            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.
++          </p>
++
++          <h3>What is the best first step?</h3>
++          <p>
++            Start with one high-value pilot: 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.
++          </p>
++
++          <h3>How do you convince users to try XWiki?</h3>
++          <p>
++            Do not start by saying that XWiki is replacing everything. Start by showing that XWiki gives them a clearer,
++            more reliable place for trusted knowledge. The new platform should solve a visible problem: finding the right
++            document, knowing who owns it, understanding whether it is current and seeing related decisions in context.
++          </p>
++
++          <h3>What should remain in Google Workspace during transition?</h3>
++          <p>
++            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.
++          </p>
++
++          <h2 id="sources">Useful reference links</h2>
++
++          <ul>
++            <li><a href="https://workspace.google.com/">Google Workspace product overview</a></li>
++            <li><a href="https://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/">XWiki user features</a></li>
++            <li><a href="https://extensions.xwiki.org/xwiki/bin/view/Extension/App%20Within%20Minutes%20Application">XWiki App Within Minutes</a></li>
++            <li><a href="https://extensions.xwiki.org/xwiki/bin/view/Extension/OpenID%20Connect/OpenID%20Connect%20Authenticator/">XWiki OpenID Connect Authenticator</a></li>
++            <li><a href="https://store.xwiki.com/xwiki/bin/view/Extension/OnlyOfficeConnectorApplication">XWiki ONLYOFFICE Connector</a></li>
++            <li><a href="https://store.xwiki.com/xwiki/bin/view/Extension/Collabora%20Connector%20Application%20%28Pro%29/">XWiki Collabora Connector</a></li>
++            <li><a href="https://extensions.xwiki.org/xwiki/bin/view/Extension/Nextcloud%20Application/">XWiki Nextcloud Application</a></li>
++            <li><a href="https://nextcloud.com/">Nextcloud</a></li>
++            <li><a href="https://www.onlyoffice.com/docs">ONLYOFFICE Docs</a></li>
++            <li><a href="https://www.collaboraonline.com/">Collabora Online</a></li>
++            <li><a href="https://mattermost.com/">Mattermost</a></li>
++            <li><a href="https://element.io/">Element / Matrix</a></li>
++            <li><a href="https://jitsi.org/">Jitsi</a></li>
++            <li><a href="https://www.limesurvey.org/">LimeSurvey</a></li>
++            <li><a href="https://www.keycloak.org/">Keycloak</a></li>
++          </ul>
++
++        </article>
++      </div>
++    </div>
++  </section>
++
++  <section class="cta-section" aria-labelledby="google-workspace-xwiki-cta-title">
++    <div class="container">
++      <div class="cta-panel">
++        <h2 id="google-workspace-xwiki-cta-title">Planning a transition from Google Workspace to XWiki?</h2>
++        <p>
++          Agnease can help evaluate what should move to XWiki, what should remain in office collaboration tools,
++          and how to design the right structure, permissions, templates, SSO and migration approach.
++        </p>
++        <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request a consultation</a>
++      </div>
++    </div>
++  </section>
++
++{{/html}}
++{{/velocity}}