Veloxant Practical Guide: Microsoft 365 Migration Insights

A hands-on approach to planning and executing small-business migrations with minimal disruption.

Most Microsoft 365 migrations fail because of poor planning, not technical issues. After managing 20+ successful migrations, here's the roadmap that actually works for small businesses.

Migration reality: Plan for the weekend migration window to extend into Monday morning. Even "simple" migrations run into DNS propagation delays or unexpected mailbox sizes.

Pre-Migration Checklist

Thorough planning prevents most migration disasters. Spend 2 weeks on planning to save 2 weeks of cleanup.

2 weeks before migration:
  • ✓ Inventory all mailboxes, shared mailboxes, and distribution lists
  • ✓ Document current email forwarding rules and aliases
  • ✓ Verify domain ownership and prepare DNS access
  • ✓ Plan MFA rollout and conditional access policies
  • Inventory mailboxes, shared mail, aliases. Export a complete list from your current system—include mailbox sizes, forwarding rules, and any automation that touches email.
  • Decide auth (MFA, CA policies) before cutover. Configure multi-factor authentication and conditional access policies in advance, but don't enforce them until after migration is complete.
  • Verify domains, DNS, and DKIM/SPF/DMARC plan. Ensure you can modify DNS records and plan the exact sequence for updating MX records, SPF, and DKIM settings.
  • Size mailboxes accurately. Large mailboxes (>10GB) need special handling and longer migration windows—identify these early.

Common Planning Oversights

  • Forgotten shared mailboxes that break after migration
  • Distribution lists used by external partners
  • Email rules and signatures that need recreation
  • Mobile device access during transition period

Cutover Plan

Execute migrations during low-traffic periods with clear communication and rollback plans.

  • Choose weekend or evening windows. Friday evening to Sunday evening gives maximum recovery time if issues arise.
  • Pilot first; communicate timelines clearly. Migrate 2-3 test users first, verify everything works, then proceed with full migration.
  • Stage PST ingestion; validate folders/permissions. Import PST files in batches, verify folder structures and shared calendar permissions after each batch.
  • DNS cutover sequence matters. Update MX records last, after user mailboxes are fully synchronized.
Migration weekend timeline:
  • Friday 6 PM: Start user mailbox sync
  • Saturday 10 AM: Complete initial sync, start incremental sync
  • Saturday 4 PM: Update DNS records (MX, SPF, DKIM)
  • Sunday 10 AM: User testing and validation
  • Monday 8 AM: Go-live with user communication

Migration Tools That Work

Based on real-world experience with different migration paths:

  • From Exchange on-premises: Microsoft's native migration tools handle most scenarios well
  • From Google Workspace: Microsoft's migration wizard works for basic setups
  • From other email providers: Third-party tools like BitTitan or manual PST import

Post-Migration Hardening

The real work starts after email is flowing. Focus on security and user adoption in the first 30 days.

  • Enable baseline CA, MFA, and alerting. Turn on the security features you planned during pre-migration, monitor for login issues.
  • Set retention labels and DLP if needed. Configure data loss prevention for sensitive information, set up retention policies for compliance.
  • Train users on OneDrive/SharePoint basics. Schedule group training sessions for file sharing and collaboration features.
  • Monitor and optimize performance. Track mailbox performance, identify users having trouble, and address mobile device setup issues.
Week 1 priorities: Focus on email working reliably before introducing advanced features. Users need confidence in basic email before they'll adopt OneDrive or Teams.

Security Configuration Essentials

Conditional Access Policies

  • Block legacy authentication protocols
  • Require MFA for all cloud apps
  • Block access from unknown locations (with user-friendly exceptions)

Data Protection

  • Enable audit logging for all mailboxes
  • Configure alert policies for suspicious activity
  • Set up data loss prevention for credit cards, SSNs

Troubleshooting Common Issues

DNS and Mail Flow Problems

  • Intermittent email delivery: Usually DNS propagation delays—wait 24-48 hours before panic
  • External emails bouncing: Check SPF records include Microsoft's IP ranges
  • Mobile devices not connecting: Often autodiscover DNS record issues

User Access Issues

  • Can't access email on phone: Recreate the email account rather than troubleshooting settings
  • Outlook desktop app problems: Create new Outlook profile instead of fixing corrupted profile
  • Missing shared mailboxes: Add permissions explicitly in Exchange admin center

Performance and Sync Issues

  • Slow mailbox performance: Often due to oversized mailboxes—archive old emails
  • Calendar sync problems: Remove and re-add calendar connections
  • OneDrive not syncing: Reset OneDrive client rather than troubleshooting sync conflicts

Success Metrics

Track these metrics to measure migration success:

  • Technical success: 95%+ of mailboxes migrated without data loss
  • User satisfaction: <5% of users reporting ongoing email issues after week 2
  • Security improvement: 100% of users using MFA within 30 days
  • Adoption metrics: 80%+ of users accessing OneDrive within 60 days

Need help with next steps?

Get a short, focused consult to map your migration path. No pressure, just practical advice based on 20+ successful Microsoft 365 migrations.

Schedule a Consultation
Founder

About Veloxant

Veloxant Solutions is founder-led and hands-on. You'll work directly with the person doing the work, backed by trusted tools and proven processes from managing 20+ successful Microsoft 365 migrations for small businesses.

Learn more →