Short answer
Migrate yourselves if the move is small, simple and your team has done it before: one source, few users, no identity or domain changes. Hire a partner when you face a tenant-to-tenant move, a domain cutover, hybrid Exchange, large file shares, device re-enrollment or a hard deadline. Many organizations split the work, with the partner owning the technical runbook.
Key facts
- The risk is concentrated in identity, mail flow and cutover, not in copying data.
- A first-time migration team learns on production users.
- Internal IT time is not free; day-to-day support still has to happen.
- A split model often costs less than full outsourcing and carries less risk than full DIY.
- Whoever does it, insist on a written runbook and rollback plan.
When doing it yourself is reasonable
Small, single-source migrations are often fine in house. Examples include moving 20 to 50 mailboxes from a hosted email provider to a new Microsoft 365 tenant, or moving a single file share into a SharePoint library with simple permissions.
Microsoft provides free tooling for many of these cases: the SharePoint Migration Tool and Migration Manager for files, the Exchange admin center migration batches for mail, and documentation for Google Workspace migration. If your team has time, has done a similar move, and the business can tolerate some disruption, DIY is a valid choice.
When to hire a partner
Bring in specialists when mistakes are expensive or hard to reverse.
- Tenant-to-tenant moves after a merger, acquisition or divestiture
- Moving a domain between tenants, which requires removing it from one before adding it to another
- Exchange hybrid, Entra Connect changes or UPN changes
- Terabytes of files with complex or broken permissions
- Re-enrolling Intune or Autopilot devices into a new tenant
- Regulated data, legal hold or retention requirements
- A fixed deadline such as a contract end or a deal close
Comparing the options
There are three realistic models. Pick by risk and internal capacity, not by headline cost.
| Model | Best for | Main risk |
|---|---|---|
| Full DIY | Small, simple, single-source moves | Learning on production; IT overload |
| Split model | Teams with capable IT but no migration experience | Unclear ownership if roles are not written down |
| Full partner delivery | Complex, deadline-driven or multi-workload moves | Choosing a partner without matching experience |
The hidden costs of DIY
Internal teams rarely have spare capacity. While staff run the migration, tickets, projects and security work wait. The learning curve also shows up as extra cutover attempts, longer outages, or missed items such as shared mailbox permissions, calendar delegates, mail-enabled apps and Outlook profile issues.
The other cost is recovery. Fixing a broken mail flow or a misconfigured domain after cutover takes longer than doing it right the first time.
How a split model works
In a split model, the partner leads discovery, design, the migration runbook, tooling, DNS and identity changes, and cutover. Internal IT handles user communication, desk-side support, device checks and app owners. Write down who does what in a simple responsibility matrix before work starts.
This keeps knowledge in house, because your staff take part in every step, while the riskiest technical steps are handled by people who have done them many times.
A quick self-assessment
Before deciding, answer a few questions honestly. Has anyone on the team run this exact migration type in the last two years? Can the team spend most of its time on the project for several weeks without support suffering? Is there a rollback plan if cutover goes wrong? Does the business have a hard deadline?
If the answers are mostly yes, no deadline pressure exists and the scope is small, DIY is reasonable. If several answers are no, get specialist help for at least design and cutover. Even a short engagement to review your plan and runbook can catch the mail flow, identity and permission gaps that cause most outages.
How Accred Consulting approaches it
Accred Consulting starts with Discovery to map your environment and the migration steps that carry the most risk. The Proposal sets clear scope, a fixed price and a timeline with responsibilities written down. Delivery runs with structured check-ins, and Handover includes documentation and knowledge transfer so your staff can run the environment afterward. Clients work directly with US-based specialists, with no offshore handoffs, and optional Support retainers are available.
Track record: 400+ client projects, 2,000+ migration workstreams and 150,000+ users migrated by a US-based team. Company facts · Case studies
Related questions
Want this scoped for your environment?
Book a free consultation. After discovery you get a written plan with scope, a fixed price and a timeline.
Book a free consultation