Google Workspace integration is the process of connecting a custom domain to Gmail so businesses can send and receive professional email while leveraging Google’s collaboration tools. The setup involves domain verification (TXT), mail routing (MX), and email security hardening with SPF, DKIM, and DMARC. This guide provides SMEs, agencies, and developers with a validated step-by-step workflow covering sign-up, DNS configuration, migration, and monitoring.

Moving to Google Workspace is one of the fastest ways to give every employee a professional business email on a custom domain while utilising Gmail for business and the rest of Google’s collaboration stack.

This guide walks SMEs, agencies, and developers through a proven Google Workspace integration workflow. By the end, you’ll have a validated setup plan that covers sign-up, domain verification, MX/DNS changes, deliverability hardening, migration, and live testing.

Quick Preflight Checklist

Before touching any DNS record, make sure you have the following on hand:

  • Admin access to your domain registrar or DNS host (cPanel, managed DNS, or equivalent).
  • An inventory of current mail senders and the exact MX, SPF, and DKIM records already published.
  • A primary Google Workspace admin account plus billing details (start with Google’s 14-day trial).

Completing this checklist minimises downtime and prevents SPF/DKIM clashes during cutover. Free tools such as dig, MXToolbox, and the Google Workspace setup wizard help confirm every change.

Also Read: Improve Collaboration with Google Workspace – Now at Crazy Domains!

Step-by-Step Setup: Sign up to Verified Inbox

The following sequence has been field-tested on dozens of client roll-outs. Take it step by step and you will send and receive mail on Gmail for business with zero guesswork.

Sign up & Initial Setup in Google Workspace

Start the signup flow at workspace.google.com. Enter your business name and user count, and choose “Use my own domain” (or buy a new one directly in the wizard). Create the first admin user and keep the 14-day trial active so you can test DNS changes before any billing starts. The result is a fresh Workspace tenant with Gmail for business ready to be activated.

Verify Domain Ownership (TXT)

Google immediately provides a unique TXT token. Copy it exactly—name/host is often “@” and the value begins with google-site-verification=. In your registrar’s DNS editor:

  1. Add a TXT record with the supplied value.
  2. Save, then wait for propagation (anywhere from a few minutes to 48 hours).
  3. Click “Verify” in the admin console.

If verification fails, re-check for typos, extra quotes, or adding the record under the wrong subdomain. Use an external DNS lookup to confirm the TXT string is publicly visible before trying again.

Configure MX Records for Mail Routing

Once ownership is confirmed, replace any existing MX records with Google’s. As of mid-2025, many new Workspace tenants use a single MX entry:

Host/Name: @ Value: SMTP.GOOGLE.COM Priority: 1

Legacy tenants may require the classic five-record set (ASPMX.L.GOOGLE.COM, etc.). Always follow the exact values shown in your admin console. Steps:

  1. Remove all previous MX entries.
  2. Add Google’s MX record(s) with the stated priorities.
  3. Save and allow propagation.
  4. Run an MX lookup and send a test message from an external account to confirm routing.

Correct MX configuration unlocks Google’s built-in spam controls and keeps your professional business email flowing reliably.

Enable Gmail, Create Users, Groups and Aliases

Back in the admin console, assign a Gmail license to each user you create. For shared addresses, create Groups (e.g., sales@)—they are free and avoid extra licences. Equip users with the Gmail web app or native mobile apps for the best Workspace experience. Set 2-step verification as mandatory for all admins and place users into organisational units if you need policy segmentation.

Also Read: How to Maximise Business Productivity with Google Workspace

Mailbox Migration and Cutover Best Practices

Most teams move legacy mail in parallel with DNS changes:

  1. Lower your old MX record’s TTL to 300 seconds at least 24 hours before cutover.
  2. Pilot a small batch of users using Google’s data migration tool or IMAP migration.
  3. Validate SPF and DKIM on pilot accounts, then migrate the rest.
  4. Keep legacy MX details handy in case you need to roll back quickly.

Don’t forget non-human senders—CRMs, marketing platforms, servers—when drafting SPF/DKIM rules. Omitting them is the most common source of post-migration bounces.

Post-setup Deliverability & Security (SPF, DKIM, DMARC)

With mail now routing through Google, lock down sender identity to stop spoofing and protect your reputation.

SPF

Publish a single SPF TXT record that authorises Google and any third-party senders, for example:

v=spf1 include: _spf.google.com include: _spf.your-crm.com -all

Keep total DNS lookups under 10 and use an SPF checker to validate.

DKIM

In the admin console, click “Authenticate email”, generate a 2048-bit DKIM key, then add the TXT record at the selector Google provides. After propagation, enable signing and send a test email—headers should show DKIM=PASS.

DMARC

Start with a non-blocking policy:

v=DMARC1; p=none; rua=mailto:[email protected]; fo=1

Review aggregate reports for a week or two, fix any misaligned senders, then tighten to p=quarantine or p=reject.

Troubleshooting & Monitoring

If Google still can’t verify your domain or mail is bouncing, revisit the basics:

  • TXT/MX record values, host names, and TTL settings.
  • Conflicting legacy records left in place.
  • MX lookups and Gmail message headers to confirm SPF/DKIM results.

Free tools such as MXToolbox, Google’s CheckMX, and the Workspace status dashboard will pinpoint most issues. Monitor mail flow for at least 72 hours post-cutover and keep stakeholders updated on any anomalies.

When to Get Help and Managed DNS Option

Call in an expert if you are dealing with:

  • Multi-domain ecosystems
  • Legacy on-premise mail servers
  • Terabyte-scale email archives

Consider a Managed DNS service when you want to:

  • Reduce risk by consolidating domain registration and DNS management in one place
  • Simplify DNS edits with a single, user-friendly interface
  • Support SME teams that don’t have full-time IT staff

Professional Email Made Easy with Google Workspace

You now have a clear flight plan: preflight inventory, TXT verification, MX cutover, SPF/DKIM/DMARC hardening, plus migration and monitoring.

Small teams can finish Google Workspace integration in an afternoon; larger organisations should schedule phased migrations and thorough testing. Ready to give every user a professional business email on a custom domain? At Crazy Domains, we make it simple with managed DNS, guided Google Workspace setup, and ongoing support—so your business runs smoothly from day one.

Sign up now!