Google Workspace migration

The manager of a small business with a handful of staff contacted us because they weren’t happy with their email service. The quality of the email itself wasn’t the problem: they wanted collaboration tools, a shared calendar and file sharing that would also be convenient to use outside the office. Their previous provider had no solution for this.

Starting point

  • Email: hosted with a traditional email provider, fewer than ten mailboxes. Staff read their mail almost exclusively in webmail, and no mail was stored locally.
  • Files: a small Linux PC in the office served as the file server, with three Samba shares. It worked well while everyone was in the office, but since remote working was introduced, people had to connect to it over a VPN, and Samba over the internet was often slow.
  • Users: almost everyone had already used Google products, so the interface wouldn’t have been unfamiliar to anyone.

Why Google Workspace?

After discussing their needs, we recommended Google Workspace, because a single package includes everything they needed:

  • email: Gmail,
  • personal and shared calendars: Google Calendar,
  • address book: Google Contacts,
  • file sharing: Google Drive, with shared drives,
  • video calls: Google Meet.

They chose the Business Standard plan, mainly for the larger storage (2 TB per user, pooled at company level) and the shared drives. Files on a shared drive belong to the company, not to individual users, so they aren’t lost when someone leaves.

Migration steps

Domain and DNS

After creating the Workspace account, we verified the domain with Google using a TXT record. Email was switched over by changing the MX records: from that moment, Google’s servers receive the mail. We added Google’s sending servers (include:_spf.google.com) to the SPF record, so that mail sent from Gmail wouldn’t get caught in recipients’ spam filters.

Email

As there was no locally stored mail, we only had to move the mailboxes on the old provider’s server. With so few mailboxes there was no need for a separate tool: we copied the mail from the old server over IMAP using the built-in data migration service of Google Workspace.

Files

To match the three shares on the file server, we created three shared drives in Google Drive and uploaded the data with a simple file copy. We installed the Google Drive desktop app (Drive for desktop) on every laptop, so everyone reaches the shared drives and their own drive from the file manager, the way they are used to.

The app shows when someone else is currently editing a Word or Excel file, which prevents two people from overwriting each other’s work – something that had happened before with the Samba shares.

Calendar, contacts, phones

No other data had to be moved: everyone uploaded their own contacts, and they started using the shared and personal calendars at this point. On the Android phones, it was enough to add the company Google account as a new account in the preinstalled Gmail app, and email, calendar and contacts appeared straight away.

Result

  • Files are available from anywhere without a VPN, and the office file server could be switched off.
  • The company uses a shared calendar and video calls without a separate service.
  • The interface was familiar, so people learnt it quickly.

Looking back from 2026

For a migration like this today, we would set up DKIM and DMARC alongside SPF from day one. Since February 2024, Google has required every sender to Gmail addresses to use SPF or DKIM, and bulk senders to use all three. In Workspace, the DKIM key can be generated in the Admin console, and it’s best to start DMARC with a p=none policy, watch the reports, and only tighten it afterwards.

Planning to move your email or file sharing? On the Infrastructure and operations page, we describe what we take on around email.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch