Skip to content
ConsultEvo

How to Choose Business Email Hosting: Provider Fit, Costs, and Migration Checks

There is no single best business email hosting provider. Choose the smallest plan that meets confirmed requirements for mail, collaboration, storage, client access, security, and administration. A five-person team that needs only custom-domain email has a different buying decision from one that needs desktop Office applications, shared documents, meetings, and Exchange.

Hosted email is the service that manages business mailboxes and sends and receives mail for your domain. An email client, such as Outlook, Apple Mail, or Thunderbird, is the application used to read and compose messages. This guide covers hosted business email with custom domains, then follows the decision from requirements and cost comparison through a controlled domain cutover.

The practical sequence is simple: define must-haves, compare like-for-like plans, confirm client and administration details, then validate migration and DNS changes before approving routing.

Buy for confirmed work requirements, not for the longest list of bundled features.

Set requirements before comparing providers

Write down what the company must support before looking at prices. Mark each item as required, preferred, or not needed. This prevents an attractive introductory price or a broad suite from hiding a client, storage, or administration mismatch.

  • Identity and mail: user count, custom-domain count, aliases, shared addresses, forwarding, and ownership of role addresses such as support@ or sales@.
  • Applications and clients: desktop Office applications, browser tools, Outlook, Apple Mail, Thunderbird, mobile access, direct IMAP, POP, or ActiveSync, and any required bridge application.
  • Storage and records: mailbox storage per user, archive storage, file storage per user, team-level file storage, pooled storage, and retention storage. Keep these as separate requirements.
  • Administration and compliance: retention, eDiscovery, export, audit and recovery controls, data jurisdiction, security policies, and whether different users need different plans.
  • Budget and terms: billing region, annual or monthly commitment, tax treatment, minimum seats, promotional status, and whether Teams or desktop applications are included.

A useful requirements record can include user_count, domain_count, required_clients, mailbox_storage_gb_per_user, archive_storage_gb_per_user, file_storage_gb_per_user, file_storage_gb_per_team, pooled_storage_gb_per_user, retention_required, desktop_office_required, billing_region, and annual_budget. Do not collapse mail, archive, and file storage into one capacity number.

Compare providers by operational fit

Use this table to create a shortlist, not to declare an overall winner. A plan is a candidate only if it meets every required condition. An unclear detail remains open for vendor confirmation rather than being inferred from a general product overview.

Requirement Candidate fit Check before choosing
Desktop Office applications and Exchange Microsoft 365 Compare email-focused Exchange plans with full suites. Confirm mailbox, archive, Teams, and desktop-app packaging.
Browser-first Google collaboration Google Workspace Check pooled storage, edition-specific Vault availability, Gemini features, and administrator controls.
Budget-focused email or collaboration Zoho Mail or Workplace Zoho Mail Free is web-only in the current comparison. Confirm regional availability, client access, and paid-plan limits.
Focused email, calendar, and contacts Fastmail Separate mail, calendar, and contact storage from file storage. Verify the selected tier’s domain features.
Encrypted-mail ecosystem Proton Mail Check domain and storage limits and whether third-party clients require Proton Mail Bridge.
All-in-one email and collaboration IceWarp Obtain current pricing, minimum-seat terms, desktop options, and storage allocations before numerical comparison.

Dated US price snapshot: Vendor pages reviewed November 21, 2026 displayed Microsoft 365 Business Basic at $7 and Business Standard at $14 per user per month when paid yearly. Microsoft’s Exchange comparison separately displayed Plan 1 at $4 and Plan 2 at $8 per user per month when paid yearly. Google Workspace displayed Business Starter at $7, Business Standard at $14, and Business Plus at $22 per user per month after the displayed promotional period. These are US list-page observations, not guaranteed quotes. Billing term, promotion, taxes, Teams inclusion, and packaging can change the result. Check the current Microsoft 365 Business Standard page, Exchange Online comparison, and Google Workspace US pricing page before purchase.

Other plan distinctions matter more than a starting price. Zoho Mail Free lists up to five users, one custom domain, and 5GB of mail storage per user, but the current comparison excludes IMAP, POP, and ActiveSync and limits availability to selected regions. Zoho Workplace Standard lists 30GB of mail storage per user and WorkDrive storage beginning at 100GB per team for three to ten users.

Fastmail’s US page lists Basic at $4 and Standard at $6 per user per month in its plan presentation. Basic shows 6GB total storage: 5GB for mail, calendar, and contacts plus 1GB for files. Standard shows 60GB total: 50GB for mail, calendar, and contacts plus 10GB for files. Proton Mail Essentials lists 15GB per user and three custom domains, but the reviewed business page did not expose a reliable current price. IceWarp’s current public product page markets an all-in-one workspace but does not verify current price, minimum seats, or storage packaging. Review the live Zoho plan comparison, Fastmail US pricing, Proton business pricing, and IceWarp product page.

Compare total cost on equal terms

Normalize the same number of users, region, currency, billing commitment, tax treatment, and application needs. Calculate annual cost as the monthly annual-equivalent price multiplied by users and 12 only when the vendor states that the price applies to annual billing.

For example, five Microsoft 365 Business Basic seats at the observed US annual-billing price of $7 per user per month equal $420 per year before tax. That is not automatically comparable with an email-only plan because Business Basic includes a different application and storage package. Exchange Online Plan 1 may be a more appropriate Microsoft comparison when the requirement is hosted email rather than a complete office suite.

Email-first

Price the mailbox requirement

Compare Exchange Online with focused mail providers. Confirm mailbox and archive capacity, domains, client access, aliases, and shared-address behavior.

Suite-first

Price the work applications

Compare complete suites when desktop Office, shared files, meetings, identity, or browser collaboration are actual requirements. Count included applications and storage scope.

Storage labels must remain precise. Microsoft lists business-plan cloud storage separately from Exchange mailbox and archive limits. Google describes pooled storage per person rather than a separate private file quota. Zoho separates mail storage from team-level WorkDrive storage. Fastmail separates mail, calendar, and contact storage from file storage. These amounts should not be added together and called mailbox capacity.

Cost control

Every price observation should retain its plan name, region, billing term, tax basis, promotional status, included applications, storage scope, source URL, and observation date. Without those fields, a low price is not a reproducible comparison.

Check compatibility and administration before buying

Confirm that the exact plan supports the clients and operating model users already depend on. Zoho Mail Free’s web-only condition may rule it out for a team that requires a desktop mail client. Proton supports third-party clients for paid subscribers through Proton Mail Bridge, which is a compatibility layer rather than ordinary direct IMAP access. Fastmail’s current pricing page associates custom-domain business addresses with Standard and higher plans; verify any mixed-tier arrangement directly.

Decide whether each role address should be an alias, shared mailbox, group, or forwarding rule. These models have different ownership, access, sending, audit, and offboarding behavior. Test who can read, send from, and administer the address. Record what happens to it when an employee leaves.

Check user limits, regional availability, mail and archive quotas, retention, eDiscovery, export, audit, recovery, and data jurisdiction for the exact edition. Google Vault provides retention, search, and export for supported Workspace data, but availability depends on edition. Google’s administrator guidance explains that Gemini access to Workspace data follows relevant user and content permissions and can be restricted by administrator settings. See Google Vault and Google’s Gemini access-control guidance.

For every requirement, record pass, fail, or needs vendor confirmation. A failed must-have rules out the plan. An unresolved item remains open until current documentation or the vendor answers it.

Plan domain setup and migration as a controlled cutover

The following is provider-neutral operating guidance, not a universal vendor runbook. DNS values, migration tools, supported data types, and account-creation steps depend on the selected service. Use the destination provider’s current documentation for the exact records and migration method.

Name a migration owner and keep a change record as the system of record. Inventory accounts and addresses first, preserve current DNS values, and keep the old service available until the destination passes acceptance checks.

01InventoryList users, aliases, groups, shared addresses, forwarding, calendars, contacts, folders, and the source host. Save a dated inventory version and identify missing ownership or authorization.
02Verify the domainConfirm DNS access and domain ownership in the destination service. Capture existing MX, SPF, DKIM, and DMARC records before editing DNS.
03Configure and migrateCreate destination accounts and addresses, apply provider-specific authentication records, and migrate mail and related data using the chosen provider’s documented method.
04ValidateCompare mailbox and folder counts. Inspect old, recent, sent, and attachment-heavy messages. Sample calendars and contacts, then test external inbound and outbound delivery.
05Approve the cutoverThe designated approver changes mail routing only after mailbox acceptance checks pass. Keep prior DNS values and a named rollback authority in the change record.

Follow the selected provider’s current instructions for MX, SPF, DKIM, and DMARC. Verify the domain before changing MX, then test both directions of delivery with external addresses. Keep the old service until messages, folders, attachments, aliases, forwarding, shared-address behavior, calendars, and contacts have been checked. Fastmail and Zoho describe migration or setup capabilities on their business overview and business email setup guide. These pages support provider-specific capabilities, not one cross-provider sequence.

Use automation only after the process is defined

The reviewed sources do not establish a complete public API or verified cross-provider automation module for provisioning users, aliases, DNS, and mail migration across all six services. Treat automation as a later implementation choice, not a purchase assumption. First maintain a buyer-owned comparison and change log. Automate only steps confirmed by the selected provider’s current documentation.

Use deterministic checks for expected MX records, existing addresses, plan user limits, storage scope, migration completion, and duplicate message imports. AI may summarize free-text requirements or extract candidate limitations from vendor pages into a reviewable record. It should not select the plan, provision accounts, change DNS, delete users, or disable the old service without human approval.

For a requirements-to-shortlist record, store one row per provider-plan observation. Useful fields include requirements_id, candidate_provider, plan_name, matched_requirements, unresolved_requirements, source_url, observed_at, region, billing_term, and review_status. Keep price, application inclusion, and storage scope as separate fields. An unresolved requirement routes to the IT, operations, finance, or procurement owner rather than becoming an unverified approval.

For domain onboarding, keep each DNS observation at its own grain: organization, domain, record type, normalized value, and observation time. Keep a separate current-state summary if the workflow needs one. For migration, store one event per source message, not one message-shaped row containing mailbox totals. A separate mailbox acceptance summary can hold counts and sign-off.

Where retries or concurrent workers can write the same event, use a database-enforced unique index or transactional upsert. A proposed migration uniqueness key is organization_id + source_provider + source_mailbox_id + source_message_id. A proposed provisioning key is organization_id + normalized_domain + normalized_address + object_type + desired_state_version. These are illustrative implementation patterns, not vendor-published schemas. A lookup followed by insert is not safe as the only duplicate-prevention method under concurrency.

For workflow design support, see Zapier automation consulting. This link indicates workflow design support and does not claim that a ready-made connector exists for any provider.

A practical selection and sign-off sequence

Shortlist by work model, test non-negotiable client and storage requirements, normalize current costs, confirm administration and migration details, then approve a controlled cutover.

  • Microsoft 365: a candidate when desktop Office applications and Exchange are required.
  • Google Workspace: a candidate for browser-first Google collaboration, Gmail workflows, and pooled Drive storage.
  • Zoho: a candidate when price is important and the relevant plan’s client, regional, and storage limitations are acceptable.
  • Fastmail: a candidate for focused hosted email, calendars, contacts, and custom domains without a full office suite.
  • Proton: a candidate when its encrypted-mail model, administration controls, and Bridge-based client workflow meet requirements.
  • IceWarp: a candidate for an all-in-one workspace after current commercial terms and storage allocations are confirmed.
Purchase gate
  • Record the price, region, billing term, promotion, tax basis, and included applications.
  • Confirm every required client, domain, mailbox, archive, and file-storage condition.
  • Resolve retention, administration, regional availability, and role-address ownership.
  • Name the migration owner and record mailbox-level acceptance checks.
  • Save current DNS values and identify who can approve cutover or rollback.

Plans and prices change. Preserve the source URL and observation date for each final decision, then recheck live terms before signing. If the work also requires broader systems or operations support, review ConsultEvo’s services.