🌭
Menu
← Field notes

Primary-source migration plan · September 3, 2026

Google Drive to Nextcloud: migrate the collaboration system, not just the files.

A ZIP can preserve useful content while losing ownership, sharing, native-document behavior, comments, versions, and the operating system around it. Make those gaps explicit before cutover.

Individual and organization exports are different lanes

Google Takeout creates an archive for data available to one account. Google Workspace's organization export requires an eligible super administrator and can include shared-drive and other customer-owned data. Google says exports have a snapshot boundary, can complete with errors, and may require remediation.

Downloading data does not delete the Google source. Record the authorized scope, export snapshot, archive access and expiry, final delta, source-retention window, and deletion owner.

A five-stage migration

  1. 1

    Choose the export authority

    Use individual Takeout only for data the account can export. For organization-wide Workspace data, confirm eligible super-administrator authority, the exact users and services, shared-drive scope, snapshot timing, completion errors, and final-delta method.

  2. 2

    Inventory behavior, not just bytes

    Count My Drive and shared-drive items, Google-native files, versions, comments, shortcuts, internal and external permissions, public links, large files, clients, APIs, automations, and office-editor dependencies.

  3. 3

    Decide every conversion

    Select and test formats for Docs, Sheets, and Slides. Record what happens to formulas, pivots, validation, charts, comments, suggestions, versions, links, Forms, Drawings, Sites, Vids, and shortcuts.

  4. 4

    Pilot access and clients

    Start with synthetic data, then a small authorized sample in a non-production destination. Rebuild ownership and groups; test sharing, search, preview, desktop/mobile sync, conflicts, offline work, the largest file, and a constrained network.

  5. 5

    Prove operation and rollback

    For self-hosting, name owners and restore configuration, apps, data, theme, and database. Reconcile counts and meaningful hashes, run a final delta, retain Google through the rollback window, then remove temporary exports.

Managed Nextcloud
Confirm provider limits, region, support, export, backup, restore, office integration, identity, apps, and exit terms. Managed hosting transfers operating work; it does not prove migration fidelity.
Self-hosted Nextcloud
Own identity, storage, database, email, TLS, file-size and temporary-space limits, backups, restore, monitoring, upgrades, app compatibility, security response, support, and incidents.

License the exact deployed system

The Nextcloud server repository states AGPL-3.0-or-later unless otherwise noted. That does not establish the terms of every app, hosted service, office integration, or enterprise feature.

Record each component, version, edition, use, and license. Get qualified advice when modification or network use creates a commercially material obligation.

Primary sources

Run the migration ledger

The free v0.16.0 kit contains the authority record, source inventory, conversion and access matrix, destination operating gate, representative pilot, reconciliation, cutover, and rollback checks.

Run the free migration kit ↗Request migration helpBuild a software shortlist

Get the next decision note

One maintained recipe each week. Explicit opt-in, no vendor-paid ranking, unsubscribe any time.