Bring us in on your client's migration.
Sunrise is the specialist inside engagements other firms own. We do complex Microsoft 365 migration and consolidation work, and we do not use a specialist engagement as a route around the partner who brought us in. Here is who you would be handing a client to.
When partners bring us in
A migration you would rather not staff
Tenant consolidations absorb senior people for weeks and go wrong in ways that are expensive to unwind. The load also concentrates around the cutover rather than spreading evenly across the project. Bringing in a specialist for the project is usually cheaper than clearing the bench for it.
Someone who has seen it go wrong before
Most of what goes wrong in a tenant move is predictable. The connector nobody documented. The attribute a dynamic group depends on. The domain that cannot be released on the promised day. That list comes from repetition, and it is worth most before a cutover.
A migration that starts somewhere unusual
Hosted Exchange, IMAP, a Microsoft 365 tenant GoDaddy provisioned years ago, or an on-premises Exchange that has outgrown the design it was built for. The destination is the same for all of them; the path in is not, and each source has its own set of things that do not map cleanly.
A plan you need to stand behind
You are being asked whether a migration plan is realistic before anyone commits to a date. We do the discovery so the answer is evidenced rather than estimated.
An attempt that stalled
Someone started and stopped. A half-migrated estate is its own problem: two sets of identities, mail flowing in both directions, and no clean point to resume from.
A deal that already set the deadline
Transaction terms commonly require consolidation inside 6–12 months. Assessing before close means the integration is scoped rather than discovered.
Who brings us in
Regional MSPs and IT providers — for the project they would rather not staff.
Fractional CIOs and technology advisers — to deliver a plan they can stand behind, with the discovery to support it.
Microsoft partners specialized elsewhere — Dynamics, Azure, security. Tenant work is a different discipline.
M&A advisers, corporate development and PE operating partners — engaged before close, so the integration is scoped rather than discovered.
Transaction services and IT due-diligence teams — they find the estate problem; we cost it and fix it.
Other consultancies — where the client is mid-program on something else and the Microsoft estate is in the way.
Recruiters and staffing firms — when the role a client is trying to fill is really a project with an end date.
What you can hand over
- Tenant consolidation
- Two or more Microsoft 365 tenants becoming one. Identity, mail flow, domains, SharePoint, OneDrive and Teams.
- M&A technology integration
- The whole estate after a transaction, not just the mailboxes.
- Divestiture and tenant separation
- Pulling users, data and systems out of a shared tenant, usually against a TSA exit date.
- Google Workspace → Microsoft 365
- Usually triggered by a licensing renewal, or by a standardization decision after an acquisition.
- Another source → Microsoft 365
- Exchange and hybrid, hosted Exchange, IMAP, GoDaddy-provisioned tenants, and file servers into SharePoint and OneDrive.
- Migration Readiness Assessment
- Where the answer needed is what this will actually take, before anyone commits to a date.
Two ways to work together
Which one fits is a conversation rather than a policy, and it usually follows from whether you want to hold the contract.
You subcontract us
You hold the contract and the client relationship. We are your delivery team for the migration, working to your timeline and reporting to you.
Your client may never need to meet us.
You introduce us
We contract directly with the client for the migration; you stay the adviser and stay in the loop.
What an introduction is worth to you is agreed up front, case by case.
How a joint engagement runs
One named technical lead
The same person from discovery through handoff, accountable to you and reachable directly. Not a team your client meets after signing.
Status comes through you
If you hold the relationship, we do not build a parallel reporting line to your client.
Your change process, not ours
Your maintenance windows, your approvals, your client’s calendar.
Anything outside the migration comes to you
On complex estates something always surfaces. You decide what happens with it.
What we need from you
The estate as you understand it
Even where that is incomplete. Discovery is faster when it starts from what you already know.
Access, or a path to it
Most delays on these engagements are waiting for credentials, not doing the work.
The relationship map
Who the client listens to, who approves a cutover window, and who will be unhappy if their mailbox moves on a Tuesday.
Where you want us to stay out
Say it up front and it is simply how the engagement runs.
What your client is left with
Documentation their team can operate: the estate as discovered, the decisions taken and why, the sequence run, and the state of the environment at handoff.
You get the same set your client does. A partner who has to come back to us to answer a question about the environment was handed a result rather than a handover.
See how a consolidation actually runs
Seven phases, what the client receives at each, what tends to break, and what we will not do. Built from the artifacts themselves rather than from a case you have to take on trust.
If your client later needs something outside what you deliver, that is a conversation with you — not around you. Licensing and retainers work the same way: neither goes into an account you hold unless you agree to it.
Start a partner conversation.
Have a client situation now? Tell us what you would like us to take on, and where you would rather we stayed out. Referring regularly? Say so, and attribution is agreed directly between us. A partner portal that issues your own link and QR code is planned and not running yet — until it is, nothing depends on it.