Using an address at the business’s domain can make ownership and staff transitions easier to manage. It does not require Google Workspace, and owning a domain or running WordPress does not automatically include an email service. Microsoft 365, Google Workspace, a hosting provider, and other mail platforms can all be valid choices depending on the business.
Whichever provider you choose, moving email is not just creating a new inbox. The project has to preserve the messages people need, keep new mail flowing, and leave the business—not one employee or outside technician—in control of the result.
Inventory mailboxes before choosing a migration method
List every person, address, alias, forwarding rule, group, shared mailbox, and application that sends or receives business mail. Include former staff accounts that must be retained, scanner or website messages, billing contacts, mobile devices, and any mailbox used for password recovery.
For each item, record the current provider, approximate size, owner, retention need, and intended destination. Decide whether the scope includes only email messages or also calendars, contacts, tasks, delegated access, shared mailboxes, signatures, filters, and local archives stored on a computer.
That distinction matters because IMAP is a mail-access protocol. An IMAP message import should not be described as an automatic migration of calendars, contacts, shared mailboxes, multiple users, local-only folders, or every account setting.
Our earlier checklist for mapping dependencies before changing email providers covers the vendor logins, forms, devices, and recovery paths that can be missed when attention stays on the inbox.
Verify the limits of the import tool
On September 23, 2026, Google announced a simplified IMAP email import during Google Workspace setup. It is available to Workspace administrators after domain verification and email activation, runs in the background, and supports importing past email from one user through that setup path.
Google directs administrators to a different process for multiple IMAP accounts. The announcement says “past emails”; it does not say this two-step import automatically moves calendars, contacts, shared mailboxes, multiple users, or non-mail data. Verify the source provider’s IMAP access, credentials, folder behavior, size limits, and retention needs before treating the tool as the migration plan.
Google Workspace is one option, not a requirement. The same planning discipline applies when migrating to or from another platform.
Coordinate domain records and authentication
The domain’s DNS determines where new mail is delivered. A planned change may involve MX records for routing and TXT or CNAME records for SPF, DKIM, DMARC, and provider verification. Record the working state before editing it, follow the chosen provider’s exact documentation, and avoid deleting unrelated DNS records.
Sender authentication is not a box to check blindly. SPF has lookup and authorization rules, DKIM keys are provider-specific, and DMARC policy should match a monitored rollout. A domain can receive mail while outgoing messages are still misconfigured or treated as suspicious.
Plan a change window and keep the old mailbox accessible long enough to catch missed messages and dependencies. Do not erase the source or cancel the old service merely because the first test message arrived.
Test the complete handoff
Send messages in both directions using addresses inside and outside the new domain. Reply, forward, attach a file, and check spam placement. Verify phones, desktop clients, shared access, website forms, scanners, notifications, aliases, and recovery addresses. Compare folders and a sample of old messages, including attachments and dates.
Write down who approved the result and who can recover the administrator account. Our notes on avoiding one-person password dependency and business ownership of technology accounts provide a practical ownership baseline.
Google also announced temporary administrator role assignments on September 23, 2026. A super administrator can give a user, group, or service account a role until a preset or custom expiration; the primary administrator cannot be temporary. For a migration, that can reduce long-lived outside access. It does not replace a business-controlled primary administrator, recovery methods, audit trail, or deliberate review of the permissions granted.
Computer 911 can help inventory the current email environment, define migration scope, coordinate DNS changes, test the handoff, and document account ownership. Begin with the Business Project intake and include the current provider, number of users, domain owner, and what must be preserved.
