We're a small company with fewer than 50 active email users, and our current setup is becoming increasingly difficult to manage. Email runs on a privately hosted Exchange server, while our Microsoft 365 licenses are handled separately for applications such as Teams, Word, and Excel. Teams and Outlook do not reliably stay synchronized, employees cannot reset their own passwords, and we cannot easily create groups such as managers or maintenance staff. We also use Dropbox for file storage and have some folders that should be restricted to administrators.
Many field employees have trouble accessing email on their phones, and our current IT provider routes mail through a filtering and encryption service that frequently blocks messages from legitimate business partners without making the situation clear. We own our domain, although it is currently managed by the IT provider.
Would moving everything to Google Workspace solve these problems, or would it make more sense to move the existing Microsoft environment to Microsoft 365 with Exchange Online, OneDrive, and properly configured identity management? Is this mainly a platform issue, or does it sound like our current IT provider has designed and maintained the environment poorly?
5 Answers
Your mail-filtering complaint should be addressed with the current provider rather than solved by changing platforms. Sensitive-data inspection can be useful, but legitimate messages should either be allowed through using sensible policies or rejected with a clear notification to the sender. The provider should also be able to maintain allowlists, quarantine workflows, encryption rules, and audit logs.
A replacement provider should review the filtering configuration and explain exactly what is being blocked and why.
Most of these problems are not specific to Microsoft versus Google. Self-service password resets, employee groups, mobile access, shared calendars, MFA, permissions, and Teams integration are all standard capabilities when Microsoft is configured properly. Running a private Exchange server for a company of this size is also an unnecessary operational burden.
Before changing platforms, get a second opinion from a competent IT provider and seriously consider moving to Microsoft 365 with Exchange Online. You already use Microsoft applications, so that route should create less training and migration friction than moving the entire company to Google Workspace.
The best next step is probably replacing or independently evaluating the IT provider. Ask for a documented assessment covering your domain, identity accounts, Exchange configuration, Microsoft 365 licensing, mail flow, filtering, backups, mobile access, file permissions, and migration options.
A good provider may recommend Microsoft 365, Google Workspace, or a hybrid approach, but they should explain the tradeoffs instead of saying, “that’s how it was set up.” Make sure the company retains administrative ownership of its domain and tenant, and avoid giving broad administrator access to employees simply to bypass support delays.
That makes sense. After reading the responses, it sounds like the main problem is our provider and the outdated architecture, not necessarily Microsoft itself. We’ll look for a new provider to assess the environment before deciding on a migration.
Moving email from on-premises Exchange to the cloud is worthwhile, but the target should probably be Microsoft 365 in this case. Exchange Online, Microsoft 365 Groups, OneDrive or SharePoint, MFA, and self-service password reset would address most of the complaints while keeping the staff in familiar applications.
Regardless of the platform, plan the project carefully: inventory mailboxes and aliases, confirm domain ownership, review shared mailboxes and permissions, test mobile devices, migrate files separately, communicate the changes to employees, and keep a rollback or recovery plan.
There is no clear benefit to switching to Google in the information provided. Google Workspace could provide hosted email, groups, shared calendars, cloud storage, and office applications, but it would also require a major migration and a new user workflow. It would not automatically fix bad permissions, poor support, or overly aggressive mail filtering.
If you did choose Google, migrate deliberately and test Gmail, Drive permissions, document conversion, mobile access, and any third-party integrations before committing. Do not treat the move as a shortcut around IT governance or security controls.
Having separate accounts for on-premises Exchange and Microsoft 365 is often a sign of an old design. Entra ID can provide a central identity system for Microsoft 365 and other services, with MFA and self-service password resets enabled.