SharePoint, OneDrive & Full Microsoft 365 Migration in the UK

Migrating an entire organisation to Microsoft 365 is far more than switching on a few cloud licences and pointing users at a new login page. When the scope extends beyond email to encompass SharePoint Online, OneDrive for Business, file server decommissioning, and the full suite of collaborative workloads, the complexity multiplies dramatically — and so does the potential for disruption if the migration is handled without proper planning, tooling, and expertise.

For UK businesses, the stakes are particularly high. Data residency obligations under UK GDPR, sector-specific compliance requirements from regulators like the FCA and ICO, and the sheer volume of unstructured data accumulated across years of on-premises file servers and legacy SharePoint farms mean that a Microsoft 365 migration London project — or indeed any full-scope M365 migration anywhere in Britain — demands a methodical, phased approach that accounts for every document library, every permission set, every metadata column, and every user workflow that depends on existing file structures.

At Cloudswitched, a London-based managed service provider, we have delivered hundreds of full-scope Microsoft 365 migrations for organisations across the United Kingdom. From 20-person professional services firms in the City to 2,000-seat enterprises with offices in Manchester, Birmingham, Leeds, and Edinburgh, we have encountered every permutation of legacy environment, every edge case in permissions inheritance, and every variant of "we tried to do it ourselves and now nothing works." This guide distils that experience into a comprehensive, actionable resource covering every aspect of SharePoint, OneDrive, and full M365 migration — written specifically for British businesses, with British spelling, British compliance considerations, and references to the regional IT landscapes that shape how organisations in different parts of the UK approach cloud transformation.

Whether you are planning an email migration Manchester project that also needs to bring across SharePoint sites, or a comprehensive SharePoint migration services UK engagement that covers document libraries, workflows, custom lists, and InfoPath forms, this guide walks you through every phase — from initial discovery and environment assessment, through data classification, permissions mapping, pilot migration, full cutover, and post-migration optimisation. We address the specific challenges that arise when migrating from SharePoint 2013, 2016, and 2019 on-premises, from traditional Windows file servers with deeply nested NTFS permission trees, and from third-party platforms like Google Workspace, Dropbox Business, and Box.

The guide is structured around the migration lifecycle as we practise it at Cloudswitched: assess, plan, prepare, migrate, validate, optimise. Each phase contains detailed technical guidance, real-world examples from UK client engagements, and the specific pitfalls that catch organisations off guard when they attempt these migrations without specialist support. Let us begin with the fundamental question every UK business needs to answer before a single file moves to the cloud.

Understanding Full-Scope Microsoft 365 Migration

A full-scope Microsoft 365 migration encompasses every workload that an organisation needs to move from its current environment to the M365 cloud platform. For most UK businesses, this means far more than email — it means migrating the entire digital workplace. Understanding the full scope before you begin is critical, because underestimating the breadth of migration is the single most common cause of project overruns, budget blowouts, and user dissatisfaction.

The Workloads That Constitute a Full M365 Migration

Exchange Online (email, calendars, contacts): The most visible workload. Every user mailbox, shared mailbox, resource mailbox, distribution list, and mail-enabled security group needs to be migrated. Calendar data, contacts, rules, signatures, and delegate permissions all need to transfer accurately. For organisations moving from on-premises Exchange, this includes decommissioning the legacy Exchange servers and updating DNS records — MX, autodiscover, SPF, DKIM, and DMARC.

SharePoint Online (document management, intranets, team sites): This is where complexity escalates rapidly. A typical mid-sized UK organisation may have dozens of SharePoint site collections, hundreds of document libraries, thousands of custom permissions, and workflows built on SharePoint Designer or Power Automate. Migrating all of this whilst preserving metadata, version history, and permissions is a significant undertaking. SharePoint migration services UK providers like Cloudswitched invest heavily in tooling and methodology specifically because this workload is so prone to data loss and permission breakage when handled incorrectly.

OneDrive for Business (personal file storage): Every user's personal files — previously stored on local drives, home drives on file servers, or personal SharePoint sites — need to move to OneDrive. The OneDrive migration services UK scope includes mapping home drive paths to OneDrive accounts, handling files that exceed OneDrive's path length and character restrictions, and training users on the new sync client. For many users, this is the most disruptive change in the entire migration, because it affects how they save and access files every single day.

File server decommissioning: Many UK organisations still run Windows file servers — sometimes dozens of them, accumulated over years of organic growth, mergers, and acquisitions. These file servers typically contain terabytes of data with complex NTFS permission hierarchies that have been layered over years by successive IT administrators. Migrating this data to SharePoint document libraries and OneDrive requires careful mapping of NTFS permissions to SharePoint permission levels, resolution of permission inheritance conflicts, and identification of data that should be archived rather than migrated.

Teams, Planner, Power Platform: Whilst these services are provisioned automatically with M365 licences, configuring them properly — Teams governance policies, channel structures, Planner integration, Power Automate flows that replace legacy workflows — is part of the overall migration scope that organisations frequently underestimate.

Phase 1: Discovery and Environment Assessment

Every successful migration begins with discovery. At Cloudswitched, we consider the assessment phase to be the single most important determinant of migration success — more important than the migration tooling, more important than the cutover schedule, and more important than the post-migration support plan. The reason is simple: problems identified during discovery can be solved calmly and systematically. Problems discovered during migration cause panic, delays, and data loss.

SharePoint On-Premises Assessment

If your organisation is migrating from SharePoint on-premises (2013, 2016, or 2019), the assessment must cover every aspect of your existing farm. This is not a five-minute scan — for a typical mid-sized UK business, a thorough SharePoint assessment takes two to five days of dedicated effort.

Site collection inventory: Document every site collection, including its URL, template, size, last modified date, and owner. Pay particular attention to site collections that have been inactive for more than 12 months — these are candidates for archival rather than migration, and excluding them from the migration scope reduces both cost and risk.

Document library analysis: For each site collection, catalogue every document library. Record the number of documents, total size, whether versioning is enabled (and how many versions are retained), whether check-in/check-out is enforced, and any custom columns or content types defined on the library. Custom content types are particularly important because they may reference site columns that exist at the site collection level, and these dependencies must be preserved during migration.

Permissions audit: This is where most migration projects encounter their first major challenge. SharePoint on-premises environments that have been in use for years typically have permissions structures that have drifted far from their original design. You will find broken inheritance at the folder and document level, users granted direct permissions instead of being added to groups, SharePoint groups with overlapping membership, and permissions granted to Active Directory groups that no longer contain the correct members. All of this must be documented and rationalised before migration begins.

Customisations and workflows: Document every customisation — master pages, page layouts, custom web parts, SharePoint Designer workflows, InfoPath forms, and any custom solutions deployed as WSP packages or sandbox solutions. Many of these customisations will not migrate directly to SharePoint Online and will need to be rebuilt using modern equivalents (SPFx web parts, Power Automate flows, Power Apps forms). Identifying these early prevents last-minute surprises during migration.

File Server Assessment

File server assessment is equally critical, particularly for organisations planning to decommission on-premises file servers as part of their M365 migration. British businesses frequently have file server estates that have grown organically over decades, with permission structures that no single person fully understands.

Share enumeration: Identify every shared folder on every file server. Include hidden administrative shares, departmental shares, project shares, and home drive mappings. For each share, record the UNC path, total size, file count, deepest folder nesting level, and longest file path. SharePoint Online and OneDrive have specific limitations — 400 characters for the full URL path, restrictions on certain special characters, and a maximum of 30 million items per library — and your assessment needs to identify any data that would violate these constraints.

NTFS permissions mapping: Export the full NTFS permission tree for every share. This needs to capture both explicit permissions and inherited permissions, because the migration to SharePoint requires translating NTFS permission levels (Full Control, Modify, Read & Execute, List Folder Contents, Read, Write) into SharePoint permission levels (Full Control, Design, Edit, Contribute, Read, View Only). The mapping is not one-to-one, and decisions about how to handle edge cases — particularly where NTFS permissions combine deny entries with allow entries — need to be made during planning, not during the heat of migration.

Data classification: Not everything on your file servers should migrate to the cloud. Temporary files, duplicate copies, outdated project archives, and personal files that violate acceptable use policies should be identified and excluded. We typically find that 25–40% of file server data is either duplicate, obsolete, or trivial (ROT data), and removing it from the migration scope significantly reduces both migration time and ongoing storage costs.

Phase 2: Planning the Migration Architecture

With discovery complete, the next phase is designing the migration architecture — determining exactly how your on-premises data structures will map to Microsoft 365's cloud architecture. This is where strategic decisions are made that will affect your organisation for years to come, so it is worth investing the time to get it right.

SharePoint Information Architecture Design

The transition from SharePoint on-premises to SharePoint Online is not a simple lift-and-shift. SharePoint Online has a fundamentally different architecture in several key respects, and understanding these differences is essential for planning a successful migration.

Hub sites replace managed paths: In SharePoint on-premises, organisations typically used managed paths to create a hierarchical site collection structure — for example, /sites/Finance, /sites/HR, /sites/Marketing. In SharePoint Online, hub sites provide a flat-but-connected architecture where any site can be associated with a hub for shared navigation, search, and branding. Planning your hub site structure before migration prevents the need for disruptive restructuring after go-live.

Modern vs classic experience: SharePoint Online has been progressively moving towards the modern experience, and Microsoft has indicated that classic pages will eventually be retired. If your on-premises SharePoint farm uses classic pages extensively — and most long-established farms do — you need to plan for the conversion to modern pages as part of the migration. This affects page layouts, web parts, and the overall look and feel of your intranet.

Document library mapping: The most consequential decision in any SharePoint migration services UK project is how to map existing document libraries, folders, and files to the SharePoint Online and OneDrive structure. The options include:

OneDrive Mapping Strategy

For OneDrive migration services UK engagements, the mapping strategy determines where each user's files end up. The most common scenarios are:

Home drives to OneDrive: Each user's H: drive (or equivalent mapped network drive) migrates directly to their OneDrive for Business library. This is the cleanest mapping, but it requires that every user's home drive content is genuinely personal. Shared folders within home drives need to be identified and redirected to SharePoint team sites instead.

Departmental shares to SharePoint team sites: Shared departmental folders — typically mapped as S: or G: drives — migrate to SharePoint Online team sites connected to Microsoft 365 Groups. Each department gets its own site with document libraries that mirror the logical structure of the original file share. Permissions transfer from NTFS security groups to M365 Groups and SharePoint permission levels.

Project shares to SharePoint sites or Teams: Project-specific file shares can map to either dedicated SharePoint sites or Microsoft Teams channels, depending on whether the project team also needs chat, meetings, and task management capabilities alongside file storage.

Permissions Mapping Framework

Permissions mapping is the most technically demanding aspect of any full M365 migration. The fundamental challenge is that NTFS permissions and SharePoint permissions use different models, and the translation between them is not always straightforward.

Active Directory group to M365 Group mapping: Every AD security group that appears in NTFS ACLs needs to be mapped to an equivalent M365 Group or Azure AD security group. If your organisation is implementing Azure AD Connect (now Entra Connect) as part of the migration, many of these groups will synchronise automatically. However, groups that exist only in on-premises AD — local domain groups, distribution groups used for permissions, and groups with special characters in their names — may require manual creation in Azure AD.

For organisations running email migration Manchester or email migration Birmingham projects as part of a broader M365 rollout, the permissions planning phase is where email distribution lists, shared mailbox access, and calendar permissions intersect with file-level permissions. A unified identity and access plan that covers both email and file workloads prevents the common scenario where users have access to their email but cannot reach their files, or vice versa.

Phase 3: Licensing, Tenant Configuration, and Compliance

Before any data moves, your Microsoft 365 tenant must be properly configured and licensed. For UK businesses, this phase includes compliance and data residency considerations that are specific to the British regulatory environment.

Licensing for Full M365 Migration

Microsoft 365 licensing is notoriously complex, and choosing the wrong licence tier is one of the most expensive mistakes an organisation can make. For a full-scope migration covering email, SharePoint, OneDrive, and Teams, the relevant licence tiers are:

Microsoft 365 Business Basic (£4.50/user/month): Includes Exchange Online, SharePoint Online, OneDrive (1 TB per user), and Teams. Suitable for organisations that do not need desktop Office applications and have straightforward compliance requirements. Does not include advanced security features or eDiscovery.

Microsoft 365 Business Standard (£9.40/user/month): Adds desktop Office applications (Word, Excel, PowerPoint, Outlook). The most common choice for UK SMBs with up to 300 users. Includes everything needed for a full migration, but lacks advanced compliance and security features.

Microsoft 365 Business Premium (£16.60/user/month): Adds Intune device management, Azure Information Protection, and advanced threat protection. Recommended for organisations in regulated sectors or those handling sensitive personal data under UK GDPR.

Microsoft 365 E3 (£28.40/user/month): Enterprise tier with unlimited OneDrive storage, advanced eDiscovery, data loss prevention, and information barriers. Required for organisations with more than 300 users and those with stringent compliance requirements. This is the most common licence tier for Microsoft 365 migration London projects involving large professional services firms, financial institutions, and public sector organisations.

Microsoft 365 E5 (£47.20/user/month): Adds Power BI Pro, advanced analytics, Phone System, and Microsoft Defender for Office 365 Plan 2. Typically only justified for organisations with specific telephony or advanced security requirements.

UK Data Residency and Compliance

Since Brexit, UK businesses must ensure that personal data processed and stored in Microsoft 365 complies with the UK GDPR (the Data Protection Act 2018 as amended) rather than the EU GDPR. Microsoft has committed to storing core customer data for UK tenants within UK data centres (located in London and Durham), but organisations need to verify this configuration during tenant setup.

Data residency verification: In the Microsoft 365 admin centre, navigate to Settings > Org Settings > Organization Profile > Data Location to confirm that your tenant's data is stored in the United Kingdom. For organisations that require contractual guarantees, Microsoft offers the Advanced Data Residency add-on, which provides a committed data residency guarantee for a broader range of workloads.

UK GDPR considerations: Your migration plan must include a Data Protection Impact Assessment (DPIA) if the migration involves large-scale processing of personal data — which, for most organisations migrating email and files, it does. The DPIA should address how personal data will be protected during migration (encryption in transit and at rest), who will have access to migrated data, and how data subject rights (access, rectification, erasure) will be maintained throughout the migration process.

Retention policies: Configure Microsoft 365 retention policies before migration to ensure that data governance requirements are met from day one. This includes retention labels for different document types, litigation hold for any ongoing legal matters, and auto-apply retention policies that classify documents based on sensitive information types relevant to your industry.

Phase 4: SharePoint Online Migration — Document Libraries, Metadata, and Permissions

SharePoint migration is the most technically complex workload in any full M365 migration. The volume of data, the intricacy of permissions structures, the importance of preserving metadata, and the variety of customisations that need to be addressed make this a workload that demands specialist expertise and enterprise-grade tooling. This is the core of what SharePoint migration services UK providers deliver, and it is where the difference between a properly planned migration and a rushed one becomes starkly apparent.

Migration Tooling Selection

The choice of migration tool has a significant impact on the quality and speed of SharePoint migration. The major options available to UK businesses are:

SharePoint Migration Tool (SPMT): Microsoft's free migration tool. Suitable for simple migrations from SharePoint 2013+ and file shares, but limited in its handling of permissions, metadata, and large-scale migrations. Does not support incremental migration well, which means it is difficult to use for phased migrations where users continue working in the source environment during the migration period.

ShareGate (now part of GSX): A mature third-party tool popular with UK MSPs and IT teams. Excellent permissions mapping, metadata preservation, and incremental migration support. Handles SharePoint-to-SharePoint migration very well, including custom content types, managed metadata, and workflows. The licensing model (per-migration-seat) makes it cost-effective for mid-sized projects.

Quest/Metalogix: Enterprise-grade migration platform with extensive pre-migration analysis, automated remediation, and detailed reporting. Best suited for large organisations with complex SharePoint farms and stringent compliance requirements. Higher cost but provides the most comprehensive migration capabilities.

Microsoft Migration Manager: Cloud-based migration service built into the SharePoint admin centre. Good for file share to SharePoint Online migrations, with recent improvements to SharePoint on-premises support. Free to use but requires migration agents installed on-premises.

Document Library Migration Process

The process of migrating document libraries from SharePoint on-premises to SharePoint Online follows a structured sequence that Cloudswitched has refined over hundreds of UK migration projects:

Step 1 — Pre-migration scan: Run the migration tool's assessment against each source document library. This identifies files that will fail migration due to path length, invalid characters, blocked file types, or size limits. Address all flagged items before proceeding.

Step 2 — Content type and column provisioning: Create all required content types, site columns, and managed metadata term sets in the destination SharePoint Online environment before migrating any documents. Documents that reference content types or columns that do not exist in the destination will either fail or lose their metadata.

Step 3 — Permissions pre-staging: Create all required SharePoint groups, M365 Groups, and Azure AD security groups in the destination. Map source permissions to destination permissions using the mapping framework established during the planning phase. Verify the mapping with stakeholders from each department before proceeding.

Step 4 — Pilot migration: Migrate a representative subset of document libraries — typically one from each department — and validate the results thoroughly. Check that all documents transferred, that metadata is correct, that version history is preserved, that permissions are accurate, and that any custom views or default column values are intact.

Step 5 — Full migration: Execute the full migration in waves, typically organised by department or site collection. Run migrations during off-peak hours (typically overnight and over weekends for UK businesses) to minimise network impact. Use incremental migration to capture changes made to source libraries after the initial migration pass.

Step 6 — Validation and sign-off: After each wave, conduct systematic validation against the pre-migration inventory. Compare document counts, folder structures, permission assignments, and metadata values. Obtain formal sign-off from department heads before decommissioning source sites.

Metadata Preservation Strategies

Metadata is the lifeblood of any document management system, and preserving it during migration is non-negotiable for organisations that depend on document classification, search, and compliance. The specific challenges that arise during SharePoint-to-SharePoint-Online migration include:

Managed metadata term sets: If your on-premises SharePoint farm uses the managed metadata service (taxonomy), all term sets, terms, and their hierarchical relationships must be recreated in the SharePoint Online term store before migration. Migration tools can automate this, but they often struggle with term sets that have been modified extensively over the years, particularly those with deprecated terms, orphaned terms, or terms with special characters.

Custom content types: Content types defined at the site collection level in on-premises SharePoint must be recreated at the equivalent level in SharePoint Online. If your information architecture uses content type publishing (where content types are defined in a hub and published to subscribing site collections), this functionality needs to be replicated using the SharePoint Online content type hub.

Created/Modified timestamps: By default, migrated documents retain their original Created and Modified dates, but only if the migration tool correctly sets these values using the SharePoint migration API. Some tools and some migration methods (particularly manual upload) reset these dates to the migration date, which can cause significant problems for organisations that rely on these timestamps for compliance, retention, or operational purposes.

Version history: SharePoint Online supports version history, but there are practical limits. Migrating documents with hundreds of versions can be extremely slow and may not be necessary. Discuss with stakeholders how many versions to preserve — in most cases, migrating the current version plus the last 5–10 major versions is sufficient for operational and compliance purposes.

Phase 5: OneDrive for Business Migration

OneDrive for Business migration is often underestimated because it appears simpler than SharePoint migration — after all, it is just personal files, right? In practice, OneDrive migration services UK projects present their own set of challenges, particularly when migrating from traditional file server home drives that have accumulated years of data, nested folders, and inconsistent naming conventions.

Source Environment Considerations

Home drive migration: The most common source for OneDrive migration is the Windows file server home drive — the H: drive that users have been saving files to for years. These drives typically contain a mix of genuine work documents, personal files, application data, cached files, and forgotten downloads. Before migration, each home drive should be scanned for:

Files that exceed OneDrive's 250 GB individual file size limit (rare but it happens with database files and virtual machine images). Files with invalid characters in their names — OneDrive prohibits characters including " * : < > ? / \ | and leading/trailing spaces. Files with paths that, when combined with the OneDrive URL prefix, would exceed 400 characters. PST files, which should be migrated to Exchange Online archive mailboxes rather than OneDrive. Application data files that are locked or constantly changing, which will cause sync conflicts.

Google Drive migration: For organisations migrating from Google Workspace to Microsoft 365, Google Drive to OneDrive migration requires converting Google-native file formats (Docs, Sheets, Slides) to their Microsoft equivalents (Word, Excel, PowerPoint). Most migration tools handle this conversion automatically, but formatting differences — particularly in complex spreadsheets with Google Sheets-specific functions — need to be reviewed and corrected manually.

Dropbox and Box migration: Some UK organisations have adopted Dropbox Business or Box as their primary cloud storage, often alongside an existing Microsoft 365 subscription. Migrating from these platforms to OneDrive requires extracting sharing links, comments, and folder-level permissions that may not have direct equivalents in OneDrive.

OneDrive Sync Client Deployment

The OneDrive sync client (OneDrive.exe) is the primary interface through which users interact with their OneDrive files on Windows and macOS. Deploying and configuring the sync client correctly is essential for a smooth user experience post-migration.

Known Folder Move (KFM): One of the most valuable features for OneDrive migration services UK projects is Known Folder Move, which automatically redirects the Windows Desktop, Documents, and Pictures folders to OneDrive. This ensures that users' most important files are automatically backed up and synced without changing their workflow. KFM can be deployed silently via Group Policy or Intune, and it should be enabled as part of the migration rollout.

Files On-Demand: OneDrive Files On-Demand allows users to see all their files in File Explorer without downloading them, reducing local storage requirements. Files are downloaded on-demand when opened. This feature is particularly valuable for users with large OneDrive libraries or limited local storage, and it should be enabled by default for all users.

Sync client configuration: Use Group Policy or Intune to configure sync client settings including: bandwidth throttling during business hours, automatic sign-in with Windows credentials, blocking sync of specific file types (e.g., .pst files), and enabling the sync client to sync SharePoint team sites as well as OneDrive. These settings ensure consistent behaviour across the organisation and prevent the sync client from consuming excessive bandwidth or storage.

User Communication and Training

For many users, the move from a mapped network drive (H: or G:) to OneDrive represents the most visible change in the entire Microsoft 365 migration. Unlike email — where Outlook looks and feels largely the same after migration — the file access experience changes fundamentally. Users need to understand how to access files through File Explorer (via the sync client), through the OneDrive web interface, through the OneDrive mobile app, and through the OneDrive integration in Office applications.

Cloudswitched provides structured change management support for every OneDrive migration, including pre-migration communications explaining what is changing and why, video tutorials demonstrating the new file access workflows, drop-in support sessions during the first week after migration, and a dedicated helpdesk queue for migration-related issues. This investment in user communication consistently reduces support ticket volume by 60–70% compared to migrations that rely on a single email announcement.

Phase 6: File Server to Cloud Migration

For many UK businesses, the file server to cloud migration is the largest and most consequential workload in the entire M365 project. File servers that have been in continuous use for a decade or more contain terabytes of data, thousands of folders, and permission structures that reflect every organisational change, merger, and IT administration decision made over that period. Decommissioning these servers and moving their contents to SharePoint Online and OneDrive requires careful planning, robust tooling, and meticulous execution.

File Server Migration Strategy

The first strategic decision is how to map file server shares to Microsoft 365 destinations. There is no single correct answer — the right approach depends on how the data is used, who needs access, and how the organisation wants to manage it going forward.

Departmental shares to SharePoint team sites: Shared departmental folders (e.g., \\server\Finance, \\server\HR, \\server\Marketing) typically map best to SharePoint Online team sites connected to M365 Groups. Each department gets a dedicated site with document libraries that replicate the logical structure of the original share. The M365 Group membership replaces the NTFS security group that controlled access to the share.

Project shares to Teams/SharePoint: Project-specific shares that are actively used by cross-functional teams often map well to Microsoft Teams channels, which provide file storage (backed by SharePoint) alongside chat, meetings, and task management. Archived project shares that are retained for reference but no longer actively used should go to SharePoint sites with read-only permissions.

Personal folders to OneDrive: Any personal or user-specific folders on file servers should migrate to the corresponding user's OneDrive. This includes home drives, personal project folders, and any other data that belongs to a single user.

Archive data to Azure Blob Storage or SharePoint: Data that must be retained for compliance or legal reasons but is rarely accessed should be evaluated for archival. For data that does not need to be searchable through SharePoint search, Azure Blob Storage provides a cost-effective cold storage option. For data that needs to remain searchable, a dedicated SharePoint site with appropriate retention policies is more suitable.

Handling Complex NTFS Permissions

NTFS permissions on long-established file servers are often the single biggest source of migration complexity. Over years of use, permissions tend to become layered, inconsistent, and difficult to understand. Common patterns we encounter during SharePoint migration services UK projects include:

Broken inheritance at multiple levels: Permissions inheritance was broken at folder and subfolder levels to grant access to specific teams or individuals, creating a patchwork of explicit permissions that no longer reflects the organisation's current structure. During migration, these need to be rationalised — in many cases, the broken inheritance is no longer needed and the permissions can be simplified.

Deny entries: NTFS supports deny permissions, which take precedence over allow permissions. SharePoint does not have a direct equivalent of deny permissions, so these must be handled through alternative means — typically by restructuring the data so that the denied content is in a separate library with restricted access.

SID history and orphaned SIDs: After domain migrations, mergers, or user account recreation, file servers often contain ACL entries that reference SIDs (Security Identifiers) that no longer resolve to active accounts. These need to be cleaned up before migration, as the migration tool will not be able to map orphaned SIDs to destination accounts.

Nested group memberships: Complex nested group structures — where Group A contains Group B, which contains Group C — need to be replicated in Azure AD or simplified during migration. Circular group nesting (where Group A contains Group B and Group B contains Group A) will cause migration failures and must be resolved.

Data Deduplication and Cleanup

Before migrating terabytes of file server data to the cloud, invest time in data cleanup. Cloud storage is not free, and migrating duplicate, obsolete, and trivial data wastes bandwidth, extends the migration timeline, and increases ongoing storage costs.

Duplicate detection: Use tools like TreeSize Professional, WinDirStat, or the file analysis features built into migration tools to identify duplicate files. In a typical file server environment, 15–25% of data is duplicate — the same document saved in multiple locations, often with slightly different names. Deduplicate before migration, not after.

Stale data identification: Files that have not been accessed in three or more years are candidates for archival rather than migration. Generate last-access-date reports for all file shares and present the findings to department heads for decisions about what to archive and what to migrate.

Policy enforcement: Use the migration as an opportunity to enforce data management policies. Remove personal media files, application installers, and other data that violates acceptable use policies. Block migration of known problematic file types (e.g., .pst files, .ost files, temporary files, system files) using the migration tool's exclusion rules.

Regional Migration Services Across the United Kingdom

The United Kingdom's technology landscape is not monolithic. Different regions have distinct business demographics, industry concentrations, and IT infrastructure characteristics that affect how Microsoft 365 migrations are planned and executed. Understanding these regional nuances is important for organisations that operate across multiple UK locations or are selecting a migration partner for a specific region.

Microsoft 365 Migration London

London is the UK's largest market for Microsoft 365 migration London services, driven by the concentration of financial services firms, professional services practices, media companies, and technology businesses in the capital. London migrations tend to have several distinctive characteristics:

Regulatory complexity: London's financial services sector — including banks, asset managers, insurance companies, and fintech firms — must comply with FCA, PRA, and Bank of England requirements around data handling, operational resilience, and third-party dependency management. M365 migrations for these organisations require detailed regulatory impact assessments, formal approval processes, and post-migration compliance verification.

Multi-tenancy and shared infrastructure: Many London businesses occupy serviced offices or shared buildings where IT infrastructure (internet connections, server rooms, network equipment) is shared with other tenants. Migration planning must account for bandwidth constraints in shared environments and coordinate with building management to schedule bandwidth-intensive migration activities during off-peak periods.

International workforce: London's diverse workforce means that migration communications and training materials often need to be available in multiple languages, and user support must accommodate different time zones for staff who travel frequently or work remotely from overseas.

Cloudswitched is headquartered in London and has deep experience with the specific challenges that London businesses face. Our proximity means we can provide on-site support during critical migration phases — something that is often essential for large-scale migrations where user adoption and change management require face-to-face interaction.

Email Migration Manchester

Manchester is the UK's second-largest digital economy, with a thriving technology sector, a strong manufacturing base, and growing professional services and creative industries. Email migration Manchester projects frequently involve organisations that have grown rapidly and have IT estates that reflect that growth — multiple email systems, fragmented file storage, and infrastructure that has been added piecemeal over the years.

Manufacturing and logistics: Manchester's manufacturing and logistics firms often have a mix of office-based workers who need full M365 functionality and operational staff who need limited email access on shared devices or mobile phones. Migrations must accommodate these different user profiles with appropriate licences, device configurations, and training approaches.

Multi-site operations: Many Manchester-based organisations have offices, warehouses, or production facilities across the North West and beyond. The migration plan must account for varying internet connectivity at different sites, with some locations having full fibre and others relying on slower connections that will constrain migration throughput.

Growing tech sector: Manchester's technology companies often migrate from Google Workspace or other cloud platforms rather than on-premises infrastructure. These migrations involve different tooling and different challenges — particularly around converting Google-native file formats and migrating Google Sites content.

Email Migration Birmingham

Birmingham is the UK's second-largest city by population and a major centre for professional services, manufacturing, automotive, and public sector organisations. Email migration Birmingham projects reflect this diverse economic base.

Professional services concentration: Birmingham has a significant concentration of law firms, accountancy practices, and consultancy firms, many of which handle highly sensitive client data. Migrations for these organisations require enhanced security measures, detailed chain-of-custody documentation for data transfer, and post-migration security verification to confirm that client data confidentiality has been maintained throughout the process.

Public sector presence: Birmingham is home to numerous local government organisations, NHS trusts, and central government agencies. Public sector M365 migrations must comply with the Government Security Classifications Policy, Cyber Essentials Plus certification requirements, and specific procurement frameworks (G-Cloud, Digital Outcomes and Specialists). Cloudswitched has experience working with public sector organisations across the Midlands and understands the additional governance and security requirements these migrations entail.

Legacy infrastructure: Some of Birmingham's longer-established businesses still run Exchange 2010 or even Exchange 2007 environments, which require specific migration paths and additional planning compared to more modern source environments. These legacy migrations often need a hybrid coexistence period whilst users are migrated in batches, and the hybrid configuration requires careful DNS management and certificate planning.

The chart above shows M365 adoption rates across major UK business centres, reflecting the varying pace of cloud transformation across different regional economies. London leads due to the competitive pressure in financial services and technology, whilst other cities are following strong upward trends driven by remote working requirements and digital transformation initiatives accelerated by the pandemic.

Phase 7: Email Migration as Part of Full M365 Deployment

Whilst this guide focuses primarily on SharePoint, OneDrive, and file server migration, the email workload is an integral part of any full Microsoft 365 deployment. For organisations that have not yet migrated email — or that are migrating email simultaneously with other workloads — this section covers the key considerations specific to email migration within a broader M365 project.

Email Migration Approaches

Cutover migration: All mailboxes migrate at once, typically over a weekend. Suitable for organisations with fewer than 150 mailboxes. Simple and fast, but all-or-nothing — there is no gradual rollout. Best for smaller email migration Birmingham or email migration Manchester projects where the organisation can tolerate a defined downtime window.

Staged migration: Mailboxes migrate in batches over days or weeks. Users coexist between the on-premises and cloud environments during the migration period. Requires a hybrid Exchange configuration and careful management of mail routing. Suitable for organisations with 150–2,000 mailboxes.

Hybrid migration: A permanent or long-term coexistence between on-premises Exchange and Exchange Online, with full free/busy calendar sharing, unified Global Address List, and seamless mail routing. Mailboxes can be moved individually on a flexible schedule. This is the recommended approach for large organisations and those that need extended coexistence for compliance or operational reasons.

IMAP migration: For organisations migrating from non-Exchange email systems (e.g., Zimbra, Kerio Connect, hMailServer, or other IMAP-compatible platforms). IMAP migration moves email messages but does not migrate calendars, contacts, or rules. These items need to be exported/imported separately or recreated manually.

Coordinating Email and File Migration

When email migration runs alongside SharePoint and OneDrive migration, the sequencing matters. At Cloudswitched, our standard approach for full-scope M365 migrations is:

Phase A — Identity and licensing: Set up Azure AD Connect, provision licences, and configure the M365 tenant. This foundation supports all subsequent workloads.

Phase B — Email migration: Migrate email first, because it is the most time-sensitive workload (users notice email disruption immediately) and because a successful email migration builds confidence for subsequent phases.

Phase C — SharePoint and Teams: Migrate SharePoint content and configure Teams channels. This can run in parallel with the later stages of email migration for organisations where the workloads are handled by separate teams.

Phase D — OneDrive and file servers: Migrate personal files and departmental file shares. This is typically the longest phase and can run for weeks after email and SharePoint migration is complete.

Phase E — Optimisation and decommission: Fine-tune configurations, decommission legacy infrastructure, and conduct user adoption activities.

Phase 8: Security, Compliance, and Governance Configuration

A full Microsoft 365 migration is an opportunity to implement comprehensive security and governance controls that may not have been possible — or practical — with on-premises infrastructure. For UK businesses, this phase addresses both the technical security configuration of M365 and the regulatory compliance requirements specific to the British market.

Identity and Access Security

Multi-factor authentication (MFA): Every organisation migrating to Microsoft 365 should enable MFA for all users. At a minimum, use Microsoft Authenticator or FIDO2 security keys. SMS-based MFA should be avoided as a primary method due to SIM-swapping risks. For organisations with Azure AD Premium P1 or P2 licences (included in M365 Business Premium and E3/E5), Conditional Access policies can enforce MFA based on location, device compliance, and risk level.

Conditional Access: Configure Conditional Access policies that enforce your organisation's security requirements without creating unnecessary friction for users. Common policies include: require MFA for access from outside the UK, require managed devices for access to sensitive SharePoint sites, block legacy authentication protocols (IMAP, POP3, SMTP AUTH), and require compliant devices for mobile access.

Privileged Identity Management (PIM): For organisations with Azure AD Premium P2 (M365 E5 or standalone), PIM provides just-in-time elevation for administrative roles. This means that Global Administrators, SharePoint Administrators, and Exchange Administrators operate with standard user privileges and only elevate to their administrative role when needed, with time-limited access and audit logging.

Data Loss Prevention and Information Protection

Sensitivity labels: Microsoft Information Protection sensitivity labels can be applied to documents and emails to enforce encryption, watermarking, access restrictions, and visual markings. For UK organisations handling sensitive data, labels such as "Confidential — Internal Only," "Restricted — Client Data," and "Public" provide a structured classification framework that travels with the document regardless of where it is stored or shared.

Data Loss Prevention (DLP): DLP policies prevent sensitive information from being shared inappropriately. For UK businesses, pre-built DLP templates cover UK-specific sensitive information types including National Insurance numbers, NHS numbers, UK passport numbers, and UK driver's licence numbers. Custom DLP policies can be created for organisation-specific sensitive data patterns.

Retention and records management: Configure retention policies that align with your organisation's data retention requirements. UK businesses must consider retention requirements from multiple sources: Companies Act (accounting records — 6 years), HMRC (tax records — 6 years plus current year), FCA (transaction records — 5 years for MiFID firms), and contractual obligations. M365 retention policies can be applied at the organisation, site, library, or label level, providing granular control over data lifecycle management.

Phase 9: Testing, Validation, and User Acceptance

Testing is the phase that separates professional migrations from amateur ones. Every component of the migration must be validated before users are directed to the new environment, and the validation must be systematic, documented, and signed off by stakeholders.

SharePoint Validation Checklist

For each migrated SharePoint site, validate the following:

Data completeness: Compare document counts between source and destination. Account for any files that were intentionally excluded (blocked file types, oversized files, ROT data). Verify that folder structures are intact and that no folders were truncated due to path length limitations.

Metadata integrity: Spot-check documents across each library to confirm that custom columns, content types, and managed metadata values are correct. Pay particular attention to choice columns, date columns, and lookup columns, which are most prone to migration errors.

Permissions accuracy: For each site, verify that the correct users and groups have the correct permission levels. Test access with representative user accounts from each department — can they see what they should see? Can they edit what they should be able to edit? Are they blocked from content they should not access?

Version history: Verify that version history was preserved for a sample of documents across each library. Check that the version count matches expectations and that previous versions can be restored.

Search: Test SharePoint search to confirm that migrated content is indexed and searchable. Search indexing can take 24–48 hours after migration, so build this delay into your validation timeline.

OneDrive Validation Checklist

File completeness: Compare file counts and total size between source home drives and destination OneDrive libraries. Investigate any discrepancies — common causes include files excluded due to path length, invalid characters, or file type blocks.

Sync client functionality: Verify that the OneDrive sync client is installed, signed in, and syncing correctly on representative user machines. Test file creation, modification, and deletion to confirm that changes sync in both directions.

Known Folder Move: If KFM is enabled, verify that the Desktop, Documents, and Pictures folders are redirected to OneDrive and that the redirection is transparent to the user — files should appear in the same location in File Explorer, with the green check mark indicating sync status.

User Acceptance Testing (UAT)

Select a group of pilot users — typically 5–10% of the organisation, chosen to represent different departments, technical skill levels, and working patterns — and ask them to use the new M365 environment for their normal daily work for a defined period (typically one week). Gather structured feedback on:

Can they find their files? Can they open, edit, and save documents without issues? Do shared files and co-authoring work correctly? Is the SharePoint intranet functional and navigable? Are there any workflows or processes that are broken or degraded? Is the performance acceptable, particularly for users on slower internet connections?

Address all issues identified during UAT before proceeding to full rollout. Issues that seem minor during testing will be amplified when the entire organisation migrates.

Phase 10: Post-Migration Optimisation and Ongoing Management

Migration is not complete when the data arrives in the cloud. The post-migration phase is where organisations realise the full value of their Microsoft 365 investment — or fail to, if they treat migration as a one-time project rather than the beginning of an ongoing optimisation journey.

Adoption and Change Management

The most common reason that M365 migrations fail to deliver expected value is not technical failure — it is user adoption failure. Users who received minimal training and no ongoing support revert to old habits: saving files locally instead of in OneDrive, emailing documents instead of sharing SharePoint links, and using individual email folders instead of Teams channels for project communication.

Effective adoption programmes include: structured training sessions for each user cohort, video tutorials covering the most common tasks, a champions network of enthusiastic early adopters who provide peer support, regular communication about new M365 features and best practices, and measurable adoption targets tracked through M365 usage analytics.

Performance Monitoring

After migration, monitor the M365 environment to identify and resolve performance issues before they affect user satisfaction. Key metrics to track include:

OneDrive sync health: Monitor sync client error rates across the organisation. Common post-migration issues include files stuck in "sync pending" state, conflicts caused by files being edited simultaneously on different devices, and sync pauses caused by insufficient local storage.

SharePoint page load times: If migrated SharePoint sites load slowly, investigate common causes including oversized document libraries (more than 5,000 items in a single view), excessive custom web parts, and images that have not been optimised for web delivery.

Email delivery: Monitor mail flow to ensure that all DNS changes have propagated correctly and that email is routing through Exchange Online without delays or bounce-backs. Pay particular attention to email from external senders, as DNS propagation issues can cause intermittent delivery failures for days after MX record changes.

Governance and Ongoing Management

Establish governance policies that prevent the M365 environment from becoming as disorganised as the on-premises environment it replaced. Key governance areas include:

Site provisioning governance: Define who can create new SharePoint sites and Teams, what naming conventions must be followed, what templates must be used, and what retention policies are applied by default. Without governance, organisations typically experience "Teams sprawl" — dozens of underused Teams created for ad-hoc purposes, each consuming storage and creating confusion.

External sharing policies: Configure external sharing policies that balance collaboration needs with security requirements. Options range from completely blocking external sharing (appropriate for highly sensitive environments) to allowing sharing with specific partner domains (common for professional services firms) to permitting anonymous sharing links (rarely appropriate for UK businesses handling personal data).

Storage management: Monitor storage consumption across SharePoint and OneDrive. M365 provides 1 TB of SharePoint storage per organisation plus 10 GB per licenced user. For large organisations with extensive document libraries, storage can become a cost concern. Implement policies to manage storage including version limits, retention policies that delete aged content, and regular reviews of storage consumption by site.

Common Migration Pitfalls and How Cloudswitched Avoids Them

Having delivered hundreds of Microsoft 365 migrations across the United Kingdom, Cloudswitched has encountered every conceivable migration challenge. Here are the most common pitfalls and how our methodology prevents them.

Pitfall 1: Underestimating Data Volume

Organisations routinely underestimate the total volume of data that needs to migrate. They count the data on their primary file server but forget about departmental shares, user home drives, secondary file servers, NAS devices, and data stored in individual SharePoint site collections. Our discovery process scans every data source comprehensively, producing an accurate data inventory before migration planning begins.

Pitfall 2: Ignoring Permission Complexity

Permissions that "just work" in the on-premises environment can break spectacularly during migration if the permission mapping is not handled correctly. We conduct a full permissions audit during discovery, build a detailed mapping document during planning, and validate permissions after every migration wave. No data is signed off until permissions have been verified by the relevant department head.

Pitfall 3: Insufficient User Communication

Users who are surprised by the migration — who discover that their files are in a new location without warning — generate the majority of post-migration support tickets. Our change management programme begins weeks before the first data moves, with regular communications, training sessions, and opportunities for users to ask questions and raise concerns. By the time migration day arrives, users know what to expect and how to work in the new environment.

Pitfall 4: Skipping the Pilot

Organisations eager to complete the migration quickly sometimes skip the pilot phase and proceed directly to full migration. This is a false economy — problems discovered during a full migration are exponentially more disruptive and expensive to fix than problems discovered during a pilot. Our methodology always includes a pilot phase, and we do not proceed to full migration until the pilot results meet our quality criteria.

Pitfall 5: Neglecting Post-Migration Optimisation

Migration is a means to an end, not an end in itself. Organisations that treat migration as complete the moment the data arrives in the cloud miss the opportunity to improve workflows, implement modern collaboration practices, and realise the full value of their M365 investment. Cloudswitched includes a post-migration optimisation phase in every engagement, working with the organisation to configure, refine, and adopt the full range of M365 capabilities.

Migration Tooling Deep Dive: Choosing the Right Platform

The migration tool you select has a direct impact on migration quality, speed, and cost. For UK businesses evaluating options for SharePoint migration services UK and broader M365 migration, here is a detailed comparison of the major platforms based on our hands-on experience at Cloudswitched.

Feature Comparison

For most mid-sized UK organisations, ShareGate provides the best balance of capability and cost. For large enterprises with complex requirements, Quest/Metalogix offers the most comprehensive feature set. For small organisations with simple migrations, Microsoft's free tools may be sufficient — but we recommend engaging a specialist like Cloudswitched even for simple migrations, because the cost of getting it wrong far exceeds the cost of getting it right the first time.

Migration Throughput and Scheduling

Migration throughput — how much data can be transferred per hour — is constrained by several factors: source environment read speed, network bandwidth, Microsoft 365 throttling limits, and the migration tool's efficiency. For UK businesses, the practical throughput is typically:

SharePoint-to-SharePoint Online: 1–5 GB per hour per migration thread, depending on file sizes and metadata complexity. Small files with extensive metadata migrate more slowly than large files with minimal metadata.

File share to SharePoint/OneDrive: 2–10 GB per hour per migration thread. File shares with deep folder nesting and many small files migrate more slowly than flat structures with larger files.

Google Workspace to M365: 1–3 GB per hour, constrained primarily by Google's API rate limits and the overhead of file format conversion.

To maximise throughput whilst respecting Microsoft's throttling limits, migrations should be scheduled during off-peak hours (evenings and weekends for UK businesses), run with multiple parallel migration threads (typically 5–10 for a mid-sized organisation), and use incremental migration to spread the load over multiple passes rather than attempting to migrate everything in a single session.

Cost Analysis: Full M365 Migration for UK Businesses

Understanding the true cost of a full Microsoft 365 migration helps UK businesses budget accurately and evaluate the return on investment. Costs fall into four categories: licensing, migration services, infrastructure decommissioning, and ongoing management.

Migration Cost Breakdown

The infrastructure decommissioning savings are significant and often underestimated. Retiring on-premises file servers, SharePoint servers, backup infrastructure, UPS systems, and associated maintenance contracts typically saves £20,000–£40,000 per year for a 200-seat UK organisation. When combined with reduced IT staff time spent on infrastructure management, the total cost of ownership for M365 is typically 30–40% lower than the equivalent on-premises infrastructure over a five-year period.

Return on Investment Timeline

Most UK organisations achieve a positive ROI on their M365 migration within 18–24 months when all costs and savings are accounted for. The timeline is shorter for organisations with ageing infrastructure that requires imminent replacement (where the migration avoids a capital expenditure on new servers) and longer for organisations with recently refreshed infrastructure (where the on-premises depreciation has not yet been fully realised).

Beyond direct cost savings, the productivity gains from improved collaboration, anywhere access, and modern tools contribute to ROI that is difficult to quantify but consistently cited by our clients as the most valuable outcome of their M365 migration. A professional services firm in London estimated that the time saved by replacing email attachments with SharePoint co-authoring was worth £150 per user per year in recovered productive time — a figure that dwarfs the migration cost.

Hybrid Scenarios and Coexistence

Not every organisation can or should migrate entirely to the cloud in a single project. Hybrid scenarios — where some workloads remain on-premises whilst others move to Microsoft 365 — are common in the UK, particularly among larger organisations, those in regulated sectors, and those with specific technical requirements that M365 does not yet address.

SharePoint Hybrid

SharePoint hybrid allows organisations to maintain on-premises SharePoint farms whilst integrating them with SharePoint Online. This is useful for organisations that have custom solutions running on SharePoint on-premises that cannot yet be replicated in SharePoint Online, or that have data residency requirements for specific content that prevent cloud storage.

Key hybrid features include: hybrid search (showing results from both on-premises and online in a unified search experience), hybrid taxonomy (sharing managed metadata term sets between on-premises and online), and hybrid OneDrive (redirecting users' "My Site" links to OneDrive for Business instead of on-premises personal sites).

Exchange Hybrid

Exchange hybrid is the most common hybrid scenario and is essentially mandatory for organisations migrating from on-premises Exchange to Exchange Online in a staged manner. The hybrid configuration provides free/busy calendar sharing between on-premises and cloud mailboxes, unified address book, and the ability to move mailboxes between on-premises and cloud in either direction.

Azure AD Hybrid Identity

Most UK organisations migrating to M365 maintain their on-premises Active Directory and synchronise it with Azure AD using Azure AD Connect (now Entra Connect). This hybrid identity model allows users to authenticate with the same credentials for both on-premises and cloud resources, and it provides a seamless experience during the transition period when some workloads are still on-premises.

For organisations planning a phased migration, hybrid identity is the foundation that supports all other hybrid workloads. It must be configured and tested thoroughly before any workload migration begins, because errors in identity synchronisation affect every M365 service.

Industry-Specific Migration Considerations for UK Businesses

Different industries have different requirements for their Microsoft 365 migration, driven by regulatory obligations, data sensitivity, and operational characteristics. Here are the industry-specific considerations that Cloudswitched addresses for our UK clients.

Financial Services

FCA-regulated firms must ensure that their M365 configuration meets requirements for data retention (MiFID II — 5 years for transaction records, 7 years for some categories), communication surveillance (monitoring of electronic communications for market abuse), and operational resilience (PS21/3 — identifying important business services and setting impact tolerances). M365 features including eDiscovery, communication compliance, and audit logging address these requirements, but they must be properly configured and documented.

Legal

Law firms migrating to M365 must address client confidentiality (ethical walls between matter teams), legal hold (preservation of documents and communications relevant to ongoing litigation), and the specific requirements of the SRA Standards and Regulations around data security. SharePoint information barriers and M365 eDiscovery legal hold features are essential tools for legal sector migrations.

Healthcare (NHS and Private)

Healthcare organisations handling patient data must comply with the NHS Digital Data Security and Protection Toolkit (DSPT), and their M365 configuration must meet the requirements for processing special category data under UK GDPR. This includes encryption, access controls, audit logging, and the ability to respond to patient subject access requests (SARs) across all M365 workloads.

Education

UK educational institutions can access M365 Education licences (A1, A3, A5) at significantly reduced costs. Migration considerations include safeguarding requirements (content monitoring, restricted external sharing), GDPR requirements for processing children's data (ICO Children's Code), and the need to support both staff and student users with different access levels and governance requirements.

Public Sector

UK public sector organisations must comply with the Government Security Classifications Policy (OFFICIAL, SECRET, TOP SECRET) and meet Cyber Essentials Plus certification requirements. M365 Government Community Cloud (GCC) configurations may be required for organisations handling sensitive government data. Procurement must follow G-Cloud or Digital Outcomes and Specialists frameworks.

Frequently Asked Questions About Microsoft 365 Migration in the UK

Based on the questions we receive most frequently from UK organisations considering a full M365 migration, here are detailed answers to the most common concerns.

How long does a full Microsoft 365 migration take?

For a typical 200-seat UK organisation migrating email, SharePoint, OneDrive, and file servers, the complete migration project takes 10–16 weeks from kickoff to decommission. The timeline varies based on data volume, complexity of permissions and customisations, and the organisation's tolerance for parallel workload migration. Smaller organisations (under 50 users) with straightforward environments can complete in 4–6 weeks. Large enterprises (500+ users) with complex SharePoint farms and multiple file servers typically need 16–24 weeks.

Will users experience downtime during migration?

With proper planning, user-facing downtime can be eliminated or reduced to a few minutes for the final DNS cutover. Email migration using the hybrid approach involves no downtime — mailboxes are moved in the background and users continue working throughout. SharePoint and OneDrive migration runs in parallel with continued access to source systems, and users are redirected to the new environment only after migration and validation are complete. The only moment of potential disruption is the DNS cutover for email (MX record change), which typically takes a few minutes and can be scheduled for a low-impact period.

What happens to our existing SharePoint customisations?

Customisations fall into three categories. First, customisations that migrate directly: content types, site columns, managed metadata, list views, and most content. Second, customisations that need to be rebuilt: SharePoint Designer workflows (replaced by Power Automate), InfoPath forms (replaced by Power Apps), custom master pages (replaced by modern site designs), and sandbox solutions. Third, customisations that cannot be replicated: server-side code solutions that depend on the SharePoint server-side object model. These must be re-architected as SPFx solutions or alternative approaches. Cloudswitched assesses all customisations during discovery and provides a detailed remediation plan with effort estimates for each item.

Is our data safe during migration?

Data security during migration is addressed at multiple levels. Data in transit is encrypted using TLS 1.2+. Data at rest in Microsoft 365 is encrypted using BitLocker and per-file encryption. Migration tools authenticate using modern authentication (OAuth 2.0) with service accounts that have the minimum necessary permissions. At Cloudswitched, we operate under ISO 27001-aligned information security practices, and our migration engineers are vetted and trained in data handling procedures appropriate for sensitive UK business data.

Can we migrate from Google Workspace to Microsoft 365?

Yes. Google Workspace to Microsoft 365 migration is a common project for UK businesses. The migration covers Gmail to Exchange Online, Google Drive to OneDrive and SharePoint, Google Sites to SharePoint Online, and Google-native file formats (Docs, Sheets, Slides) to their Microsoft equivalents (Word, Excel, PowerPoint). The main challenges are format conversion fidelity (particularly for complex spreadsheets) and retraining users who are accustomed to Google's interface. Cloudswitched has extensive experience with Google-to-Microsoft migrations and can provide accurate scoping and realistic timelines.

What about ongoing support after migration?

Migration is the beginning, not the end. Cloudswitched offers ongoing managed services for Microsoft 365 that include: monitoring and alerting, security policy management, user onboarding and offboarding, licence management, backup (M365 does not provide comprehensive backup by default), and regular reviews to ensure the environment remains optimised and compliant. Our managed service clients benefit from proactive management that prevents issues before they affect users, rather than reactive break-fix support that addresses problems after they have already caused disruption.

Why UK Businesses Choose Cloudswitched for Microsoft 365 Migration

Choosing the right migration partner is one of the most important decisions in your M365 journey. The wrong partner can turn a straightforward migration into months of disruption, data loss, and user frustration. The right partner makes the process smooth, predictable, and — ultimately — transformative for your organisation.

Cloudswitched is a London-based managed service provider that specialises in Microsoft 365 migration and management for UK businesses. Here is what sets us apart:

UK-focused expertise: Every member of our migration team understands the regulatory, compliance, and business environment specific to the United Kingdom. We do not apply generic migration playbooks — we build migration plans that account for UK GDPR, FCA regulations, SRA requirements, NHS DSPT, and the specific operational characteristics of British businesses. Whether you need a Microsoft 365 migration London project for a Canary Wharf financial firm, an email migration Manchester engagement for a Northern manufacturing group, or an email migration Birmingham rollout for a Midlands professional services practice, we have the local knowledge and technical depth to deliver.

Full-scope capability: We do not just migrate email and walk away. Our team handles the complete M365 migration scope — Exchange Online, SharePoint Online, OneDrive for Business, Teams, file server decommissioning, identity management, security configuration, and ongoing managed services. A single partner for the entire project eliminates the finger-pointing that occurs when multiple vendors are involved and one workload affects another.

Proven methodology: Our ten-phase migration methodology has been refined over hundreds of UK migration projects. Every phase has defined inputs, activities, outputs, and quality gates. We do not proceed to the next phase until the current phase meets our quality criteria. This disciplined approach is why our migrations consistently complete on time, on budget, and without data loss.

Post-migration commitment: We measure our success not by the number of files migrated, but by the business outcomes our clients achieve after migration. Our ongoing managed services ensure that your M365 environment continues to be optimised, secured, and aligned with your evolving business needs for years after the migration is complete.

Getting Started: Your Next Steps

If your organisation is considering a full Microsoft 365 migration — whether you are starting from scratch, expanding an existing M365 deployment to include SharePoint and OneDrive, or migrating from another cloud platform — the first step is a conversation with a specialist who understands your specific requirements.

Cloudswitched offers a complimentary migration assessment for UK businesses. During this assessment, we will review your current environment, identify the workloads and data volumes that need to migrate, provide a high-level timeline and cost estimate, and discuss the compliance and security considerations specific to your industry and region. There is no obligation, and the assessment provides valuable insight regardless of whether you choose to work with us.

A full Microsoft 365 migration — covering SharePoint, OneDrive, email, file servers, and the full M365 suite — is a significant undertaking, but it is also one of the most impactful technology investments a UK business can make. The organisations that approach it with proper planning, specialist expertise, and a focus on user adoption realise benefits that extend far beyond cost savings: improved collaboration, stronger security, regulatory compliance, and a modern digital workplace that attracts and retains talent.

Whether you are in London, Manchester, Birmingham, or anywhere else in the United Kingdom, Cloudswitched is ready to guide you through every phase of your migration journey. Contact us today to begin your complimentary assessment and take the first step towards a modern, cloud-powered workplace.