From Legacy Hosting to Microsoft 365 Over a Single Weekend

← Back to Insights

The Problem

Our sister company, Tricon Solutions, had been running email on InMotion Hosting's cPanel IMAP for years. It worked — until it didn't. The team had grown to span the US and India, with personal mailboxes for every team member and a substantial number of shared functional accounts handling everything from HR to contracts to client communications. The India team was using Thunderbird. There were no shared calendars, no unified contacts, and no integration with Microsoft Teams, which the company was already using for meetings and collaboration.

The breaking point was operational: the team needed shared mailboxes that actually worked across time zones, calendar integration that synced with Teams, and an email infrastructure that could support a growing staffing operation without duct tape.

We needed to execute with minimal disruption. The team handles time-sensitive staffing operations — active candidate pipelines, vendor compliance documentation, contracts, and weekly timesheet processing. Extended email downtime was not an option.

Scope and Planning

We started by building a complete account inventory. Every mailbox on InMotion was cataloged: who owned it, how large it was, what it was used for, and whether it needed to migrate, convert to a shared mailbox, or be retired entirely.

The final migration plan covered three categories:

• All personal mailboxes — full IMAP migration to M365 Exchange Online, preserving all historical email across tens of gigabytes
• All shared and functional mailboxes (HR, contracts, legal, recruiting, operations, and more) — created fresh in M365 as shared mailboxes with historical email archived to Google Drive
• Retired accounts — former employees, duplicates, and system accounts identified and documented for clean decommissioning

Licensing was optimized by tier: each user received only the license level their role required, and all shared mailboxes ran on M365's free shared mailbox allocation — saving over 40% compared to licensing everyone identically.

Our Approach: AI as IT Consultant

Rather than engaging a traditional managed service provider or Microsoft partner, we worked directly with Claude through Cowork mode — Anthropic's desktop interface that gives Claude the ability to interact with your browser, file system, and local tools in real time. Claude operated across four distinct roles throughout the project:

1. Technical Architect

Claude designed the migration strategy around an IMAP-based approach using Exchange Online's native migration tools rather than third-party solutions. It recommended planning the migration in sequential batches to manage risk and validate incrementally — starting with a single admin test account, progressing through shared mailbox groups, and culminating in all personal accounts.

2. Implementation Partner

Through Cowork mode's browser automation, we used Claude to directly execute changes across multiple admin portals simultaneously — Exchange Admin Center for migration batches and CSV configurations, cPanel Zone Editor for DNS records, Microsoft Defender for DKIM signing, and M365 Admin Center for license provisioning.

3. Real-Time Problem Solver

The migration hit several real-world complications that Claude diagnosed and resolved in real time: a CNAME/A record conflict that blocked Autodiscover configuration, a missing Exchange Online license that caused a batch failure, a UserDuplicateInOtherBatchException when re-adding a failed user, and "Investigate" data consistency warnings on several batches that turned out to be minor oversized items — not errors requiring re-migration.

4. Communications Coordinator

Claude drafted employee announcements tailored to our specific context: users already signed into Teams (so SSO would simplify Outlook access), the India team transitioning from Thunderbird, and the need to preserve access to old webmail for historical email verification. Three emails were timed for pre-migration, cutover day, and post-migration follow-up.

Execution

The migration ran in five phases, with planning and preparation done during the week and the actual cutover executed over a single weekend:

Migration Architecture

What Claude Produced

Every document in this migration was generated through Claude — not copied from a template library or adapted from a generic playbook. Each artifact was specific to this environment, with real server addresses, real account names, and real permission assignments.

The speed matters. A project like this, scoped and documented traditionally, would involve a week of planning before any execution begins. With Claude, the planning and documentation were produced in a single working session, leaving the rest of the week for execution and validation.

Design Decisions

Phased Batches, Not Big Bang

We migrated personal accounts first in parallel, validated them, then cut DNS. Shared mailboxes were created fresh in M365 rather than migrated — their historical email was archived to Google Drive as a reference, but the new shared inboxes started clean. This simplified permissions and avoided migrating years of accumulated noise.

License Optimization

Not every user needs the same license tier. Advisory team members who only needed email were placed on lower-cost plans, while shared functional mailboxes ran on M365's free allocation. Right-sizing licenses by role saved over 40% compared to assigning everyone the same plan.

India Team Transition

The India team had been using Thunderbird for years. Rather than installing Outlook desktop clients, we moved them to Outlook Web — a browser-based experience that requires no software installation, includes the full Outlook feature set, and integrates directly with Teams calendars they were already using. The employee communications included India-specific instructions for this transition.

Clean Account Retirement

Seven accounts were identified for retirement during the inventory phase: former employees who had left, duplicate accounts, and system accounts that served no current purpose. Documenting these explicitly — rather than quietly skipping them — created an audit trail and reduced the attack surface of the legacy hosting environment.

Results

The migration completed in under a week with zero downtime and zero lost emails. DNS propagation finished within 4 hours of the MX cutover. Every employee received structured communications at three touchpoints — pre-migration, cutover day, and post-migration follow-up — so the transition felt planned rather than abrupt.

The team now operates on a unified platform: email, calendar, shared inboxes, and Teams collaboration all running on Microsoft 365. The India team replaced a fragmented Thunderbird setup with Outlook Web, gaining shared calendar visibility and integrated shared mailboxes for the first time.

The result: an enterprise-grade email platform with unified calendars, shared inboxes, and full security hardening — at a fraction of what a managed service provider would have charged just for the migration itself.

The Takeaway

Email migrations are not glamorous work. But they are the kind of infrastructure project that can stall for months because the planning overhead doesn't justify pulling an engineer off client work. The Claude-driven approach changes that calculus. When the planning, documentation, and change management materials can be produced in a single session, the barrier to execution drops dramatically.

This is the Tricon Infotech methodology applied to real operations: identify the problem, use Claude to accelerate the planning and documentation, execute with precision, and move on. No six-month timeline. No RFP process. Just a well-planned migration from start to finish.