DEV Community: Medha Cloud

Microsoft 365 Tenant-to-Tenant Migration: The Complete 2026 Playbook

Medha Cloud — Mon, 16 Mar 2026 16:48:39 +0000

Tenant-to-tenant migrations happen during mergers, acquisitions, divestitures, and rebranding. They're among the most complex M365 operations. Here's what you need to know.

When T2T Migration Happens

Mergers & Acquisitions: Consolidating two companies into one tenant
Divestitures: Splitting a division into its own tenant
Rebranding: Moving to a new primary domain
Regulatory: Separating data for compliance (EU data residency, etc.)

What Needs to Move

Data Type	Complexity	Tool Options
Email & Calendar	Medium	Native (Cross-tenant) or BitTitan
OneDrive	Medium	ShareGate, BitTitan, Mover
SharePoint Sites	High	ShareGate, Quest
Teams	Very High	Manual + third-party
Azure AD Users	Medium	Azure AD Connect + PowerShell
Conditional Access Policies	Manual	Export/Import via Graph API
Intune Policies	Manual	Export/Import
DLP Policies	Manual	PowerShell export/import

Step-by-Step Process

Phase 1: Discovery (Week 1-2)

# Count mailboxes and sizes
Get-Mailbox -ResultSize Unlimited |
  Select DisplayName, PrimarySmtpAddress,
  @{N='SizeGB';E={(Get-MailboxStatistics $_.Identity).TotalItemSize.Value.ToGB()}} |
  Export-CSV mailbox-inventory.csv

# Count OneDrive usage
Get-SPOSite -IncludePersonalSite $true -Limit All |
  Where-Object { $_.Url -like '*-my.sharepoint.com/personal/*' } |
  Select Owner, StorageUsageCurrent |
  Export-CSV onedrive-inventory.csv

Phase 2: Preparation (Week 2-4)

Create target tenant and configure domains
Set up Azure AD in target tenant
Purchase licenses — use M365 license comparison to pick the right plans
Configure cross-tenant trust (if using native migration)
Set up migration tool (BitTitan, ShareGate, or native)

Phase 3: Migration (Week 4-8)

Email Migration Order

Shared mailboxes first (low risk, good test)
Conference rooms and resources
VIP/executive mailboxes (during low-traffic hours)
Regular users in batches of 50-100

DNS Cutover Sequence

Day 0: Lower TTL to 300 seconds
Day 2: Switch MX records to target tenant
Day 2: Update SPF, DKIM, DMARC
Day 2: Update Autodiscover CNAME
Day 3: Verify all mail flow
Day 30: Raise TTL back to normal

Phase 4: Validation (Week 8-10)

Test email send/receive (internal and external)
Verify calendar data and recurring meetings
Check OneDrive file access and sharing
Validate Teams channels and chat history
Confirm mobile devices reconnected
Run compliance checks

Cost Estimates

Org Size	DIY Cost	With Migration Partner
50 users	$500-1,000 (tools)	$2,000-5,000
200 users	$2,000-5,000 (tools)	$8,000-15,000
1000 users	$10,000-20,000 (tools + time)	$25,000-50,000
5000+ users	$50,000+ (tools + dedicated team)	Custom quote

The "DIY cost" doesn't include internal labor, which is typically 2-5x the tool cost.

Biggest Risks

1. Teams Data Loss

Teams migration is the hardest part. Chat history, files, and channel configurations don't migrate cleanly with most tools. Plan for some data loss or extended parallel operation.

2. Shared Mailbox Permissions

Delegated permissions (Send As, Send on Behalf, Full Access) must be manually recreated in the target tenant.

3. Conditional Access Policies

These don't migrate. Document everything in the source tenant and recreate in the target.

4. Third-Party App Integrations

Every app using OAuth tokens from the source tenant needs to be reconfigured. This includes:

CRM systems (Salesforce, HubSpot)
Ticketing systems (Zendesk, ServiceNow)
HR platforms
Custom line-of-business apps

When to Get Help

Tenant-to-tenant migrations are not a good DIY project for most organizations. The complexity, risk of data loss, and business disruption make professional help worth the investment.

Medha Cloud's tenant-to-tenant migration service handles the entire process with zero-downtime guarantees and dedicated project management. They've completed complex T2T migrations for organizations up to 50,000 users.

For a broader view of all migration options, see their M365 migration services overview.

Planning a tenant-to-tenant migration? Get a free migration assessment from Medha Cloud's certified Microsoft engineers.

Google Workspace to Microsoft 365: Migration Checklist for IT Admins

Medha Cloud — Mon, 16 Mar 2026 16:48:08 +0000

Switching from Google Workspace to Microsoft 365 is a common move for organizations that need deeper desktop app integration, advanced compliance tools, or better hybrid identity management. This checklist covers every step.

Why Organizations Switch

Feature	Google Workspace	Microsoft 365
Desktop apps	Web-first	Full desktop suite
Email storage	30 GB (basic)	50-100 GB
Compliance	Basic	Advanced (DLP, eDiscovery, retention)
Identity	Google Identity	Azure AD + Entra ID
Security	Good	Enterprise-grade (Defender, Sentinel)
Hybrid support	Limited	Full (Azure AD Connect, ADFS)

Pre-Migration Checklist

Week 1-2: Discovery & Planning

[ ] Count total users, shared drives, and data volume
[ ] Audit Google Groups → map to M365 Distribution Lists / Security Groups
[ ] Identify Google Sites → plan SharePoint migration
[ ] List Google Forms → plan Microsoft Forms replacement
[ ] Check Google Vault data → plan eDiscovery migration
[ ] Map Google Drive shared permissions → OneDrive/SharePoint permissions
[ ] Identify third-party apps using Google OAuth → plan re-authentication

Week 2-3: Tenant Setup

[ ] Purchase M365 licenses (compare plans)
[ ] Create M365 tenant at admin.microsoft.com
[ ] Add and verify domain(s)
[ ] Set up Azure AD Connect (if on-prem AD exists)
[ ] Create user accounts (manual or CSV bulk import)
[ ] Configure security defaults (MFA, conditional access)

Week 3-4: Data Migration

Email Migration

Use Microsoft's built-in Google Workspace migration tool:

Admin Center → Settings → Migration → Gmail
1. Enter Google admin credentials
2. Generate migration key
3. Select users (batch or all)
4. Choose data: Email, Calendar, Contacts
5. Start migration (runs in background)

Estimated speeds:

1 GB per user per hour (average)
100 users × 5 GB average = ~500 hours of migration time
Run multiple batches in parallel to speed up

Drive Migration

Options for Google Drive → OneDrive/SharePoint:

Tool	Cost	Speed	Best For
SharePoint Migration Tool	Free	Moderate	Bulk migration
Mover (Microsoft)	Free	Fast	Large drives
BitTitan	$15/user	Fast	Complex permissions
ShareGate	$$$	Fast	SharePoint-heavy orgs

Week 4-5: DNS Cutover

# Old Google records to remove:
MX: ASPMX.L.GOOGLE.COM (priority 1)
MX: ALT1.ASPMX.L.GOOGLE.COM (priority 5)
MX: ALT2.ASPMX.L.GOOGLE.COM (priority 5)

# New Microsoft 365 records:
MX: company-com.mail.protection.outlook.com (priority 0)
TXT: v=spf1 include:spf.protection.outlook.com -all
CNAME: autodiscover → autodiscover.outlook.com

Critical: Lower TTL to 300 seconds 48 hours before the switch.

Week 5-6: User Training & Cleanup

[ ] Deploy Outlook desktop clients
[ ] Configure mobile devices (Outlook mobile)
[ ] Train users on Teams, OneDrive, SharePoint
[ ] Verify all data migrated correctly
[ ] Keep Google Workspace active for 30 days (safety net)
[ ] Cancel Google Workspace subscription after soak period

Common Gotchas

1. Google Drive Links Break

External links shared from Google Drive will stop working. Plan to:

Re-share critical documents from OneDrive/SharePoint
Set up redirects for widely-shared links

2. Google Calendar Integration

Third-party apps connected via Google Calendar API need to be reconfigured for Microsoft Graph API.

3. Google Groups vs M365 Groups

Google Groups and M365 Groups have different permission models. Plan the mapping carefully.

Cost Comparison

For a 100-user organization:

Platform	Plan	Cost/mo	Annual
Google Workspace Business Starter	$7/user	$700	$8,400
Google Workspace Business Standard	$14/user	$1,400	$16,800
M365 Business Basic	$6/user	$600	$7,200
M365 Business Standard	$12.50/user	$1,250	$15,000

Microsoft 365 is often cheaper AND includes desktop Office apps.

When to Hire Migration Experts

Consider professional help if:

You have 500+ users
You have complex shared drive permissions
You need compliance-grade migration (audit trail)
You can't afford extended downtime
You have Google Vault data that must be preserved

Medha Cloud's Google to M365 migration service handles the entire process — from discovery to post-migration support. Their M365 migration services cover every source platform.

Conclusion

The Google to Microsoft 365 migration is straightforward with proper planning. Give yourself 4-6 weeks, follow this checklist, and you'll have a smooth transition.

Planning a Google Workspace to M365 migration? Medha Cloud provides zero-downtime migration services for organizations of all sizes. Get a free assessment.

Exchange Server End of Life 2025: Your Migration Options Explained

Medha Cloud — Mon, 16 Mar 2026 16:48:03 +0000

Exchange Server 2016 reaches extended end of support on October 14, 2025. Exchange Server 2019 follows on October 14, 2025 as well. If you're still running on-premises Exchange, now is the time to plan your migration.

Why You Must Migrate

Running unsupported Exchange Server means:

No security patches — every new vulnerability is a permanent zero-day
No compliance — HIPAA, SOC 2, PCI-DSS all require supported software
No vendor support — Microsoft won't help when things break
Insurance risk — cyber insurance policies increasingly exclude unsupported software

Your Migration Options

Option 1: Cutover Migration to Microsoft 365

Best for organizations with fewer than 150 mailboxes.

Step	Action	Duration
1	Set up M365 tenant & licenses	1 day
2	Create migration endpoint	1 hour
3	Start migration batch	24-72 hours
4	Switch MX records	30 minutes
5	Decommission Exchange	After 30-day soak

Pros: Simple, one-shot migration
Cons: Brief email disruption during DNS switch

Option 2: Hybrid Migration

Best for organizations with 150+ mailboxes or complex requirements.

On-Premises Exchange ←→ Exchange Online
       ↕                      ↕
  Active Directory  ←→  Azure AD Connect

Mail flow continues normally throughout the migration. Users are moved in batches over weeks or months.

Pros: Zero perceived downtime, move at your own pace
Cons: Requires hybrid configuration expertise

Option 3: Staged Migration

A middle ground — migrate groups of users over time without full hybrid complexity.

Option 4: IMAP Migration

For non-Exchange mail servers (Zimbra, Postfix, etc.) migrating to M365.

Pre-Migration Checklist

Before starting any migration:

[ ] Inventory all mailboxes and sizes
[ ] Document distribution groups and shared mailboxes
[ ] Map public folder structure
[ ] Check third-party integrations (CRM, ticketing, etc.)
[ ] Plan DNS changes (MX, SPF, DKIM, DMARC, Autodiscover)
[ ] Communicate timeline to end users
[ ] Purchase correct M365 licenses
[ ] Set up Azure AD Connect (if using hybrid)

Choosing the Right M365 License

Plan	Mailbox Size	Key Features	Price/user/mo
Exchange Online Plan 1	50 GB	Email only	$4
M365 Business Basic	50 GB	Email + Teams + OneDrive	$6
M365 Business Standard	50 GB	+ Desktop Office apps	$12.50
M365 E3	100 GB	Enterprise security + compliance	$36
M365 E5	100 GB	Advanced security + analytics	$57

Not sure which plan fits? Use an M365 license comparison tool to evaluate features side by side.

Common Migration Mistakes

1. Not Testing Mail Flow First

Always create test mailboxes and verify:

Internal send/receive works
External send/receive works
Calendar invites sync
Mobile devices connect

2. Forgetting Public Folders

Public folders require a separate migration process. Plan for this.

3. Ignoring DNS TTL

Lower your DNS TTL to 300 seconds (5 minutes) at least 48 hours before migration. This ensures the MX record change propagates quickly.

4. Skipping User Training

Users will notice differences between Outlook connecting to Exchange vs Exchange Online. Prepare training materials.

Post-Migration Tasks

Verify all mailboxes are accessible
Confirm calendar data migrated correctly
Test mobile device connectivity
Update firewall rules (you can now close Exchange ports)
Decommission old Exchange servers (after 30-day parallel run)
Document the new environment

Timeline Estimates

Org Size	Migration Type	Estimated Duration
1-50 users	Cutover	1-3 days
50-150 users	Cutover/Staged	1-2 weeks
150-500 users	Hybrid	2-4 weeks
500-2000 users	Hybrid	1-2 months
2000+ users	Hybrid (batched)	2-6 months

When to Get Expert Help

DIY migration works for small, simple environments. Consider professional migration services when:

You have 200+ mailboxes
You need zero-downtime migration
You have compliance requirements (HIPAA, SOC 2)
You're running Exchange 2010/2013 (older versions have more gotchas)
You have complex mail routing or third-party integrations

Medha Cloud's M365 migration service has completed 1,200+ migrations. Their team handles the heavy lifting — planning, execution, DNS cutover, and post-migration support.

For Exchange-specific migrations, their Exchange to M365 migration guide covers every method in detail.

Conclusion

Exchange Server EOL is not optional — it's a hard deadline. The good news: Microsoft 365 is a better platform with better security, better uptime (99.9% SLA), and better collaboration features. Start planning now.

Need help with your Exchange migration? Medha Cloud specializes in zero-downtime Exchange to M365 migrations for enterprises.

Microsoft 365 Migration: Complete Step-by-Step Guide for 2025

Medha Cloud — Sat, 13 Dec 2025 17:07:20 +0000

Migrating to Microsoft 365 can transform how your organization works. This guide covers everything from planning to post-migration optimization.

Pre-Migration Planning

1. Inventory Your Current Environment

Before migrating, document:

Number of mailboxes
Total data size
Custom domains
Third-party integrations
Compliance requirements (HIPAA, SOC2, etc.)

2. Choose Your Migration Method

Method	Best For	Complexity	Downtime
Cutover	<150 mailboxes	Low	1-2 days
Staged	150-2000 mailboxes	Medium	Weeks
Hybrid	2000+ mailboxes	High	Minimal
IMAP	Non-Exchange servers	Low	Days
Third-party	Complex scenarios	Varies	Minimal

3. Prepare Your Domain

# DNS records needed
MX:    example-com.mail.protection.outlook.com
TXT:   v=spf1 include:spf.protection.outlook.com -all
CNAME: autodiscover -> autodiscover.outlook.com

Migration Steps

Step 1: Set Up Microsoft 365 Tenant

Purchase licenses at admin.microsoft.com
Add and verify your domain
Create user accounts (or sync from AD)

Step 2: Configure Connectors (Hybrid)

For hybrid migrations, set up send and receive connectors between on-premises Exchange and Microsoft 365.

Step 3: Migrate Mailboxes

# PowerShell for batch migration
New-MigrationBatch -Name "Batch1" -SourceEndpoint $Endpoint \
  -CSVData ([System.IO.File]::ReadAllBytes("users.csv")) \
  -TargetDeliveryDomain "company.mail.onmicrosoft.com"

Start-MigrationBatch -Identity "Batch1"

Step 4: Update DNS

Switch MX records to Microsoft 365 when ready:

MX 0 company-com.mail.protection.outlook.com

Step 5: Post-Migration Tasks

Reconfigure mobile devices
Update Outlook profiles
Test email flow
Archive old servers
Train users on new features

Common Migration Scenarios

Google Workspace to Microsoft 365

Use the built-in Google Workspace migration tool:

Admin Center → Data migration → Gmail
Authorize access with admin credentials
Select users and data types
Start migration (runs in background)

Full guide: Google Workspace to M365 Migration

Exchange Server to Microsoft 365

For on-premises Exchange 2016/2019:

Set up hybrid configuration wizard
Move mailboxes in batches
Decommission on-premises servers

Full guide: Exchange to M365 Migration

Tenant-to-Tenant Migration

For M&A or rebranding scenarios:

Cross-tenant migration (preview feature)
Third-party tools (BitTitan, Quest)
Manual export/import (small orgs)

Full guide: Tenant-to-Tenant Migration

Cost Estimation

Use migration calculators to estimate:

Duration based on data size
License costs
Consulting fees

Try our Migration Calculator

Tips for Success

Communicate early: Inform users 2 weeks before migration
Migrate in waves: Don't do everyone at once
Keep old system running: 30-day parallel operation
Test thoroughly: Create test accounts first
Document everything: For future audits

Conclusion

A well-planned migration minimizes disruption and sets your organization up for success with Microsoft 365's collaborative features.

Need expert migration help? Medha Cloud has completed 1,200+ successful Microsoft 365 migrations. Get a free assessment today.

How to Choose the Right VPS Hosting in 2025: A Complete Guide

Medha Cloud — Sat, 13 Dec 2025 17:07:16 +0000

Virtual Private Server (VPS) hosting has become the go-to choice for developers and businesses who need more control than shared hosting but don't want the complexity of dedicated servers.

What is VPS Hosting?

A VPS is a virtual machine that provides dedicated resources (CPU, RAM, storage) within a shared physical server. Unlike shared hosting, your resources are guaranteed and isolated from other users.

Key Factors to Consider

1. Virtualization Technology

KVM (Kernel-based Virtual Machine) provides the best isolation and performance. Each VPS runs its own kernel, allowing you to install any operating system.

OpenVZ offers lighter resource usage but less isolation. You're limited to Linux distributions.

Recommendation: Choose KVM-based VPS for production workloads.

2. Storage Type

Storage	Speed	Reliability	Best For
HDD	Slow	Good	Archival
SSD	Fast	Great	General use
NVMe	Very Fast	Great	Databases, high I/O

NVMe SSDs can deliver 500,000+ IOPS - essential for database-heavy applications.

3. Location

Choose data centers close to your users:

India: Mumbai, Bangalore
USA: Dallas, Los Angeles, New York
Europe: Amsterdam, Frankfurt, London

4. Support Quality

24/7 support with actual engineers (not just script readers) is crucial. Look for:

Live chat response under 5 minutes
Phone support availability
Managed options for hands-off operation

VPS Use Cases

Web Applications: WordPress, Node.js, Django
Development/Staging: CI/CD pipelines, testing environments
Game Servers: Minecraft, Counter-Strike
VPN/Proxy: Self-hosted VPN services
SaaS Backends: API servers, microservices

Cost Comparison 2025

Provider	Basic Plan	vCPU	RAM	Storage
AWS Lightsail	$5/mo	1	1GB	40GB SSD
DigitalOcean	$6/mo	1	1GB	25GB SSD
Linode	$5/mo	1	1GB	25GB SSD
Medha Cloud	$9.99/mo	2	4GB	80GB NVMe

The key difference? Medha Cloud includes 24/7 managed support and doesn't charge egress fees.

Getting Started

Assess your needs: CPU, RAM, storage, bandwidth
Choose your OS: Ubuntu 22.04 LTS is most popular
Deploy: Most providers offer 1-click or 3-minute deployment
Secure: Set up firewall, SSH keys, fail2ban
Monitor: Set up alerts for resource usage

Conclusion

For most developers, a KVM-based VPS with NVMe storage and good support is the sweet spot. Start small and scale as needed.

Looking for managed VPS hosting? Medha Cloud offers VPS from $9.99/mo with 99.99% uptime SLA and 24/7 expert support.