Migration Service

Nextcloud Migration Service: From Google, Microsoft or Dropbox

Moving a company onto Nextcloud is a four-week project when it is done right and a bad month when it is not. MassiveGRID's migration service plans and runs the move from Google Workspace, Microsoft 365, Dropbox, a self-hosted Nextcloud or another provider onto a Nextcloud Hub plan or a dedicated Nextcloud Enterprise instance: files with their structure and permissions, mail, calendars, contacts and the external shares that would otherwise break, with a cutover you can schedule and a rollback you will not need.

Request a Migration Quote How It Works

Sources covered

4 weeks

Typical project, 10 to 50 users

Mail lost at cutover

30 days

Old suite kept read-only

What we migrate

By source

	Google Workspace	Microsoft 365	Dropbox	Another Nextcloud
Files and folder structure	✓	✓ OneDrive and SharePoint	✓	✓
Version history	Partial latest versions; history on request	Partial latest versions; history on request	Partial latest versions	✓
Internal shares and permissions	✓ rebuilt as group and folder permissions	✓ rebuilt from library and folder permissions	✓	✓
External share links	✓ inventoried and recreated	✓ inventoried and recreated	✓ inventoried and recreated	✓
Mail	✓ Gmail over IMAP	✓ Exchange over IMAP or export	—	✓
Calendars and contacts	✓ CalDAV and CardDAV	✓ export and import	—	✓
Documents in native formats	✓ converted to DOCX, XLSX, PPTX	✓ as is	✓ as is	✓
Users and groups	✓	✓	✓	✓
Google Sites, AppSheet, Vault; Intune, Power Platform	— no equivalent; we flag them in discovery	— no equivalent; we flag them in discovery

Partial rows are honest limits of the source platforms' export tools, not of Nextcloud. Hub 26 Winter's export and import tooling makes Nextcloud-to-Nextcloud moves the simplest case.

How a migration runs

Five steps, one owner on each side

Step 1

Discovery

We inventory users, data volumes, shared drives and libraries, external share links, mail sizes, calendars and the tools with no Nextcloud equivalent. You get a plan with dates and a list of decisions.

Step 2

Pilot

A pilot group gets the new workspace with a copy of their data and works on it for a week or two while the rest of the company carries on. This is where the folder structure and permissions are settled.

Step 3

Data move

Files, permissions and documents move in bulk with a delta pass before cutover so nothing edited in the last days is lost. External links are recreated and a redirect list is produced for the people who sent them.

Step 4

Mail and calendar cutover

Mailboxes are copied, calendars and contacts imported, phones and clients reconfigured, then MX records switched at a time you choose. The old mailboxes keep receiving in parallel until you are sure.

Step 5

Hand-over and decommission

Training sessions for the team, an admin hand-over, the old suite in read-only for 30 days, then cancellation. You keep the inventory and the redirect list.

What it costs

Scoped per project

Migrations are scoped and quoted after discovery, because a 15-person studio with a tidy Drive and a 200-person firm with eleven years of SharePoint are not the same project. The quote covers the engineer time for the steps above; the Nextcloud plan itself is priced separately at the published Hub plan or dedicated instance rates. For organisations taking Sovereign Workspaces, migration is part of the service.

Teams that would rather run the move themselves have everything they need on this site: the Google Workspace export guide, the Microsoft 365 migration guide, the Dropbox migration guide, the first-month walkthrough and the onboarding playbook. Support is a ticket away on every plan if a step goes wrong.

What you provide

The short list

An administrator account on the source suite for the duration, with export rights.
One decision-maker for folder structure, permissions and the cutover date.
Access to DNS for the MX and verification records, or someone who has it.
The list of things that must not break: client-facing share links, shared mailboxes, calendar invitations for events already scheduled.
A plan: order the Nextcloud Hub plan for the pilot users, or request a dedicated instance quote, before discovery starts.

Questions

Migration, Answered

About four weeks for a company of 10 to 50 users: a week of discovery and pilot setup, a week or two of pilot, the data move with a delta pass, then mail cutover and training. Larger organisations and those with years of SharePoint take longer; discovery gives you the date.

No. Mailboxes are copied before the switch, the old mailboxes keep receiving in parallel, and MX records are changed at a time you choose. The last messages are synced across after the switch and the old suite stays read-only for 30 days.

Public share links point at the old provider and stop working when the account closes, so we inventory them during discovery, recreate the important ones as Nextcloud links, and give you a redirect list for the people who sent them. Internal shares are rebuilt as permissions.

They are exported as DOCX, XLSX and PPTX and open in Nextcloud Office. Everyday documents convert cleanly; spreadsheets with Apps Script and documents built on Google-only add-ons are flagged in discovery so nobody is surprised.

Yes, and it is the simplest case: Nextcloud's export and import tooling (since Hub 26 Winter) moves users, files, shares, calendars and contacts between instances, and we handle the DNS and the cutover.

The guides and support are. The engineer-run service is scoped and quoted per project. Migration is included in Sovereign Workspaces, MassiveGRID's managed single-tenant deployment.

Tell us where you are coming from

Google Workspace, Microsoft 365, Dropbox or another Nextcloud: send the user count and the source, and we come back with a discovery call and a plan with dates.

Request a Migration Quote See Nextcloud Hub Plans