Leaving Google Workspace means deliberately ending a dependency on a platform that handles email, file storage, calendar, video conferencing and collaborative documents in a single integrated environment. For most organisations, the decision is not purely technical: it is driven by data sovereignty obligations under the GDPR, exposure to the US CLOUD Act, rising subscription costs, or a combination of all three. Understanding what the exit actually costs, where the migration gets hard, and how to sequence the transition is what separates a successful switch from a failed one.
What it actually costs to leave Google Workspace
The direct financial cost of leaving breaks down into three categories: export fees, lost productivity during transition, and the price of replacement software.
Google does not charge for using Google Takeout to export user data, but that is only part of the story. Once data volumes rise above a few gigabytes, organisations running workloads connected to Google Cloud storage encounter egress charges.
Beyond egress, the real cost is human time. Remapping shared drives, recreating permission structures, converting Workspace-native file formats and retraining staff on new tools typically adds up to several weeks of internal IT effort, even for mid-sized teams. Organisations that underestimate this consistently overshoot their migration budgets.
Subscription overlap is a further cost that is easy to overlook. During a phased migration, most organisations pay for both the legacy Google Workspace licences and the new platform simultaneously for one to three months per department. For a 100-user company on a Business Standard plan, that parallel-run period can cost several thousand euros in duplicate licensing.
Which data is hardest to migrate
Not all data types leave Google’s ecosystem cleanly. The difficulty scales directly with how deeply a file type relies on Google-proprietary features.
| Data type | Migration difficulty | Primary reason |
|---|---|---|
| Gmail (IMAP/MBOX) | Low | Standard IMAP protocol; most mail servers accept direct import |
| Google Calendar | Low to medium | ICS export works, but shared calendar permissions need manual rebuild |
| Google Docs and Slides | Medium | DOCX/PPTX conversion loses advanced formatting and embedded comments |
| Google Sheets with Apps Script | High | Apps Script macros have no equivalent in LibreOffice or Nextcloud; must be rewritten |
| Google Sites | Very high | No export format; pages must be manually rebuilt in the target platform |
| AppSheet applications | Very high | Proprietary low-code environment; no migration path exists |
The European Data Protection Board has been explicit on this point: “Data portability is not just a technical feature, it is a fundamental right under GDPR Article 20. Organisations must be able to retrieve their data in a structured, commonly used and machine-readable format without obstruction.” In practice, Google Takeout delivers on this for Gmail and Contacts, but falls short for deeply integrated Workspace-native content.
Shared Drive structures deserve special attention. When Google Drive folders are owned by individual user accounts rather than a Shared Drive, exporting them via Google Takeout attaches the export to that user’s account. If the user has already left the organisation, recovery requires administrative intervention and sometimes Google Support involvement.
A phased Google exit: how to structure the transition
A phased approach reduces risk by allowing teams to adapt incrementally rather than facing a hard cutover. ENISA has noted that “vendor lock-in is one of the top cloud risks organisations face,” and a phased exit is the primary operational tool for managing that risk without disrupting daily work.
Phase 1: Audit and inventory (weeks 1 to 4). Catalogue every service in active use, including third-party integrations that authenticate via Google OAuth. Identify Apps Script automations, Google Sites and AppSheet instances early, as these require the most lead time to replace.
Phase 2: Deploy the target platform in parallel (weeks 4 to 10). Stand up the replacement environment, whether that is a self-hosted Nextcloud instance or a managed deployment such as Qsentinel, and migrate a pilot department. File sync, email and calendar are the logical starting points because they have clean export paths and staff adapt to them quickly.
Phase 3: Migrate email and identity (weeks 8 to 16). Move MX records to the new mail infrastructure and redirect authentication away from Google OAuth. This is the most disruptive single step and should happen on a Friday evening with IT staff on standby.
Phase 4: Decommission Google services (weeks 14 to 24). Remove Google Workspace licences department by department after confirming data integrity. Retain read-only admin access to the Google Admin console until the final billing cycle closes.
France’s CNIL fined Google €150 million in January 2022 for cookie consent violations, a reminder that regulatory pressure on Google’s data practices is not theoretical. Organisations in regulated sectors, particularly finance and healthcare, face their own GDPR accountability obligations under Articles 5 and 28, which make the sovereignty case for migration concrete rather than abstract.
FAQ
Can I export all my Google Workspace data for free?
Google Takeout lets you export most user data at no direct charge, but egress fees apply when transferring large volumes out of Google Cloud storage, and some Workspace-native formats convert imperfectly to open standards.
How long does a full Google Workspace migration take?
For a team of 50 to 200 users, a well-planned phased migration typically takes three to six months, depending on data volume, application dependencies and the complexity of shared Drive structures.
Which Google Workspace apps have the worst vendor lock-in?
Google Sites, AppSheet applications and complex Google Sheets with Apps Script automation carry the highest lock-in risk because they have no direct open-standard equivalent and require rebuilding rather than converting.
Does GDPR give us the right to demand our data back from Google?
GDPR Article 20 grants data portability rights to individuals, and Google’s Data Processing Addendum obliges Google to return customer data upon contract termination. However, the format and completeness of that export varies by service.
Is a managed Nextcloud platform a realistic Google Workspace replacement?
Nextcloud covers files, calendar, contacts, video calls and collaborative document editing. Managed providers such as Qsentinel add enterprise support, post-quantum encryption and hosting in Swiss or on-premise environments, which addresses sovereignty requirements that Google cannot meet under US CLOUD Act jurisdiction.
Hoe Qsentinel dit oplost
Qsentinel is the managed Nextcloud Enterprise workspace, enhanced by Qsentinel with post-quantum encryption and sovereign private AI, hosted in Switzerland or on-premise, out of reach of the CLOUD Act.