Do we have to migrate at the end of it?

No. The assessment reports what your environment actually depends on and what the realistic path is. If the honest finding is that you should stay hybrid for now, that is what the report says.

What do you need to run the assessment?

Read-only access to the directory and the tenant, agreed at scoping, and time with whoever knows the environment's history. The dependencies that stall migrations are usually the undocumented ones, so the conversation matters as much as the tooling.

Do you do the migration itself?

No. The report is written to be handed to whoever does, your MSP or your own team, with the phases and risks named. Not performing the migration is what keeps the assessment honest, because I have no project to sell on the back of it.

AD to Entra Migration Readiness

Every business still running on-premises Active Directory eventually hears the same sentence: it is time to move everything to the cloud. Sometimes it comes from an MSP, sometimes from a Microsoft renewal, sometimes from the age of the server in the cupboard. The sentence is usually right. The plan behind it usually does not exist.

The gap between those two things is where migrations go wrong, because the question that matters is not whether to move. It is what, in your environment, still quietly depends on the thing you are about to switch off.

A readiness assessment answers that before anyone commits to anything. I inventory what actually depends on your on-premises directory: applications using legacy authentication, NTLM and Kerberos dependencies, LDAP binds from devices and software, service accounts nobody has documented, and the Group Policy estate mapped against what Intune can and cannot replace.

What you get

A written report stating what can move now, what can move with work, what cannot move yet and why, and the realistic phased path between here and there, with the risks named. It is written to be handed to whoever does the migration, your MSP or your own team. I do not perform the migration, which is precisely why the assessment is honest: I have no project to sell on the back of it.

What it costs

Fixed price, $2,450 plus GST. Set against the cost of a migration that stalls halfway because an unmapped dependency surfaced in week three, it is the cheapest part of the whole exercise.

What it is not

Not the migration itself, not a cloud sales pitch, and not a Microsoft-funded assessment with a predetermined answer. If the honest finding is that you should stay hybrid for two more years, that is what the report will say. If the questions it raises about identity are broader than the migration, that is the posture review.

The work offered through robswain.au is one-off and self-contained by design. There is no retainer and no ongoing commitment: the engagement ends when the work is done, and you keep control of your own systems throughout.

How to start

Tell me roughly how many users you have and what is driving the move, and I will confirm scope. rob@robswain.au

Common questions

Do we have to migrate at the end of it?: No. The assessment reports what your environment actually depends on and what the realistic path is. If the honest finding is that you should stay hybrid for now, that is what the report says.
What do you need to run the assessment?: Read-only access to the directory and the tenant, agreed at scoping, and time with whoever knows the environment's history. The dependencies that stall migrations are usually the undocumented ones, so the conversation matters as much as the tooling.
Do you do the migration itself?: No. The report is written to be handed to whoever does, your MSP or your own team, with the phases and risks named. Not performing the migration is what keeps the assessment honest, because I have no project to sell on the back of it.

Let's talk.

If you want to work together, book a call below. If you would rather write first, email me and I will get back to you.

Book a call rob@robswain.au