Nextcloud Office with Euro-Office Document Server

Test both browser editors against your own documents before choosing, since feature lists rarely settle the question. The architectures differ first. Nextcloud Office uses a dedicated Document Server, which Nextcloud reaches through the Euro-Office connector app, so the Document Server is a separate service that you install, patch, size and monitor. Collabora Online works as a WOPI host: Nextcloud hands editing sessions to it through the WOPI protocol, and it also runs as its own service with its own routing and update path. Both options sit outside the Nextcloud server, so both add a component to your change process, your certificates and your incident runbooks.

The test set matters more than the tool. Collect real files from the teams that will edit them: templates, documents with tracked changes and comments, spreadsheets with formulas, named ranges and pivot tables, presentations with custom masters, and any file with embedded objects that your policy allows. Cover every format your users open, including DOCX, XLSX, PPTX, ODT, ODS and ODP. For each file, open it in the browser, edit it with several users at once, save, reopen, and compare the result in the desktop application. Record each lost or altered feature separately, so the results point to a specific gap. Include files from legal, finance and HR if they carry regulated content, and run the test through your real network path, reverse proxy and TLS settings.

Licensing and support terms are not visible in a feature comparison, so put the questions to each vendor in writing before deciding. Ask which license terms apply to every server component, connector and client package you will deploy, and whether any feature you need sits behind a paid edition. Ask what commercial support is offered, at which tiers, with which response commitments, and whether it covers your Nextcloud major version and your proxy configuration. Ask how security notices are published, how long each release line is maintained, and whether a supported upgrade path exists. Confirm these answers with the publisher and file them with procurement and legal, next to the quote.

The operating load follows the architecture. Count the services each option adds, the resources they need at your expected number of concurrent editors, and how a restart or update affects open sessions. Measure memory, CPU and response times during the pilot and treat vendor sizing guidance as a starting point. Check which logs and metrics each service exposes to your monitoring stack, and name the people who will read them. Then plan the update cadence. Nextcloud publishes a new major version every four months, so the office component must be retested against each one, and the connector version must be confirmed before the server is upgraded. Assign one owner for the Document Server and one owner for the test set.

Editing sessions in Nextcloud Office only run for users who already exist in Nextcloud, so the identity decision comes before the office decision. Nextcloud's LDAP app lets LDAP and Active Directory users appear in Nextcloud and sign in with their directory credentials. Nextcloud also documents OpenID Connect and SAML user authentication backends. Choose one of these paths with the identity team before the Document Server is sized or connected, because the same account, group and attribute model will decide who can open, edit and share documents. Confirm which groups are mapped to Nextcloud groups, how deprovisioned users are handled, and whether accounts that leave the directory lose access to documents they co-own.

Sharing permissions need their own test plan. Create a document in a team folder, share it with a user, a group and a guest, and then try each combination of read, edit, share and download rights. Confirm that a user who can edit cannot re-share beyond what the owner allows, and that removing a share ends an open editing session. Guest accounts deserve separate cases because they are often created by external collaborators outside the directory. Check which guest accounts can open office documents at all, and whether link shares to documents being co-edited behave the same way as user shares.

File version handling is where co-editing problems usually show up. Test two people editing the same DOCX or XLSX file, saving at different times, and reopening the file from the desktop sync client and the web interface. Confirm that version history records the saves you expect, that restoring an earlier version works for a document that was edited in real time, and that conflicting sync copies do not silently replace the work. Set retention for versions and trash to match your records policy before go-live, because the number of stored versions directly affects storage growth.

The most important confirmation is where document content is processed and stored in your environment. Nextcloud Office sends document content from the Nextcloud server to the Document Server for rendering and editing, so both components, their network paths and their logs must sit inside infrastructure you control. Ask Nextcloud and Euro-Office to confirm, in writing, which data the Document Server keeps, for how long, and whether temporary copies are written to disk. Verify this with your own network capture and log review in a test environment. Record the answers in your data flow documentation, since auditors and data protection teams will ask the same questions.

Nextcloud Office has two moving parts that must stay in step: the Nextcloud server and the dedicated Document Server, linked by the Euro-Office connector app. Plan Document Server updates as part of every Nextcloud upgrade step, so the editing service and the server move through each release together. Nextcloud publishes a new major version every four months and supports each one for a year through monthly maintenance releases. Because the documented rules forbid skipping major releases, an office deployment passes through each major version in sequence, and each step needs its own compatibility check.

The supplied schedule sets the timing. Nextcloud 33 is supported until February 2027, Nextcloud 34 until June 2027, and Nextcloud 35 (Hub 26 Summer) was released on 16 September 2026 with end of life in September 2027. Nextcloud 36 (Hub 27 Winter) is scheduled for 17 February 2027. An installation still on Nextcloud 33 in early 2027 would therefore move to 34, then 35, then 36, one major version at a time. Build that sequence into the roadmap now, and confirm the current support dates on the Nextcloud maintenance and release schedule before fixing any change windows, since schedules can shift.

Each step follows the same documented sequence. Back up before every upgrade, covering the database, the data directory and the configuration, and confirm that a restore has been tested on a copy. Disable third-party apps until each is confirmed compatible with the target release, and treat the Euro-Office connector app as one of those apps to verify. Run the upgrade on a staging clone that matches production, including the Document Server, then test document opening, co-authoring and saving in DOCX, XLSX and PPTX before the production change. Confirm the Document Server build against the Nextcloud release in the Euro-Office documentation.

Decide who owns each step before the first upgrade is due. Your team may hold the work internally, or it may buy an upgrade under a fixed-scope agreement or a retainer, which covers ongoing maintenance. Ask any partner to state in writing which Nextcloud and Document Server versions the work covers, how the connector app is checked, and how rollback is handled. Nextcloud's pricing page states that its Standard tier includes one year of maintenance, while Premium adds a maintenance lifecycle of five years or more. If your office service must stay on a supported release for longer than the community window, price that difference into the decision.