20+ years with Microsoft 1,100+ organisations under management 131 countries invoiced locally 4 of 6 Solutions Partner designations 4-hour first response
IT Partner.Microsoft Solutions Partner +44 20 8142 5752 Talk to us Get a quote

HomeServices › On-premises to cloud

MigrationEntra IDExchange

On-premises to cloud

Active Directory to Entra ID, Exchange and SharePoint farms to Microsoft 365, file servers to OneDrive. The migration is the easy half; finding everything that quietly depends on those servers is the other one.

Typical timeline1–4 months
From£800 / €950 / $1,000
Hybrid endsWhen you decide
Invoiced inYour currency
01 — Overview

What this engagement is

Active Directory to Entra ID. On-premises Exchange to Exchange Online. A SharePoint farm to SharePoint Online. File servers to OneDrive and SharePoint. Usually all four at once, because the reason for the project is rarely the technology — it is a lease ending, a server refresh nobody wants to fund, or an acquisition that made the estate somebody else’s problem.

The mechanics are well understood. What makes these projects go wrong is what the audit misses: the application that authenticates against a domain controller, the finance system that writes to a UNC path, the scanner that emails via the on-premises relay, the licence server nobody has logged into since 2019.

We have moved clients off on-premises Active Directory entirely, replaced servers whose only remaining job was serving LDAP to one application, and decommissioned farms after the content had been out of them for months. Hybrid stays running until you choose to switch it off, not until we do.

02 — Outcomes

What you get out of it

01Identity in Entra ID, with sign-in working the same way for users on day one
02Mailboxes in Exchange Online, with the on-premises Exchange organisation retired or kept for management as you prefer
03File server content in SharePoint and OneDrive, in a structure that was designed rather than lifted
04SharePoint farm content migrated and the farm decommissioned
05Every dependency on the on-premises estate found, listed and given an owner — before the servers are switched off
06A hybrid period that ends on your schedule, with a written decommission checklist
07Nothing left running that nobody can explain
03 — Deliverables

What you receive

Estate audit. Servers, roles, dependencies, authentication paths, scheduled tasks, service accounts and anything with a UNC path in its configuration.
Dependency register. Every application, device or process that relies on the on-premises estate, with a named owner and a decision.
Identity design. Entra ID structure, sync or cloud-only, Conditional Access baseline, and what happens to service accounts.
Migration plan covering identity, mail, files and SharePoint, sequenced by dependency.
Hybrid coexistence design for the transition period, including mail flow.
Decommission checklist per server, with the verification that must pass before it is switched off.
Closing report recording what moved, what was retired, and what deliberately stayed.
04 — Plan

How the work unfolds

Weeks 1–2

Audit

Read-only. Every server and every dependency, including the ones not in the documentation. This stage takes longer than clients expect and saves more than any other.

Weeks 2–3

Identity design and hybrid setup

Entra ID design agreed, directory synchronisation established, sign-in tested with a pilot group before anyone else is affected.

Weeks 3–5

Mail migration

Mailboxes move to Exchange Online in batches, hybrid mail flow maintained throughout.

Weeks 4–8

Files and SharePoint

File server and farm content moves into the agreed structure. Users keep working from the old location until each wave completes.

Per dependency

Application remediation

Each item on the dependency register is resolved, worked around or explicitly accepted. Nothing is switched off with an open item against it.

Your schedule

Decommission

Servers retired one at a time against the checklist, after verification. Hybrid identity is usually the last thing to go, and only when you decide.

What is still in the server room?

A list of servers and what you think they do is enough to start. The audit finds the rest — and the servers that should be retired rather than moved.

From £800 / €950 / $1,000 · 1–4 months
05 — Before we start

What we need from you

Domain Administrator access and access to the on-premises Exchange and SharePoint estates
A named owner for each line-of-business application, or acceptance that unowned ones are treated as at risk
A decision on what stays on-premises deliberately, if anything
Network and firewall visibility for the sync and migration paths
A realistic view of the deadline driving the project — a lease end date changes the sequence
06 — Working together

Who does what

IT Partner

  • Audit the estate and build the dependency register
  • Design and implement Entra ID and hybrid identity
  • Migrate mailboxes, files and SharePoint content
  • Test sign-in with a pilot group before broad rollout
  • Produce the decommission checklist and verify against it
  • Report what moved, what was retired and what stayed

Your team

  • Provide administrative and network access
  • Name application owners
  • Decide what is archived rather than migrated
  • Approve each decommission after verification
  • Own vendor conversations for line-of-business applications
  • Tell users, using our draft
07 — Scope

What is not included

×Line-of-business application re-engineering. We find the dependency and propose the resolution; rewriting the application is a separate project with its vendor.
×Network redesign. Firewall and routing changes are yours or your network partner’s.
×Hardware disposal. Decommissioning is logical, not physical.
×Azure infrastructure design at scale. Where servers move to Azure rather than retire, see Azure infrastructure.
×Backup platform replacement. Inventoried and pointed at; selecting and implementing a new one is scoped separately.
08 — Fine print

Limitations and technical notes

!The audit finds things nobody documented. On every project of this kind. Budget time for resolving them rather than assuming the documentation is complete.
!Service accounts are the commonest blocker. An account with a password nobody knows, used by a process nobody owns, that stops working the day the domain controller goes.
!Some applications only speak LDAP. Entra Domain Services can replace a domain controller whose only remaining job is serving LDAP to one application — we have done exactly that.
!Hybrid identity is usually the last thing to retire, not the first. Removing directory synchronisation before every dependency is resolved is how projects create outages.
!File server permissions rarely map cleanly. Deep NTFS structures with per-folder exceptions need a decision about the target structure, not a copy.
!A lease end date is a hard constraint. If the deadline and the scope conflict, you hear it during the audit while there is still time to negotiate the lease.
09 — Questions

Asked on almost every first call

Can we keep some things on-premises?

Yes, and sometimes you should. The point is that whatever stays does so because someone decided, not because it was forgotten. The dependency register makes that explicit.

What happens to applications that need a domain controller?

They are found during the audit and each gets a resolution. Where the application only needs LDAP, Entra Domain Services can replace the server entirely — we have done that on a live project rather than in theory.

How long does it take?

Four to six weeks for a small estate. Two to four months for a mid-sized one with Exchange, file servers and SharePoint. The audit and the dependency remediation vary far more than the data movement does.

What does it cost?

From £800 / €950 / $1,000, quoted as a fixed price after the audit. Scoping costs nothing. The audit itself is where the price becomes accurate, which is why we do not quote before it.

Will users notice?

Sign-in should behave the same way on day one, which is the design goal of the identity work. What users do notice is where files live, so that is where the communication effort goes.

Can you decommission the servers for us?

We produce the checklist, verify against it, and confirm what is safe to retire. You press the button, because switching off a server should always be a client decision.

10 — Related

Worth reading next

Scoping costs nothing

Tell us the shape of it and we will tell you what it involves

Answer the form or write to us. You get back a written scope, a sequence and a fixed price — usually within one business day, and nobody rings you unless you ask.