Microsoft 365 Migration from
On-Premise or Legacy Environment
Your email and file data, moved from wherever it lives now to a properly configured Microsoft 365 environment — with planning, a tested migration, and a hardened tenant delivered in a single coordinated engagement.
Indicative Pricing
Example: 20-user firm — £2,500 + (10 × £90) = £3,400 + VAT
Payment: 40% on commencement · 30% on Migration Plan approval · 30% on Go-Live
Supported platforms: Exchange 2013+, Google Workspace, Office 365
Three phases. Nothing rushed.
Migration is the highest-risk engagement in the Microsoft 365 portfolio. The three-phase structure exists to protect your data and your organisation — discovery and planning before any data moves, verification after it does.
Before a single byte of data moves, the plan is agreed in writing.
- Assessment of the existing environment — email platform, file storage, user directory, data volumes, and any known complications
- Production of the Migration Plan: scope, approach, tooling, migration schedule, pre-migration data baseline, and rollback provisions
- Agreement of the data completeness baseline against which post-migration verification will be measured
- Agreement of the migration window, including any out-of-hours scheduling required to minimise disruption
- Client written approval of the Migration Plan before Phase 2 or Phase 3 commences — no data moves without your sign-off
The Migration Plan is a deliverable, not an internal document. It is produced in PDF, reviewed with you, and signed off before any work proceeds to Phase 3.
The destination environment, built correctly before the data arrives.
- Microsoft Entra ID — user accounts, MFA enforcement, Conditional Access, guest governance, privileged identity management
- Exchange Online — mailbox provisioning, email routing, DNS configuration, retention policy, anti-spam and anti-phishing baseline
- SharePoint Online and OneDrive — site structure, permissions governance, sharing policy, Known Folder Move
- Microsoft Teams — governance policy, meeting controls, guest access
- Microsoft Defender for Business — activation, security baseline, endpoint protection policy
- Microsoft Purview — sensitivity labels, data loss prevention policy, audit logging
Phase 2 runs concurrently with Phase 3 preparation where technically appropriate, reducing total elapsed time.
The cutover, the verification, and the handover.
- Email data migration from the existing platform to Exchange Online — folder structure preserved, message metadata preserved where technically feasible
- File data migration from existing storage to SharePoint Online and OneDrive — folder structure and permission assignments preserved where feasible
- Post-migration verification against the agreed baseline — data completeness confirmed in writing
- DNS cutover — MX and Autodiscover records updated to route mail to Exchange Online
- Legacy email routing decommission following confirmed Go-Live
- Administrator handover session — up to ninety minutes covering the complete environment
Migration is not a lossless process. Certain metadata and permission structures may not survive depending on the source platform. Konve IT will advise on known limitations specific to your environment during Phase 1, before commitment to Phase 3.
Three written deliverables. One handover session.
Everything is documented. Before the migration, during, and after.
Migration Plan
Produced at the end of Phase 1. Sets out the migration scope, approach, tooling, data completeness baseline, migration schedule, and rollback provisions. Requires your written approval before migration commences. This document protects both parties.
Post-Migration Verification Report
Produced on completion of Phase 3. Confirms data completeness against the agreed pre-migration baseline and documents any items that could not be migrated and why. Provides the audit trail required for regulated firms.
Tenant Configuration Document
Produced on Go-Live. A complete record of every configuration decision made during the deployment — the security baseline applied, administrator guidance, and a statement of Cyber Essentials alignment at the point of delivery.
Moving from legacy infrastructure to Microsoft 365.
This engagement is specifically for organisations moving email and file data from an existing platform. If your tenant is already on Microsoft 365 but needs hardening, the Tenant Deployment and Hardening or Compliance-Aligned Remediation engagements are the right starting point.
You are running on-premise Exchange and it is time to move to the cloud.
Your on-premise Exchange server is ageing, unsupported, or approaching end-of-life. Moving to Exchange Online is the right decision. This engagement handles the migration, the tenant deployment, and the DNS cutover — with your data verified against a baseline before the old system is decommissioned.
You are moving from Google Workspace to Microsoft 365.
Your organisation has decided to standardise on Microsoft 365. The migration involves email, calendar, contacts, and file data from Google Drive to SharePoint and OneDrive. Konve IT has handled this transition before and understands the specific limitations of Google-to-Microsoft data migration.
You are a professional services firm with legacy infrastructure and regulatory obligations.
Your migration needs to land in an environment that is aligned to SRA, ICAEW, or GDPR requirements from day one. The destination tenant is configured against your regulatory context — not a generic baseline that someone else will need to remediate later.
A previous migration attempt left you with an inconsistent or ungoverned environment.
A prior migration — handled internally or by a previous provider — delivered the data but left the destination environment poorly configured. This engagement rebuilds the tenant correctly and migrates any data that was missed or corrupted in the original attempt.
Migration scope is agreed in the Migration Plan. Anything below requires either inclusion in the Plan before signature, or a separate change order.
- Migration from third-party SaaS platforms not confirmed in the SoW
- Migration of application data or line-of-business databases
- Decommissioning of on-premise servers beyond DNS changes
- Intune device enrolment and endpoint management
- Advanced email security — Mimecast or Proofpoint
- Cyber Essentials certification submission
- Procurement or payment of Microsoft 365 licences
- Helpdesk, end-user support, or break-fix
- Ongoing management following Go-Live
- Changes to scope after Migration Plan approval
Three payment milestones — one for each phase gate.
Migration engagements use three payment milestones rather than two because the Migration Plan approval is a genuine gate. You have reviewed and signed off the plan before the second instalment falls due — and before any data moves.
Microsoft 365 Migration from On-Premise or Legacy Environment
Payment Milestones
Due before Phase 1 begins. Covers discovery, assessment, and Migration Plan production.
Due on your written approval of the Migration Plan. No data moves until this milestone is paid and the Plan is signed.
Due on Go-Live — or within five working days of Konve IT confirming Go-Live in writing.
Three steps to a signed Statement of Work.
The questionnaire for this engagement is more detailed than most — it needs to capture your source environment, data volumes, and timeline constraints. Complete it as fully as you can and Konve IT will fill any gaps during Phase 1.
Complete the onboarding form
Download and complete the Konve IT Client Onboarding Form. Captures your organisation details, contacts, and regulatory context.
Complete the service questionnaire
Download and complete the Microsoft 365 Tenancy Questionnaire, selecting the Migration variant. Captures source platform, data volumes, user count, DNS access, and timeline requirements.
Review and sign the Statement of Work
Konve IT reviews your responses and issues a Statement of Work within two working days. On signature and receipt of the first instalment, Phase 1 — discovery and Migration Plan production — commences.