← daniellepel.com
Capability Profile
Capability Profile
Migration Strategy
Moving organizations to new platforms without breaking what works
Migration strategy covers the planning, sequencing, and execution of platform transitions, from email and productivity workloads to device management and business applications, with a focus on delivering the right solution for the organization's actual situation rather than the technically ideal one.
Overview
My Experience
Key Work
Related
What It Is
Migration strategy is the discipline of moving workloads, users, and data from one platform to another without disrupting the organization in the process. The technical work varies by migration type, but the strategic work is consistent: understand what is being replaced and why, identify the dependencies that will break if the migration is done wrong, define a sequencing plan that manages risk, and validate that the destination actually meets the need before decommissioning the source. Migrations fail most often not because of technical complexity but because the planning skipped one of those steps.
Why It Matters
The best migrations are the ones users do not notice. That requires thorough pre-migration discovery, a phased approach that limits the blast radius of any individual failure, and a clear rollback plan that is tested rather than assumed. It also requires honesty about what a migration is actually solving. Moving an organization from one platform to another does not fix governance problems, security gaps, or process issues that existed before the migration. Those need to be addressed as part of the project, not deferred to after go-live.
Migration Types
  • Email platform migrations - Exchange on-premises to Exchange Online, Google Workspace to Microsoft 365, including mailbox data, calendar, contacts, and DNS cutover
  • Third-party tool replacement - Replacing paid security and compliance tools with M365 E5 native capabilities, eliminating redundant licensing cost
  • Device management modernization - Autopilot and Intune deployment replacing legacy imaging and Group Policy, with co-management as the transition state
  • Business application migration - Right-sizing legacy on-premises tools to appropriate cloud or M365 alternatives based on actual organizational need
  • Authentication modernization - ADFS to cloud-managed authentication, including PHS vs PTA evaluation and Seamless SSO configuration
In Practice

At Latham Pool Products, the most visible migration was replacing Mimecast with native M365 E5 security capabilities, eliminating the vendor cost entirely. At NBT, Exchange on-premises to Exchange Online and Google Workspace to M365 migrations were regular engagements across the client portfolio. A completed internal Google Workspace to M365 migration for 100 users, and a hosted Exchange to M365 migration for a 40-user customer, are the most concrete examples.

At NBT, migrations were a regular part of the work across a portfolio of around 25 Microsoft tenants. The most common types were Exchange on-premises to Exchange Online, and Google Workspace to Microsoft 365. Both require careful pre-migration planning and a phased cutover approach, but they are fundamentally different problems. Google to M365 migrations involve data format differences, user retraining, and a broader platform shift. Exchange on-premises migrations involve coexistence planning and a more surgical mailbox-by-mailbox execution.
At Latham Pool Products, the most significant migration was replacing Mimecast with Microsoft 365 E5 native security and compliance capabilities. Mimecast was costing approximately $20,000 per year for around 100 users. The M365 E5 licensing the organization already held included Defender for Office 365, Purview Information Protection, and compliance tooling that covered everything Mimecast was doing. The migration required configuring the native capabilities correctly before decommissioning Mimecast, validating that mail flow, filtering, and archiving were all functioning at parity, and then cutting over. The result was the same protection with no additional cost on top of existing licensing.
Not every migration needs to be a full platform transition. At NBT, one client was running a business-critical Access database from a local NAS and running into recurring permissions failures as Microsoft progressively tightened security defaults for Office file access. The technically correct answer was not a full cloud migration the organization could not afford. I migrated the data to SharePoint Lists, which gave them the same multi-user data entry capability, resolved the permissions issue permanently, and kept a 3-person non-profit from spending money they did not have on infrastructure they did not need.
Device management modernization at NBT involved deploying Windows Autopilot and Intune across client environments that were previously using legacy imaging and Group Policy. The measurable outcome at one client was a 50% reduction in onboarding time. The less visible outcome was a device estate that was consistently managed and policy-compliant without requiring physical access to machines for provisioning.
  • Exchange on-premises to Exchange Online migrations (NBT) Migrated multiple client organizations from Exchange on-premises to Exchange Online, including mailbox data migration, calendar and contact migration, hybrid coexistence planning, and DNS cutover coordination.
  • Google Workspace to Microsoft 365 migrations (NBT) Migrated organizations from Google Workspace to the full Microsoft 365 platform, covering email, calendar, contacts, document migration, and user transition planning. Addressed the platform shift aspects beyond pure data migration.
  • Mimecast replacement with M365 E5 native capabilities (Latham Pool Products) Replaced Mimecast email security and archiving with Microsoft 365 E5 native capabilities across approximately 100 users. Validated feature parity across mail filtering, archiving, and compliance functions before decommissioning Mimecast, eliminating approximately $20,000 in annual licensing cost from existing E5 entitlements.
  • Access database to SharePoint Lists migration (NBT) Migrated a 3-person non-profit's business-critical Access database from a local NAS to SharePoint Lists, resolving recurring permissions failures caused by Microsoft security tightening for Office file access. Delivered a right-sized solution that met the organization's needs without a full cloud migration they could not justify financially.
  • Autopilot and Intune deployment (NBT) Deployed Windows Autopilot and Intune across client environments replacing legacy imaging and Group Policy, reducing device onboarding time by 50% at one client and producing a consistently managed, policy-compliant device estate without physical provisioning requirements.
  • ADFS to cloud authentication migrations (NBT) Migrated client environments from ADFS to cloud-managed authentication using Password Hash Sync with Seamless SSO, eliminating ADFS infrastructure overhead while maintaining a seamless sign-in experience for end users.
← Hybrid Cloud Infrastructure Microsoft Purview Data Governance →