Nextcloud is not a Google Workspace clone. That is the point and the trap.

On June 5, 2026, Nextcloud Hub 26 Winter is still the current release, while Hub 26 Spring and Euro-Office are four days away. That timing matters: Nextcloud can replace a meaningful part of Google Workspace, but treating it as a one-to-one clone is how migrations go wrong.

I already wrote the personal migration story. This is the architecture map I would use for a Dutch or EU SME before moving a team.

TL;DR

• Nextcloud is strongest where the job is files, sharing, desktop sync, WebDAV, calendar and contacts. That is the clean replacement zone.
• Nextcloud Mail is not Gmail hosting. It is a mail client for IMAP/SMTP infrastructure, so business email remains a separate architecture choice.
• Office editing, Talk video, mobile behavior, storage, identity and compliance can work well, but only after explicit design decisions.
• Sovereignty improves control over hosting, jurisdiction, subprocessors and exit options. It does not create backups, legal hold, DLP, deliverability or user support by itself.
• For many SMEs, the best answer is hybrid: managed Nextcloud for collaboration, specialist mail hosting, and Google Workspace or Microsoft 365 retained only where the workload still justifies it.

Table of contents

• Compare jobs, not logos
• Clean fits: files, sync, calendar and contacts
• The email boundary is non-negotiable
• Office, Talk and adjacent apps are architecture choices
• Operations are part of the product
• Sovereignty changes ownership, not workload
• Decision map for EU and Dutch SMEs
• Key takeaways

Compare jobs, not logos

The mistake is asking whether Nextcloud "replaces Google Workspace" as one object. Google Workspace is not one object. It bundles Gmail, Drive, Docs, Sheets, Slides, Calendar, Meet, Chat, Forms, Sites, Keep, AppSheet, Admin Console, Gemini features and security controls under one subscription and support model.

Nextcloud is a different shape. Nextcloud Files covers file sync and share. Nextcloud Groupware covers Calendar, Contacts, Mail and Deck. Nextcloud Office gives browser-based editing through an office backend. Nextcloud Talk covers chat, calls and rooms. The platform can integrate with LDAP, Active Directory, OIDC and SAML, but it is not a full Workspace Admin clone.

That distinction is not a weakness. It is the whole point. Google sells a bundled SaaS workplace. Nextcloud gives you a collaboration platform you can host yourself or buy from a managed provider. The strength is control over the parts you choose. The trap is pretending the missing parts do not need owners.

Clean fits: files, sync, calendar and contacts

Files is where Nextcloud usually feels boring in the good way. Nextcloud Files is built around storage, sharing, public links, WebDAV, desktop and mobile access, external storage and enterprise controls. If your Workspace pain is "I want team folders and client file links under EU control", Nextcloud is a serious answer.

The sync story is also credible, with one mobile caveat. The user manual describes the normal desktop model: create a local folder, put files there, and changes flow through the desktop clients. The same page says full bidirectional sync is not yet fully implemented in the Android client. That is not fatal, but it belongs in a pilot if field staff expect a phone to behave like a laptop.

Calendar and Contacts are good fits because they speak old, useful standards. Nextcloud Groupware exposes calendar and contact functionality that maps to CalDAV and CardDAV clients, and its product page documents shared calendars, appointment scheduling, resource booking, address books and device sync. That is usually enough for SMEs that need shared calendars and address books, not a full Google Calendar appointment-booking stack with every admin control.

The practical pilot should be small and annoying on purpose: one Windows laptop, one Mac, one iPhone, one Android phone, a folder with many small files, a folder with large Office documents, a shared client link, a deleted folder restore and one calendar invite to an external contact. A migration that survives that test has a much better chance than a demo built from empty folders.

The email boundary is non-negotiable

This is the line I would put in every migration document: Nextcloud Mail is not Gmail. Nextcloud's own Groupware page says it directly: "Nextcloud Mail is a client for IMAP-infrastructure; Nextcloud does not include a mail server." The Mail admin docs are written around IMAP, SMTP and Sieve servers, and even account delegation depends on mail-server support.

That means Nextcloud does not receive mail for your domain by itself. It does not maintain sender reputation. It does not sign DKIM unless the underlying mail server does. It does not solve DMARC alignment, SPF includes, MTA-STS, TLS-RPT, spam filtering, abuse handling or mailbox backups. I covered that operational burden in more detail in self-hosted email in 2026.

There are four honest designs:

• Managed privacy-oriented mail provider plus Nextcloud for files, calendars and collaboration.
• Self-hosted mail plus Nextcloud, but only if someone owns DNS, deliverability, monitoring, spam filtering and incident response.
• Google Workspace or Microsoft 365 kept for mail while Nextcloud replaces files and collaboration.
• Nextcloud Enterprise with a supported mail-server path, since the Groupware page says Enterprise can optionally include Dovecot Pro or Stalwart as mail server or MTA.

Keeping Gmail or Exchange Online for mail while moving files to Nextcloud is not a failed migration. It is architecture. For many teams, mail deliverability is a poor place to prove a sovereignty point.

Office, Talk and adjacent apps are architecture choices

Browser-based office editing is possible in Nextcloud, but it is not automatic. Nextcloud's admin manual says Nextcloud Office is based on Collabora Online Development Edition in the community path, with a more stable and scalable Collabora Online Enterprise version available through support. Collabora describes CODE as suitable for testing, home use or small teams and "not recommended for production environments."

ONLYOFFICE is a valid alternative, but it is also an architecture component. Its connector requires an ONLYOFFICE Docs server that Nextcloud and clients can reach, JWT configuration and certificate hygiene. Simple .docx, .xlsx and .pptx files may be fine. Client contracts, complex spreadsheets, macros, tracked changes and layout-sensitive templates need a real-document pilot.

Euro-Office is the current-date footnote. Nextcloud announced that the first stable Euro-Office release will be available on June 9, 2026 and integrated with Hub 26 Spring. For a June 5 article, that makes it upcoming, not current production evidence. I would watch it closely, but I would not base an SME migration plan on a release that has not shipped yet.

Talk has the same pattern. Small internal calls are realistic. For larger meetings, the Talk scalability docs explain the High Performance Backend: an SFU where each participant sends one stream to the backend, which distributes streams to the call. The same docs say HPB typically scales to 30 to 50 or more active participants and hundreds of passive participants, with bandwidth as the limit.

Notes, Deck, Collectives and Forms are useful as lightweight replacements. Groupware documents Deck as Kanban-style boards with assignments, due dates, attachments and exports. Nextcloud Forms has covered survey-style workflows since its 2020 launch announcement. That does not make them replacements for AppSheet, Apps Script, Sites, enterprise form governance or cross-suite search.

Operations are part of the product

SaaS hides operations in the subscription. Nextcloud moves the line: either you operate it, or you pay a managed provider to operate it. That bill is still real.

Nextcloud upgrade docs recommend regular maintenance releases, step-by-step major upgrades, a fresh backup before upgrade and third-party app compatibility checks. That matters because business-critical apps are often outside bare Files: Office, Talk, Deck, Notes, Forms, SSO, external storage and notification services.

Backups are not just "copy the data directory." The restore docs cover configuration, data, database and themes. If you use primary object storage, file content lives as objects while names, folders and metadata depend on the database. A backup of one without the matching other is not a restore plan.

Background jobs deserve the same attention as storage. Nextcloud's background job docs call AJAX the least reliable mode and recommend cron for multi-user instances, especially with Activity or external storage. If cron stalls, users experience it as missing notifications, stale previews, delayed cleanup or weird app behavior.

The cost map for a serious deployment is longer than the install guide:

• Updates, app compatibility checks and rollback plans.
• Application-consistent backups, restore tests and retention policy.
• Database, Redis or file-locking health, PHP-FPM, web server and TLS monitoring.
• Storage growth, object-store consistency, preview generation and egress costs.
• Office backend sizing, WOPI/JWT settings, certificates and updates.
• Talk HPB, TURN/STUN, signaling, bandwidth and mobile push expectations.
• User support for sync conflicts, external shares, mobile quirks and deleted files.
• Migration design: ownership of shared folders, old Drive links, offboarding and export retention.

None of this means Nextcloud is too hard. It means "self-hosted" is a product commitment, not a checkbox.

Sovereignty changes ownership, not workload

The sovereignty case is real. Self-hosting or using a Dutch/EU managed Nextcloud provider changes who can administer the system, where data and backups sit, which subprocessors are involved, how export works and which corporate law applies. That is the same jurisdiction logic I covered in EU data sovereignty and the CLOUD Act.

It does not make you compliant by itself. GDPR, NIS2 readiness, incident response, DLP, endpoint management, legal retention, mail deliverability and user training remain work. Nextcloud has useful building blocks: logging and optional admin_audit, data retention controls and file access control workflows. Google has packaged controls like Vault retention and eDiscovery, client-side encryption and Context-Aware Access with DLP in specific editions.

Those are different control models. Nextcloud gives more direct control over the platform. Google and Microsoft give a larger packaged admin and compliance surface. If your legal requirement is "keep files under EU operational control", managed Nextcloud can be a good fit. If your requirement is "run legal holds, eDiscovery, endpoint rules and DLP under one admin console", vanilla Nextcloud is not the same product.

Managed Nextcloud is often the sane middle path. Dutch and EU providers such as ProcoliX, BIT, The Good Cloud, Cloud68 and Hetzner Storage Share illustrate the range from budget storage to supported hosting. This is where the procurement conversation from the Open Cloud Alliantie article becomes practical: ask about parent company, data location, backups, support, office backend, Talk HPB, subprocessors and exit.

Decision map for EU and Dutch SMEs

For most SMEs, I would make the decision by workload, not ideology.

My default recommendation for a Dutch SME is conservative: start with managed Nextcloud for files, sharing, calendar and contacts; keep mail with a specialist provider unless there is a clear reason to move it; pilot office editing with real client documents; decide later whether Talk replaces external video meetings. That path captures the sovereignty win without pretending every SaaS feature has a one-click open-source twin.

Key takeaways

• Nextcloud is a strong replacement for file collaboration, sync, calendar and contacts when those jobs are the actual problem.
• Nextcloud Mail is a client, not a business mail-hosting platform. Own that decision separately.
• Office editing, Talk scale, object storage, SSO, backups, monitoring and support are design choices, not defaults.
• Digital sovereignty changes legal and operational control, but it does not remove GDPR work, DLP, eDiscovery, endpoint management or mail deliverability.
• The honest SME answer is often hybrid: Nextcloud where control matters, specialist services where operational depth matters, and Google Workspace or Microsoft 365 where the bundled suite is still doing real work.