Get the Microsoft foundation right the first time.

Tenant setup, migrations, identity, governance, the architecture decisions that determine whether everything else you build on Microsoft works properly. We handle the foundations end-to-end, then hand you something documented, secure, and supportable.

The scope

What Foundations and Migration includes.

A range of work that has one thing in common: get the underlying Microsoft estate to a known good state.

New tenant setup and configuration for firms moving onto Microsoft 365 for the first time
Migrations from Google Workspace, on-premises Exchange, on-premises SharePoint, file servers, and legacy collaboration platforms
Identity setup and modernisation: Entra ID, hybrid identity, federation, conditional access foundations
Information architecture for SharePoint and OneDrive: sites, libraries, permissions, lifecycle, search
Microsoft 365 group strategy and Teams governance baseline
M365 licence right-sizing as part of the move
Network and endpoint readiness for cloud workloads
Documentation, knowledge handover, and standard operating procedures

How the work usually scopes.

Accelerator route.

For firms where the move is well-defined and the tenant is straightforward, our productised accelerators handle most cases. M365 Efficiency Workshop (training), M365 Licence Health Check (audit), Teams Phone Migration (PBX replacement), and the SharePoint Intranet Accelerator (intranet build) are the most relevant.

Best for: 50 to 200 user firms with a known starting point and a clear target.

See Foundations accelerators

Custom project route.

For larger firms, regulated industries, or complex starting points (multiple legacy tools, hybrid identity, M&A consolidation), we scope a custom project. Indicative price range £18,000 to £80,000 depending on scale and complexity. Six to sixteen weeks.

Talk to a founder
Where it goes wrong

The mistakes we keep being called in to fix.

Four patterns we see repeatedly when we are brought in after an earlier supplier left things in a bad state.

1
Identity sprawl.
Legacy AD synced to Entra without conditional access, MFA inconsistently enforced, dormant accounts everywhere, no clear baseline of who has access to what. This is the single most common security risk we walk into.
2
SharePoint as a dumping ground.
Sites created ad hoc, no information architecture, permissions inherited everywhere, search broken because the metadata never existed. We have to redesign rather than fix.
3
Licence drift.
SKUs assigned years ago and never reviewed. Half the users on Business Premium when most need Standard. £20,000 a year wasted that nobody flagged.
4
Teams sprawl without governance.
Hundreds of Teams created during the pandemic, half abandoned, no naming convention, no expiry, no ownership.

Productised Foundations and Migration accelerators.

Accelerator

M365 Licence Health Check

Find what you are overpaying for and save thousands this year.

£1,200–£2,800
3 working days
View
Accelerator

M365 Efficiency Workshop

Close the gap between what your team uses M365 for and what it could be doing.

£950–£1,800
Half day
View
Accelerator

Teams Phone Migration

Replace your PBX or VoIP with Microsoft Teams Phone in four to six weeks.

£2,800–£9,500
4 to 6 weeks
View
Accelerator

SharePoint IA Rebuild

Cut through years of SharePoint sprawl into an information architecture that scales.

£8,400–£16,000
4 weeks
View

Foundations and Migration questions.

We are not sure whether we need a migration or just a clean-up. How do we tell?
+

Most firms need both at varying levels. The first conversation usually settles which is the bigger lift. If your tenant is broken structurally (identity, permissions, governance), no amount of new content fixes that. If your tenant is fine but the way people use it is messy, the cleanup is mostly governance and training rather than infrastructure work.

How long does an average Microsoft 365 migration take?
+

For a fifty to two-hundred user firm moving from Google Workspace or on-premises Exchange, expect six to twelve weeks end to end. The technical migration is two to four weeks of that; the rest is planning, user comms, training, and the inevitable cleanup of things nobody told you about.

Do you handle on-premises Exchange decommission?
+

Yes. We move you cleanly off, decommission the on-prem environment, and document what is left. Some firms keep a hybrid Exchange server for management; we cover that too.

Will my email be down during a migration?
+

No. We use cutover or hybrid migration patterns that keep mail flowing throughout. Users experience the change as a switch in client configuration rather than an outage.

Can you handle migrations across multiple tenants (post-M&A)?
+

Yes, with care. Cross-tenant migrations are more complex than greenfield ones. We scope these as custom projects rather than accelerators because no two are the same.