Migrating from Google Workspace to FolioInbox: The Cutover Guide for Solo Operators

Pre-Migration Audit: Archiving Workspace Data and Auditing Active Aliases

A smooth cutover requires documenting your active endpoints and backing up existing records before updating public DNS records. When you move email from workspace to custom host platforms, incoming messages route immediately to the new destination once MX records propagate.

Email remains the authoritative authentication layer for modern online services. As documented in Pew Research Center research on email use, digital messaging systems function as the primary structural tool in modern commercial environments. Ensuring zero data loss during an infrastructure cutover requires auditing four technical zones:

1. Export Historical Mail via Google Takeout: Log into each Workspace account, navigate to Google Takeout, deselect all services except Mail, and request an MBOX format archive. Store this archive in secure local storage or cold cloud storage. This ensures you retain full historical archives for tax, legal, and operational continuity after your Workspace accounts close.
2. Catalog Inbound Aliases and Group Routing: Navigate to the Google Workspace Admin Console under Directory > Users and record every alias assigned to your primary user (for example, billing@, legal@, or hello@). Verify whether any Workspace Groups were configured to forward inbound mail to external addresses.
3. Document Transactional API Senders: Check if transactional systems (Shopify, Stripe, Postmark, AWS SES, or Brevo) send outbound notifications using an address on your domains. These services use dedicated SPF inclusions or DKIM CNAMEs that must be retained during the DNS update.
4. Lower DNS TTL Values 48 Hours in Advance: Locate the MX and TXT records at your domain registrar or DNS host (such as Cloudflare, Route 53, or Namecheap). Lower the Time to Live (TTL) values from 86,400 seconds (24 hours) or 3,600 seconds (1 hour) down to 300 seconds (5 minutes). This step ensures that when you swap MX records during cutover, recursive resolvers clear cached records and recognize the new mail exchange within minutes.

Before modifying DNS records, establish a baseline health check for your domains. Run your domains through the free domain health audit tool to evaluate existing SPF strings, DKIM keys, and DMARC alignment. Documenting this baseline ensures you do not inherit broken authentication configurations during the cutover.

Step-by-Step DNS Cutover: Step-by-Step for Migrating from Google Workspace to FolioInbox

Executing the switchover involves registering your domain identities inside Folio and reconfiguring public DNS records to transfer routing authority.

Step 1: Connect the Domain in Folio

Log in to Folio using your passkey or magic link. Add your domain inside the central dashboard. Folio features guided domain setup: if your registrar or DNS provider supports Domain Connect (such as GoDaddy or Namecheap), Folio can negotiate and publish your DNS records automatically in a single confirmation screen. If your provider does not support Domain Connect, the dashboard generates the exact MX, TXT, and CNAME records for manual entry.

Step 2: Replace Google MX Records

In your DNS management zone, delete existing Google MX records pointing to legacy endpoints:

# Remove these legacy Google Workspace records:
Priority 1:  ASPMX.L.GOOGLE.COM.
Priority 5:  ALT1.ASPMX.L.GOOGLE.COM.
Priority 5:  ALT2.ASPMX.L.GOOGLE.COM.
Priority 10: ALT3.ASPMX.L.GOOGLE.COM.
Priority 10: ALT4.ASPMX.L.GOOGLE.COM.
# Or the unified endpoint:
Priority 1:  SMTP.GOOGLE.COM.

Add the Folio MX records displayed in your setup panel. Set the record priority based on the dashboard instructions, ensuring that no other MX records remain active on the apex domain. Having conflicting MX records from two different mail providers results in bounced mail and split delivery errors.

Step 3: Establish Per-Domain 2048-Bit DKIM Keys

DomainKeys Identified Mail (DKIM) adds a cryptographic signature to outbound email headers, confirming that the message originated from an authorized server and remained unaltered in transit. Many legacy alias setups share a single signing key across multiple brands, creating deliverability dependencies between unrelated entities.

Folio provisions an independent 2048-bit DKIM key pair for every connected domain. Copy the public key record (typically a CNAME or TXT record with a custom selector such as folio._domainkey.yourbrand.com) into your DNS zone. Once published, your outbound messages carry a signature aligned specifically with that individual domain identity.

Step 4: Update the SPF TXT Record

Sender Policy Framework (SPF) designates which IP addresses and mail servers can send mail claiming your domain name in the envelope sender. A common configuration mistake during migration is leaving the Google mechanism inside the SPF string, or chaining multiple TXT records together.

If your domain only sends through your mailbox host, replace the Google mechanism entirely:

# Incorrect (Multiple TXT records):
v=spf1 include:_spf.google.com ~all
v=spf1 include:_spf.folioinbox.com ~all

# Correct (Consolidated single record):
v=spf1 include:_spf.folioinbox.com ~all

If you also send transactional receipts through a platform like Postmark or Shopify, merge their include mechanisms into that single record string. You can use the SPF record generator to construct and validate your syntax before saving.

Step 5: Enforce DMARC Alignment

Domain-based Message Authentication, Reporting, and Conformance (DMARC) instructs receiving mail servers how to treat messages that fail SPF or DKIM validation. The FTC phishing guidance highlights how rigorous email verification prevents spoofing and social engineering attempts. A sound DMARC policy ensures unauthorized parties cannot impersonate your brand.

If your domain runs p=none , keep that monitoring policy active for the first 48 hours following cutover:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourbrand.com; pct=100;

Once delivery reports verify that your outbound mail signs cleanly under Folio DKIM and passes SPF checks, update your policy to p=quarantine or p=reject to protect your domain reputation against unauthorized spoofing.

How to Cancel Google Workspace Subscription Cleanly Without Breaking SSO or File Access

Canceling Google Workspace requires more than updating MX records. Because Google Workspace identities often double as organizational authentication directories, cutting the subscription prematurely can lock you out of critical third-party tools.

The FTC guidance on how websites and apps collect and use information advises auditing connected applications and third-party data access periodically. When preparing to cancel google workspace subscription billing, perform this separation methodically:

Step 1: Audit Third-Party Single Sign-On (SSO) Dependencies

Log in to the Google Admin Console and inspect connected applications under Security > Access and data control > API controls. Review every third-party software service where you authenticated using "Sign in with Google" (such as Stripe, AWS, GitHub, Notion, or banking portals).

Log into each of those external platforms independently. Update your login profile to use direct email and password credentials or passkey authentication, anchored to your email address rather than Google OAuth tokens. If you cancel Workspace before reassigning these logins, recovering access can require protracted identity verification with customer support.

Step 2: Relocate Google Drive and GCP Ownership

Files created inside a Google Workspace tenant are owned by that organization. If you need continued access to legacy spreadsheets, presentations, or client files:

• Create a free personal Google account (e.g., yourbrand.archive@gmail.com).
• Share the core Drive folders from your Workspace user to this external account.
• Transfer file ownership where permitted, or download the folder trees to local encrypted storage.
• If you manage Google Cloud Platform (GCP) console projects under your Workspace account, add a secondary personal Google identity as an Owner in the IAM settings to prevent losing console access when the Workspace identity is deleted.

Step 3: Remove the Domain from the Google Workspace Tenant

Google Workspace prevents other services from routing mail if it believes the domain is still hosted within its internal infrastructure. Once DNS cutover propagation is verified and traffic routes to Folio, remove the domain from Google's directory:

1. Navigate to the Google Workspace Admin Console.
2. Go to Account > Domains > Manage Domains.
3. If the domain is designated as the Primary Domain, you must first swap the primary domain designation or delete the associated user accounts.
4. Click Remove next to the custom domain name and confirm the deletion.

Step 4: Terminate the Workspace Subscription

With domains detached, authentication dependencies transferred, and archives secured, halt the billing cycle:

1. Open Billing > Subscriptions in the Admin Console.
2. Select your active Google Workspace subscription (e.g., Business Starter).
3. Click Cancel Subscription.
4. Follow the cancellation confirmation steps. Google will bill any accrued prorated usage for the active month, and your seat renewal charges will cease.

Day-One Verification: Delivering Across Separate Identities from a Single Mailbox

Once DNS updates propagate and Google Workspace is disconnected, your day-one operational setup inside Folio begins. Rather than juggling five separate web browser profiles or mobile app logins, you manage all business domains through a single screen.

Authentication via Modern Credentials

Folio eliminates legacy passwords entirely. Account sign-in uses magic links sent to your designated administrative recovery address, or cryptographic passkeys stored in your hardware authenticator or operating system keychain. This structure prevents credential compromise via brute-force dictionary attacks or database credential leaks.

Configuring Domain Personas and Outbound Signatures

Inside the Folio web client or Android application, establish dedicated sending personas for each connected business:

• Consulting Identity: jane@consultingbrand.com with legal disclosures and calendar scheduling links.
• Holding Entity Identity: admin@holdingsllc.com with corporate registration details and formal sign-offs.
• Ecommerce Store Identity: support@shopbrand.com with customer care notices and returns policies.

When composing or responding to messages, Folio selects the appropriate outbound domain and matching signature automatically based on the recipient address and thread history. Outbound mail routes through Folio's servers with the correct DKIM signature aligned to that specific entity, ensuring receiver verification checks pass cleanly.

Verifying Inbound and Outbound Deliverability

Major inbox providers—including Google and Yahoo—enforce strict deliverability and authentication requirements for bulk and transactional senders. Test each connected domain across two critical criteria:

1. Outbound Delivery and Header Inspection: Send an outbound message from each domain to an external test address. Inspect the raw message headers to confirm:
   • DKIM-Signature passes with your specific domain tag (d=yourbrand.com).
   • Received-SPF returns a Pass status for Folio's sending IPs.
   • DMARC reports Pass with valid identifier alignment.
2. Inbound Routing and Aliasing: Send inbound messages to your configured aliases (e.g., billing@, hello@). Verify that messages land in your unified inbox with clear visual badging indicating which domain and alias received the message.

Monitor your monthly outbound send volume against your subscription caps. Solo plans provide 1,000 monthly sends, Studio accommodates 6,000, and Holding Co. supports 30,000. For solo operators handling business correspondence, client deliverables, and supplier communication, these thresholds comfortably accommodate typical multi-brand operations without per-seat fees.

Frequently Asked Questions

Will I lose my existing Google Drive documents if I move my email from Google Workspace to FolioInbox?

Yes, if you cancel your Google Workspace subscription without backing up or transferring your files, you will lose access to the associated Google Drive data. Moving your MX records to Folio only reroutes incoming and outgoing email; it does not transfer files stored in Google Drive. Before canceling your Workspace account, export your documents via Google Takeout or share and transfer folder ownership to a free, personal Google account.

Can multiple team members share the FolioInbox mailbox after migrating from Google Workspace?

No. Folio is a single-operator inbox, not a team or shared mailbox — there are no per-user seats and no team collaboration features. Folio is engineered specifically for one person managing multiple custom domains from a single interface. If your organization requires shared drafts, collision detection, or concurrent multi-user access, Folio is not built for your workflow.

Does FolioInbox offer a free plan for low-volume domains?

Folio has no free plan. It offers a 14-day free trial and a no-credit-card preview, then flat paid plans (Solo, Studio, Holding Co.). based on the platform's published pricing schedule, Folio Studio costs a measurable budget per month billed annually (a measurable budget per year) or a measurable budget monthly, supporting up to 10 domains and 6,000 sends per month.

How long does the DNS cutover take when migrating my domains away from Google Workspace?

The time required for a cutover depends on the Time to Live (TTL) values configured on your existing DNS records. If you lower your MX and TXT record TTLs to 300 seconds (5 minutes) at least 48 hours prior to the migration, the actual routing transition completes within minutes of publishing Folio's records. If TTL values remain set to standard defaults like 86,400 seconds, full global propagation can take between 24 and 48 hours.

Review your exact monthly savings on the FolioInbox pricing page and start a 14-day trial or zero-card preview to cut over your primary business domains today.