Choosing the platform is the easy part
The hard part is the migration weekend, the mail flow nobody documented, and the licence count that quietly grew by forty seats.
Microsoft 365 or Google Workspace
Both are good. Which is right depends on what your people already do, what your applications already integrate with, and what your licence position looks like — not on which one we would rather sell.
- Platform selection against actual usage and existing integrations
- Licence mix chosen per user role rather than assigned uniformly
- Tenant build, domain and DNS configuration done properly
- Shared mailboxes, groups and delegation modelled deliberately
- Hybrid or coexistence where a staged approach is needed
Who gets in, and to what
The workspace is where identity becomes the perimeter. Get this wrong and every other control is decoration.
- Single sign-on across the applications your people actually use
- Multi-factor authentication with a rollout that will not cause a helpdesk queue
- Conditional access by device, location and risk
- Joiner, mover and leaver process automated where possible
- Privileged accounts separated from daily-use accounts
Laptops and phones on the estate
Devices enrolled and compliant, so that access can be conditional on the state of the endpoint rather than only on the password.
- Intune or Workspace device management enrolment
- Baseline compliance policies before access is granted
- Application deployment and patch state visibility
- Selective wipe on personal devices, full wipe on corporate
- Lost-device procedure that works on a Sunday
Keeping the information in the right place
A workspace makes sharing easy, which is the point and also the risk. The controls sit around the data rather than around the people.
- Sharing policies for internal, external and anonymous links
- Data loss prevention rules for the data that actually matters
- Retention and legal hold configured to policy
- Backup of mail and files — the platform is not a backup
- Audit logging retained for the period compliance requires
Whether anyone actually uses it
The difference between a migration and a transformation is whether the second week looks different from the first. That is a training and communication problem, not a technical one.
- Champion group identified and trained before the wider rollout
- Role-based training rather than a generic session
- Quick-reference material in the languages your team uses
- Usage reporting so gaps are visible and addressable
- Follow-up sessions at thirty and ninety days
Platforms we are authorised to sell
Cloud, workspace & hosting
Tell us what you are running today
We will tell you what we would change, and what it would cost. No obligation, and a named engineer on the call rather than an account manager.