A specialist firm for work usually handed to generalists.
Sunrise Digital Labs is an IT consultancy. What we are deepest in is complex Microsoft 365 migration, tenant consolidation, and the technology integration that follows an acquisition. This page covers how the firm is put together and who is accountable once work starts.
What we do, and who we do it for
The specialization is complex Microsoft 365 migration and tenant consolidation, and the integration work that follows an acquisition. That is what the firm is built around, and what people call us for.
It is not the whole of what we do. Identity, security, cloud and the on-premises estate are part of every one of these projects. Once we know an environment, they are also work we are hired for on their own terms. The specialization is narrow on purpose; the firm is not.
Who this is for: organizations with an internal IT team that is competent and fully occupied, usually with more than one office, business unit or acquired company, and more Microsoft 365 environments than anyone set out to have. What decides it is the shape of the estate rather than the headcount. In practice that has run from a couple of dozen people to fifteen hundred. A move like this comes round every several years, which is not often enough for an internal team to accumulate the pattern.
There is no industry we concentrate on. What our clients have in common is structural rather than sectoral.
The depth behind it
More than 3,500 accounts migrated, led or delivered by the founder. It is a personal delivery figure rather than a client count. It accumulated over fifteen years in infrastructure and systems architecture, a stretch of it inside a Canadian MSP where migrations arrive continuously rather than once.
What repetition produces is a sequence rather than an opinion. The same phases run on every engagement, in an order set by dependencies rather than preference, and the whole of it is published, including what tends to break at each stage and the promises we decline to make. You can read it before you speak to anyone here. It sits with the case studies and method pieces published so far.
Much of that sequence is automated, and it changes what you receive rather than only how fast it arrives. Discovery is generated from the tenant rather than compiled by hand, including tenants that started outside Microsoft entirely, GoDaddy-hosted mail and domains among them. Waves are executed and checked by script, against failure patterns built up across engagements rather than found after the fact. The documents you end up with are produced from the same data, rather than written up afterwards from somebody's notes. Some of the tooling is Microsoft's and CISA's — open source, free, and named on the pages where it does the work. A name you can go and check is worth more than an adjective. Some of it we wrote ourselves, and the honest claim about that is what it does rather than what it is called.
Who is accountable, and how engagements are staffed
Every engagement has one named technical lead, and the word doing the work in that sentence is accountable rather than involved. Execution is delegated. Other people run waves, write scripts, configure endpoints. The material decisions, the sequencing and the escalation path are not. If that person ever changes, it is a deliberate handover rather than something you notice in an email signature.
That lead is assigned to the engagement and stays with it, and they are a specialist in the work it actually involves rather than a generalist reading up on it. Someone who has taken environments like yours apart before, holds the source and target architecture in their head, and is reachable when a wave surfaces something the plan did not anticipate.
The capabilities Sunrise is known for are owned inside the firm. Microsoft 365 architecture, tenant migration and consolidation, identity, endpoint management and the automation that runs them are delivered by the people you are introduced to at the start. If an engagement calls for a capability outside that, you are told what it is before it begins.
Three things you can check before you sign
Each of these is a question worth asking us, and worth asking anyone else you are considering.
“What will you understand, and what will we have, before the first production wave?”
Nothing gets a cutover date until discovery is finished. If an environment is not ready to move, we say so — and that is an outcome of the assessment rather than a failure of one.
“If discovery finds MFA gaps or admin rights nobody can justify, what happens?”
They are surfaced, and you decide who closes them — us, your team, or someone else. Data that arrives intact in a tenant carrying the same gaps has not improved anything.
“What is in our hands at the end, and who else could use it?”
Inventories, configuration records, runbooks, cutover procedures, validation results. The artifacts exist at handoff or they do not, which makes this the easiest of the three to check. They are written to be used by whoever operates the environment afterwards.
Why the firm is built this way
Narrow, because narrow is what gets referred.
Most of our work arrives through somebody who has watched this go wrong once. A person refers the tenant consolidation people. Nobody refers the complex technology people. The specialization is what makes us a specific call rather than one of forty — which is also how we work with partners.
Deliberately not everything.
A consultancy listing fourteen service lines invites a fair question about how it could be good at all of them. The answer a buyer usually reaches is that it is not. We would rather be checkable on a few things than plausible on many.
The other capabilities are not a second business.
Consolidating tenants means solving identity. Solving identity surfaces security. A cutover touches endpoints, DNS and every application that authenticates against the tenant. That work is the surface area of the specialization rather than a wider menu — which is also why it is reasonable follow-on work once we know an environment.
Talk to us about the estate.
The useful first conversation is about the environment rather than about us. What is in it, what is forcing the timing, and whether the plan somebody has handed you holds up.