Professional Services · Migration
On migration day, nobody should notice
Microsoft 365 tenant migration, data center moves, Hyper-V and VMware transitions, on-premises to cloud: with a pilot, wave plan and rollback plan, a method that cuts downtime to minutes.
Method
Replication based
Typical downtime
< 1 hour
Rollback plan
Every wave
A badly planned migration is the new system’s first bad impression
Sentinel migration projects start with discovery and a dependency map; systems are split into waves and each wave is validated with a pilot. Data is moved in advance by replication; on cutover night only the delta and DNS change happen. A rollback plan is ready for every wave.
Dependency map
Which application depends on which server and service; nobody says “we forgot that server”.
Zero-downtime method
Replication with Veeam, Azure Migrate and vendor tools; only the final delta on cutover night.
Rollback guarantee
A tested rollback for every wave; if something goes wrong you return to the old system.
Migration types
Migration projects we run frequently
Microsoft 365 tenant
Mail, OneDrive, SharePoint and Teams migration and merging
Exchange to M365
Hybrid or cutover migration, MX plan
Data center move
Physical relocation or move to Sentinel Cloud
Hyper-V ↔ VMware
Virtualization platform change
On-premises to cloud
Moving workloads to Sentinel Cloud or Azure
Storage migration
SAN/NAS replacement, data migration
Active Directory
Forest/domain consolidation and upgrades
File server
Migration to Sentinel Drive or SharePoint
Process
From discovery to post-migration care
Migration flow
Discovery and plan
Dependencies, waves, rollback
Approval
Wave plan
Replication and pilot
Data moved in advance
Acceptance
Pilot validation
Cutover and hypercare
Final delta, DNS, 30 days of support
The cutover-night runbook is written minute by minute; every step has a rollback point.
Veeam · Azure Migrate · Vendor tools
Packages
By migration type
Tenant and mail
M365 Migration
Moving mail and collaboration data
Per user
Project based
- Identity and MX plan
- Staged or cutover migration
- User communication
- 30 days of hypercare
- Most popular
Servers and platform
Infrastructure Migration
Virtualization, data center or cloud transition
Per server
Project based
- Dependency map
- Replication-based migration
- Wave and rollback plan
- Project manager
Turnkey
Full Relocation
Data center, identity and applications together
By scope
Project based
- Plan for all layers
- Weekend cutover operation
- DR site setup
- Post-migration optimization
Frequently asked questions
The most common questions about migration
In the replication-based method only the final delta and redirection happen on cutover night; under an hour for most systems. The duration is written per system in the wave plan.
It is kept in parallel for at least 30 days after cutover; it is shut down with your approval at the end of hypercare.
The vendor support policy is reviewed and, if necessary, the plan is made together with the vendor. In unsupported scenarios the risk is reported in writing.
In M365 migrations usually nothing; if a profile update is required, a step-by-step guide and service desk are provided.
It depends on vendor license terms; transferability and SPLA/CSP alternatives for Windows Server, SQL and Citrix licenses are evaluated during planning.
Related services
Together with migration
Sentinel IaaS
VPS and VDS, private cloud, virtual data center, GPU servers, virtual firewall and load balancer. Hourly or monthly.
ExploreMicrosoft 365 / Azure Management
Tenant management, licensing and security configuration.
ExploreSentinel DRaaS
Replication between Istanbul, Ankara and Frankfurt; RPO and RTO packages; two DR drills a year.
Explore
Free IT Health Check
See your infrastructure through a sentinel’s eyes.
Current state assessment, risk inventory and a prioritized roadmap. No commitment.