
Quick answer: Google Workspace setup involves four main steps: signing up for a plan at workspace.google.com, verifying your domain ownership, updating your domain's DNS records (MX, SPF, DKIM, DMARC), and creating user accounts. Most small businesses complete the process in under two hours. Costs start at approximately $6/user/month for Business Starter.
"I Expected a Week of IT Headaches" — How I Set Up Google Workspace Before Lunch
When I decided to move our six-person marketing agency in Austin, Texas off our old shared hosting email, I braced for a complicated setup. Our previous provider had taken three days and two support calls to configure. I cleared my entire morning. As it turned out, Google Workspace's setup wizard walked me through every step — including generating the exact DNS records I needed — and I had all six team members on their new @ourcompany.com Gmail accounts by 11:30 AM. The only thing I wish I had done differently was lower our DNS TTL the night before, which would have made the MX record switch propagate in minutes instead of the two hours it actually took. This guide documents the complete Google Workspace setup process, from choosing the right plan to configuring Gmail on desktop and mobile, setting up email authentication records, and migrating existing email without losing a single message. I have also included the specific DNS values and commands I used, so you can follow along exactly rather than hunting through documentation.

Google Workspace Plans — Which One Is Right for Your Business?
Google offers four business plans. For most small businesses, the choice comes down to Starter or Standard. Business Starter at approximately $6/user/month (annual) includes Gmail with 30GB of pooled Google Drive storage per user, Google Meet (up to 100 participants), Calendar, Docs, Sheets, Slides, and Forms. Business Standard at approximately $12/user/month increases pooled storage to 2TB per user, raises Meet capacity to 150 participants with recording, and adds noise cancellation and attendance tracking in Meet. Business Plus at approximately $18/user/month adds eDiscovery, audit logs, and Meet capacity up to 500 participants — features primarily relevant to larger or regulated organizations. Enterprise plans are custom-priced and include advanced security, DLP, and data residency controls. For a team of fewer than 20 people without specific compliance requirements, Business Starter is generally the right starting point and can be upgraded at any time.
PlanPrice (per user/mo, annual)StorageMeet CapacityBest ForBusiness Starter~$630GB pooled100 participantsSmall teams, startups, freelancersBusiness Standard~$122TB pooled150 + recordingGrowing teams, heavy Drive usersBusiness Plus~$185TB pooled500 participantsCompliance needs, larger teamsEnterpriseCustomUnlimited1,000 participantsLarge organizations, advanced security
Prices reflect publicly listed annual billing rates as of July 2026. Verify current pricing at workspace.google.com/pricing before purchasing.
5 Things to Know Before You Start the Setup
1. You Need a Domain Name — But You Do Not Need to Transfer It
Google Workspace requires a custom domain (e.g., yourcompany.com) to create business email addresses. If you already own a domain registered through GoDaddy, Namecheap, Cloudflare, or another registrar, you can use it with Google Workspace without transferring it. You simply add DNS records at your existing registrar pointing to Google's mail servers. Google's setup wizard supports direct integration with many popular registrars, meaning it can update your DNS records automatically if you grant it access — a feature I used with Namecheap that saved about ten minutes of manual DNS entry. If you do not yet own a domain, you can register one during the Google Workspace signup process or through a separate registrar. Domain registration typically costs $10-$20/year. Google also offers domain registration through Google Domains (now managed by Squarespace), though purchasing through a dedicated registrar generally gives you more flexibility.
2. Lower Your DNS TTL Before Making Any Changes
Before updating any DNS records, log into your domain registrar and lower the TTL (Time To Live) on your existing MX and TXT records to 300 seconds — about 5 minutes. TTL controls how long DNS resolvers cache your records. A lower TTL means changes propagate faster globally and, critically, that you can roll back quickly if you make an error. Make this change at least one hour before you plan to update your DNS records, to give the reduced TTL time to propagate. I skipped this step and spent two hours waiting for my MX record change to take effect — a mistake I will not repeat.
3. SPF: One Record Per Domain, No Exceptions
Your domain can have only one SPF record (a DNS TXT record starting with v=spf1). If you already have an SPF record from your current email provider, do not add a second one for Google Workspace — doing so will break SPF authentication and can cause your emails to be marked as spam. Instead, merge the Google include into your existing record. For example, if your current SPF record is v=spf1 include:mailgun.org ~all, the merged version should be: v=spf1 include:mailgun.org include:_spf.google.com ~all.
4. DMARC Deployment Should Be Gradual
DMARC is a policy that tells receiving mail servers what to do with emails that fail SPF or DKIM authentication. Many guides recommend setting p=reject immediately, but this is risky if any legitimate email source — a marketing tool, a CRM, a third-party sender — is not yet authenticated. Start with p=none to monitor without blocking, review the aggregate reports for two to four weeks, then move to p=quarantine, and finally to p=reject. This staged approach takes a few extra weeks but prevents deliverability problems that can be difficult to diagnose after the fact.
5. Keep Your Old Email System Running During Migration
Do not cancel or disable your existing email hosting until you have confirmed that Google Workspace is receiving and sending email correctly. During the transition period — typically 24-48 hours after switching your MX records — run both systems simultaneously. Any email sent during DNS propagation may be delivered to either system, and having both active ensures nothing is lost. Google's Data Migration Service can import your historical email from the old system in the background while both are running.

Step-by-Step: How I Set Up Google Workspace for Our Agency
Step 1: Signing Up and Choosing a Plan
I started at workspace.google.com and clicked Start Free Trial. Google offers a 14-day free trial on all Business plans — no credit card required to start. During signup, I entered our domain name (ourcompany.com), selected Business Starter, and created the first admin account using my email address. Google asked me to verify that I own the domain before proceeding, which I did in Step 2. One thing worth noting: the first account you create during signup becomes the Super Administrator for your Google Workspace account. This account has full control over all settings, users, and data. I created a dedicated admin account (admin@ourcompany.com) rather than using my personal work address, which is a best practice for account security. I then created my personal work mailbox as a separate user account.
Step 2: Verifying Your Domain and Updating DNS Records
After signup, Google's setup wizard presented a TXT record for domain verification — something like google-site-verification=abc123xyz. I logged into Namecheap, navigated to Advanced DNS for our domain, and added this TXT record. Back in the Google Admin Console, I clicked Verify and Google confirmed ownership within about two minutes. Next, the wizard presented the DNS records I needed to add to route email through Google's servers. The critical records were the MX records (five of them, with different priority values), the SPF TXT record (v=spf1 include:_spf.google.com ~all), and a note that DKIM would be configured separately after setup. I added all MX records and the SPF record at Namecheap. Because I had lowered our TTL to 300 seconds the previous evening, the changes propagated in about eight minutes — confirmed by checking our MX records with the free tool at mxtoolbox.com.
Step 3: Creating User Accounts and Groups
With the domain verified and DNS updated, I went to Directory, then Users in the Admin Console and created accounts for each of our six team members. For each user, I entered their name, set their email address (firstname@ourcompany.com), and set a temporary password. Google sent each user a welcome email with a link to sign in and set up their account, including prompts to enable two-factor authentication. I also created two Google Groups at this stage — info@ourcompany.com and hello@ourcompany.com — which function as shared inboxes that multiple team members can access. Google Groups used as collaborative inboxes do not require additional licenses. I set up the groups under Directory, then Groups, and added the relevant team members as members with the "Member" role so they could read and reply to messages.
Step 4: Configuring Gmail on Desktop and Mobile
For desktop access, most team members simply went to mail.google.com and signed in with their new Google Workspace credentials — no configuration required. Two team members who preferred to use Gmail through Outlook desktop were able to add their accounts via File, then Add Account in Outlook, entering their Google Workspace email address. Outlook auto-configured the connection using OAuth, which is more secure than entering a password directly and does not require enabling "less secure app access" in Google's settings. For mobile devices, the Gmail app for iOS and Android auto-configures with just an email address and password — the process takes under a minute. Two team members who preferred Apple Mail on iPhone added their accounts through Settings, then Mail, then Add Account, then Google, which also auto-configured without manual server entry. For any client requiring manual IMAP configuration, the settings are: incoming server imap.gmail.com, port 993, SSL; outgoing server smtp.gmail.com, port 465, SSL (or port 587 with STARTTLS).
Step 5: Setting Up DKIM and DMARC
DKIM setup in Google Workspace requires a manual step that the initial setup wizard does not complete automatically. In the Admin Console, I navigated to Apps, then Google Workspace, then Gmail, then Authenticate email. I selected our domain and clicked Generate New Record. Google provided a TXT record with a long cryptographic key that I added to our DNS at Namecheap under the host name google._domainkey. After adding the record, I returned to the Admin Console and clicked Start Authentication. Google confirmed DKIM was active within about 30 minutes. For DMARC, I added a TXT record manually at Namecheap with the host name _dmarc and the value v=DMARC1; p=none; rua=mailto:dmarc@ourcompany.com. I created a dedicated mailbox to receive the aggregate reports. After three weeks of reviewing reports and confirming that all legitimate senders — our email marketing tool, our CRM, and Google Workspace itself — were passing SPF and DKIM, I updated the policy to p=quarantine. I verified the full authentication setup using the free tool at dmarcanalyzer.com, which confirmed SPF, DKIM, and DMARC were all correctly configured.
Frequently Asked Questions — Google Workspace Setup
Do I need to transfer my domain to Google to use Google Workspace?
No. You do not need to transfer your domain to Google or change your domain registrar. You simply add DNS records at your existing registrar — MX records, an SPF TXT record, and DKIM CNAME or TXT records — that point to Google's mail servers. Your domain stays registered wherever it currently is. Google's setup wizard supports direct integration with many popular registrars including GoDaddy, Namecheap, Cloudflare, and Squarespace, and can update DNS records automatically if you grant it access.
Can I use Google Workspace email with Outlook, Apple Mail, or Thunderbird?
Yes. Google Workspace email works with any IMAP-compatible email client. Outlook desktop (2016 or later) supports automatic configuration via OAuth when you add a Google account through File, then Add Account. Apple Mail on Mac and iPhone auto-configures when you add a Google account through System Preferences or iPhone Settings. Thunderbird supports Google Workspace via IMAP with OAuth authentication in recent versions. For clients requiring manual IMAP settings: incoming server imap.gmail.com, port 993, SSL; outgoing server smtp.gmail.com, port 465, SSL.
What is a Google Workspace shared drive and do I need one?
A Shared Drive (formerly Team Drive) is a Google Drive folder that is owned by the organization rather than an individual user. Files in a Shared Drive remain accessible even if the user who created them leaves the company — unlike files in a personal My Drive, which are tied to the individual's account. For most small businesses, Shared Drives are the recommended way to store team files, client documents, and project assets. They are available on all Google Workspace Business plans and can be created in Google Drive under the Shared Drives section.
How do I add a second domain or email alias to Google Workspace?
Google Workspace supports multiple domains under a single account. To add a second domain, go to the Admin Console, then Account, then Domains, then Add a domain. You can add it as a primary domain alias (users get email addresses at both domains) or as a separate domain with its own users. Email aliases — additional addresses that deliver to an existing mailbox — can be added per user under Directory, then Users, then the user's profile, then Alternate emails. Each user can have up to 30 email aliases at no additional cost.
How much does Google Workspace cost for a small business?
Google Workspace Business Starter costs approximately $6/user/month on an annual plan as of July 2026. For a 5-person team, that is roughly $30/month or $360/year. Business Standard, which adds 2TB pooled storage and Meet recording, costs approximately $12/user/month — about $60/month for a 5-person team. Month-to-month billing is available at a roughly 20% premium over annual rates. Google offers a 14-day free trial on all Business plans. Verify current pricing at workspace.google.com/pricing before purchasing.


Conclusion & My Take
Google Workspace setup is genuinely straightforward for most small businesses, particularly if you are comfortable making DNS changes at your domain registrar. The Admin Console's setup wizard handles the most technically complex parts — generating MX records, SPF values, and DKIM keys — and Gmail's auto-configuration means most users can access their new email in under a minute. The areas where setup most commonly goes wrong are DNS-related: forgetting to lower the TTL before making changes, adding a second SPF record instead of merging, or rushing DMARC to p=reject before monitoring. Follow the staged approach in this guide and those problems are largely avoidable. If your team already uses Google services personally — Gmail, Google Drive, Google Photos — the transition to Google Workspace will feel natural. The integration between Gmail, Google Calendar, Google Meet, and Google Drive is seamless once set up, and the Admin Console gives you meaningful control over security settings, user management, and data without requiring IT expertise. If your team relies heavily on Microsoft Office desktop apps, Microsoft 365 may be a better fit — but for most small businesses starting fresh, Google Workspace Business Starter at $6/user/month is one of the best-value productivity platforms available. Have you recently set up Google Workspace for your business? I would be curious to hear whether you ran into any DNS issues or found a step in the process that was less clear than expected — feel free to share in the comments below.
Sources
Google Workspace Admin Help — Set Up Google Workspace — support.google.com
Google Workspace — Authorize Email Senders with SPF — support.google.com
Google Workspace — Set Up DKIM to Prevent Email Spoofing — support.google.com
NIST Special Publication 800-177 Rev. 1: Trustworthy Email (2019) — nist.gov
DMARC.org — Email Authentication Best Practices — dmarc.org









