You've decided Google Workspace (formerly G Suite) isn't working. Maybe the per-user pricing is bleeding your budget. Maybe you hit a storage wall. Or maybe you just realized you're paying $12/month per mailbox for features you never touch.
But here's the trap: most "G
Suite alternatives" are just different flavors of the same problem. You
swap one per-seat tax for another. You trade Google's proprietary lock-in for
Microsoft's, or Zoho's, or someone else's walled garden.
The real question isn't "What's
cheaper than Google?" It's "What architecture actually fits how my
business operates?"
This checklist cuts through the
marketing noise. Use it to audit any alternative against your actual
needs—before you migrate and discover the gotchas. For the complete evaluation
framework, see Google
Workspace Alternatives: How to Choose Business Email Without Vendor Lock-In
(2026).
The
15-Point Evaluation Checklist
Run every potential alternative
through these filters. If a platform fails on a functional requirement (items
1–5), disqualify it immediately. If it fails on operational constraints
(items 6–12), understand the ceiling you're accepting. Migration risk (items
13–15) determines your switch cost.
1.
Protocol Support: IMAP/SMTP vs. Proprietary
The Question: Can you access email using standard protocols (IMAP/SMTP),
or are you locked into a proprietary client?
Why It Matters: If you use Thunderbird, Apple Mail, or any third-party
email client, you need IMAP/SMTP. Some "secure" providers (Proton,
Tutanota) break standard protocols in the name of encryption—meaning you must
use their apps.
The Test:
- Can you configure the service in Apple Mail or
Thunderbird using just server settings (e.g., imap.example.com:993)?
- Is ActiveSync supported for full mobile
calendar/contact sync, or just basic IMAP?
- Does the provider support POP3? (Legacy protocol; many modern platforms—including
TrekMail—intentionally exclude it due to sync issues.)
Red Flag: Provider requires you to download their app to access
email. This creates a client dependency that increases lock-in.
2.
Authentication: SSO or Separate Logins?
The Question: Does the platform integrate with your existing SSO (Okta,
Azure AD, Google Identity), or does it require separate credentials?
Why It Matters: If you use SSO to manage team access, forcing employees to
remember separate passwords for email creates a security hole. Password reuse
goes up. Offboarding friction increases (you have to remember to disable the
email account separately).
The Test:
- Does the provider support SAML 2.0 or OAuth for SSO?
- Can you enforce 2FA through your existing identity
provider?
Red Flag: Provider says "We have our own 2FA." That's not
SSO. That's another silo.
3.
Proprietary Format Dependencies
The Question: Does your workflow rely on Google-specific tools (Apps
Script, Forms, Sites) that don't export to open standards?
Why It Matters: If you use Google Forms to collect leads, or Apps Script to
automate workflows, no migration tool can port these. They are
database-backed applications, not files.
The Test:
- Audit your Google Drive for .form and .site files.
- Check if any critical workflows depend on Apps Script
automation.
Migration Reality:
- Google Forms:
Total loss. Export responses to CSV, rebuild forms manually in new tool.
- Google Sites:
Not migrated. Rebuild from scratch.
- Apps Script:
No equivalent in most alternatives. Requires custom code rewrite.
4.
Storage Architecture: Pooled vs. Per-User
The Question: Is storage shared across your organization (pooled), or is
it siloed per user?
Why It Matters: Google Workspace uses pooled storage—1TB split however your
team needs. Microsoft 365 uses split storage: 100GB for Exchange (email)
+ 1TB for OneDrive (files). These buckets don't talk to each other.
The Trap: In Microsoft 365, a user with a full 100GB mailbox cannot
borrow space from their mostly-empty 1TB OneDrive. You'll hit "mailbox
full" errors despite having terabytes of unused capacity.
The Test:
- Ask: "If one user needs 150GB for email and
another needs 10GB, can storage flex between them?"
- Check: Are email storage and file storage separate
pools?
Why This Matters for Agencies: If you manage client mailboxes, pooled storage lets you
allocate capacity dynamically. Per-user limits force you to over-provision and
waste spend.
5.
Migration Fidelity: What Breaks?
The Question: What data types, permissions, or metadata will not
survive the migration?
Why It Matters: Every provider claims "seamless migration." None
of them are. Conversion always involves fidelity loss.
The Forensics (migrating FROM Google
Workspace):
|
What You're Moving |
Microsoft 365 |
Zoho |
Proton |
Lark |
|
Google Forms |
Manual rebuild |
Skipped |
Not supported |
Manual rebuild |
|
Large Docs (>10MB) |
Conversion risk |
Blocked |
N/A |
Format variance |
|
Permissions |
Partial (external shares break) |
External shares lost |
Full reset |
Requires Migration Assistant |
|
Version History |
Often lost |
Not migrated |
Stripped |
Not imported |
|
File Paths |
400-char limit; blocked chars `" * : < > ? / \ |
` |
Duplicates get suffix (1) |
100-char folder name limit |
Red
Flag: Provider's migration guide doesn't
list exclusions or limitations. This means they haven't stress-tested
real-world migrations.
Note: Email-only platforms (TrekMail, Migadu, Purelymail)
sidestep this problem entirely—they migrate email via IMAP (standard .eml format), not proprietary files.
6.
Audit Log Retention
The Question: How long are logs kept? Can you search them indefinitely,
or is there a retention ceiling?
Why It Matters: If you're in a regulated industry (finance, healthcare,
legal), you may need indefinite audit history for compliance.
The Reality:
|
Provider |
Retention Window |
|
Google Workspace (with Vault) |
Indefinite |
|
Microsoft 365 (Audit Premium) |
Indefinite |
|
Microsoft 365 (Standard) |
180 days |
|
Zoho |
Default 365 days, max 10,000 days |
|
Lark |
180-day max
(single search cannot span >30 days) |
Disqualifier: If you're subject to HIPAA, SOC 2, or similar frameworks,
Lark's 180-day ceiling may fail your audit.
7.
eDiscovery Export Limits
The Question: If you get sued and need to export email/files for legal
discovery, what are the export caps?
Why It Matters: Zoho caps eDiscovery exports at 50GB per export. If
you need to produce 200GB of data, you must segment it manually—introducing
procedural risk and chain-of-custody gaps.
The Test:
- Ask: "What is the maximum size of a single
eDiscovery export?"
- Ask: "How long are exported files retained before
automatic deletion?"
Zoho-Specific Gotcha: Exported files are kept for 7 days, then permanently
deleted. IT must download and secure them immediately.
8.
Search Depth (OCR & Indexing)
The Question: Does the platform OCR (read text inside images) and index
PDFs automatically?
Why It Matters: Google indexes the text inside image-heavy PDFs and
screenshots automatically. Zoho's search is less capable—meaning image-only
documents can become "dark data" that's unsearchable.
The Test:
- Upload a scanned PDF with no text layer.
- Search for a word you know is in the image.
- Does it return the file?
Red Flag: Provider doesn't specify OCR capabilities. Assume it's not
there.
9.
Deleted User Data Recovery
The Question: How long is deleted user data retained before permanent
purge?
Why It Matters: If you accidentally delete a user account, you have a
limited recovery window.
|
Provider |
Retention After Deletion |
|
Google Workspace (Vault) |
Per retention policy (can be indefinite) |
|
Microsoft 365 |
30 days soft delete (unless legal hold) |
|
Zoho |
30 days, then permanent purge |
|
Lark |
Anonymized after offboarding |
Best Practice: Before deprovisioning, export critical data. Don't rely on
the platform's safety net.
10.
Device Management (MDM)
The Question: Can you remotely wipe devices, enforce encryption, or
restrict app installations?
Why It Matters: If employees access email on personal phones, you need
Mobile Device Management (MDM) to protect company data.
The Reality:
|
Provider |
MDM Capability |
|
Google Workspace Endpoint |
Basic wipe, passcode enforcement |
|
Microsoft Intune |
Deep control
(GPO, Conditional Access, app protection) |
|
Zoho MDM |
Basic |
|
Lark |
Encryption, screen capture blocking |
Microsoft Intune Gotcha: Device limits do not apply to devices enrolled via
Group Policy (GPO) or hybrid Azure AD join. These follow Azure AD limits
instead—creating a blind spot for admins.
11.
Attachment & File Limits
The Question: What are the hard caps on email attachment size, file
upload size, and file/folder counts?
Why It Matters: If your team sends large files regularly, hitting a 25MB
attachment limit creates friction. Some providers compensate with
"attachment links" (Zoho's "Huge Attachments"), but these
introduce security risks.
|
Provider |
Receive Limit |
Send Limit |
Notes |
|
Google Workspace |
25MB |
25MB |
— |
|
Microsoft 365 |
150MB (indexing limit) |
150MB |
— |
|
Zoho |
250MB (Lite), 1GB (Premium) |
Via "Huge Attachment" link |
"Public access" option can bypass attachment
controls |
|
Proton |
25MB |
25MB |
— |
Zoho-Specific Gotcha: The "Huge Attachments" feature can create a
shadow-IT channel if the "Public access" toggle is enabled. Files
bypass your attachment scanning/DLP.
12.
Support Accessibility
The Question: When things break, how fast can you reach a human?
Why It Matters: Automated support is fine for billing questions. When your
domain's emails are bouncing and you're losing sales, you need a human—now.
The Test (Before You Buy):
- Send a pre-sales support ticket with a technical
question.
- Time how long it takes to get a human response
(not a bot).
The Reality:
- Google Workspace:
Notorious for poor support on lower tiers. Phone support is gated behind
Enterprise pricing.
- Microsoft 365:
Better for Enterprise customers; SMB support is still slow.
- Zoho:
Mixed reviews. Free plans have no SLA.
- TrekMail:
Priority support on Pro ($8/mo) and Agency plans. Standard response within
business hours on lower tiers.
13.
Migration Downtime Tolerance
The Question: Can you afford DNS propagation delay (up to 48 hours), or
do you need zero-downtime "dual delivery"?
Why It Matters: Email migration requires changing your MX records (DNS).
Propagation can take 24-48 hours. During this window, some senders may still
deliver to your old server.
The Options:
- Simple Cutover:
Change MX, wait for propagation. Risk: some emails may be lost in transit.
- Dual Delivery:
Route mail to both old and new servers during transition. Requires
technical setup but eliminates loss risk.
Best Practice: Use dual delivery for business-critical domains. Use simple
cutover for internal/test domains.
14.
Permission Re-Mapping
The Question: Will "Shared with Me" links and external sharing
permissions survive the migration?
Why It Matters: When you migrate files from Google Drive to OneDrive, the
"Shared with Me" links break. External clients who had
"Viewer" access will lose it.
The Reality:
- Permissions are mapped based on email addresses. If you
change your domain, or if the new system doesn't support the exact same
granularity (Viewer/Commenter/Editor), permissions reset.
The Fix:
- Audit external shares before migration.
- Re-share critical folders manually after migration.
- Warn external stakeholders of the change.
15.
Exit Cost (The "Next Switch")
The Question: If you decide to leave this platform in 3 years, how hard
is it?
Why It Matters: Vendor lock-in isn't just about entering. It's about exiting.
If your data is stuck in proprietary formats, you're trapped.
The Test:
- Can you export all data in open standards (.eml, .docx,
.csv)?
- Is there API rate-limiting on bulk exports?
- Are there file format conversions that lose fidelity?
Red Flags:
- Proton:
Proprietary .protondoc format. Converting back to .docx
creates "two truths."
- Synology:
.osheet and .odoc
formats require conversion for every external share.
- Lark:
Walled garden. Limited export APIs.
Best Practice: Favor platforms that use open standards (IMAP, SMTP, .docx,
.xlsx). Email-only providers (TrekMail, Migadu) support standard IMAP
export—your data is always portable in .eml format.
How
to Use This Checklist
Step 1: Classify Your Requirements
- Print this checklist.
- Mark items 1–5 as "Must-Have" (fail =
disqualify).
- Mark items 6–12 as "Operational Ceiling"
(understand the trade-off).
- Mark items 13–15 as "Switch Cost"
(factor into your ROI math).
Step 2: Score Each Alternative
- Test each platform against the checklist.
- Document failures clearly (e.g., "Lark: 180-day
audit log ceiling = disqualified for SOC 2 compliance").
Step 3: Run a Pilot
- Don't migrate your entire org. Migrate one test domain
first.
- Send the support team a complex question. Time their
response.
- Upload a scanned PDF. Search for text inside it.
Step 4: Calculate True TCO
- Don't just compare list prices. Factor in:
- Migration labor cost (DNS, data transfer, user
training).
- Support incidents (if support is slow, you'll burn
internal IT hours).
- Lock-in risk (if you might switch again in 3 years,
favor open standards).
Where
TrekMail Fits
We're not trying to replace Google
Workspace's entire suite. We're email infrastructure—purpose-built for teams
who realize they don't need Docs, Meet, and Chat bundled into a per-seat tax.
Good Fit If:
- You're an agency or MSP managing multiple client
domains (50-1,000+ domains on a single plan).
- You use "best-of-breed" tools (Notion for
docs, Slack for chat, Zoom for calls) and just need professional email.
- You're tired of paying per-user for mailboxes that
barely send mail (support@, billing@, noreply@).
Not a Fit If:
- You need live co-authoring in spreadsheets.
- Your team lives in Google Meet for video calls.
- You require a full productivity suite under one vendor.
What You Get:
- Flat-rate pricing:
Starter at $3.50/mo (50 domains, 100 users/domain, 15GB pooled). Pro at
$8/mo (100 domains, 300 users/domain, 50GB pooled). Add users without
adding licenses.
- Pooled storage:
Allocate capacity dynamically. No "mailbox full" errors while
80% of your storage sits idle.
- Standards-first:
IMAP/SMTP support (no POP3). Built-in IMAP migration tool for Gmail/cPanel
imports.
- Invite owner (beta):
Send one-time setup links to mailbox owners. They choose their own
password and receive a recovery code—reducing admin burden and eliminating
credential sharing.
- BYO SMTP (optional):
Connect your own Amazon SES or Mailgun for total control over
deliverability (available on paid plans; Free plan requires BYO SMTP).
Try
TrekMail Free (10 domains, 10 users/domain, 5GB
pooled, BYO SMTP)
The
Full Framework
This checklist is a spoke—a
quick-reference tool for narrowing your options. For the complete decision
framework (including persona-specific recommendations, migration playbooks, and
operational gotchas), see our pillar guide:
Conclusion:
Choose Based on Ceiling, Not Price
The cheapest alternative isn't the
best alternative. It's the one that fails first when you scale.
Before you migrate:
- Audit your functional dependencies (Do you rely on Google Forms? Apps Script? SSO?).
- Identify your operational ceiling (Do you need indefinite audit logs? OCR search? 24/7
human support?).
- Calculate your switch cost (Are you trading one proprietary format for another?).
If you choose based on these factors
instead of price alone, you'll avoid the trap of switching vendors every 18
months.
Don't just find a cheaper landlord.
Build on infrastructure you control.
Comments
Post a Comment