Free tool
Hybrid to Full Cloud
Rebuild, pre-provision, or buy a tool — above what price?
With Microsoft's own tooling, a hybrid-joined machine does not become Entra-joined by flipping a switch: there is no in-place conversion, and Autopilot Reset keeps the join type. A rebuild is therefore the starting point, not an option — which makes the third-party tool question legitimate rather than indulgent. This tool works out your person-days, compares them against a tool's cost, and computes the price above which that tool no longer pays for itself.
No sign-up, no cookie: what you enter stays in your browser and is gone when you close the tab — none of it leaves. Only the visit itself is counted, by a cookieless audience measurement that does not identify you, described in the legal notice.
Your estate and your constraints
Nothing is pre-filled: a day rate or a visit duration that arrives already written is read as a measured figure. Yours are the only ones that count here.
The estate
The team
The ground
The third-party tool
The scenario, and the threshold
The arithmetic above is worth exactly what your two estimates are worth: the visit duration, and the person-days that would remain with the tool. The first is measured on a pilot of twenty to thirty machines covering several user profiles; the second can only be measured on a test batch supplied by the vendor. An in-place profile migration tool has to be validated on your real environment — BitLocker, line-of-business applications, GPOs still in force, VPN — before it enters a plan.
A decision aid, not a purchase recommendation. LB IT Cloud resells no migration tool and earns nothing from this choice. The amounts are the ones you enter; no vendor price is provided here, because a list price is not a quotation and ages badly.
The strategy
Four scenarios, and a cost / benefit frame
Three native scenarios, and a fourth that buys time. The fourth is not judged on its promises but against a threshold, and the threshold is computed from the first.
Why a rebuild is natively necessary
With Microsoft's own tooling, a hybrid-joined machine does not become Entra-joined by flipping a switch: there is no in-place conversion. The local profile is tied to the domain identity, so the user starts on a fresh profile. And Autopilot Reset is not enough — it keeps the join type: a reset hybrid machine comes back hybrid.
What does work: Autopilot registration does not depend on the join type. A hybrid machine managed by Intune can be converted, and "Convert all targeted devices to Autopilot" does it with no script and no application secret. That makes a rebuild unavoidable in scenarios A, B and C — and it is precisely what makes the third-party tool question legitimate.
The four scenarios
| Scenario | Principle | User time | What rules it out |
|---|---|---|---|
| A — At the desk, end to end | Wipe and full reinstall in front of the user | 2 to 4 h | Volume: one technician, one machine at a time |
| B — Pre-provisioned exchange | The bench does the whole device phase beforehand | 15 to 30 min | No bench, or no logistics flow |
| C — Remote wave | With no technician on site | Not controlled | Wi-Fi with no certificate, or the technician-present rule |
| D — Third-party tool | In-place conversion, no wipe, profile preserved | A restart, in theory | The price, and the absence of a test on your environment |
Where scenario B's visit compresses
The visit is not one block. It breaks down, and each part compresses differently — which is the only reason a measured visit can come down without changing scenario.
| Step | Compressible? |
|---|---|
| Sign-in + the user phase of the ESP | Yes — through the ESP's contents: fewer blocking applications, more device targeting |
| Checks: drives, printers, Wi-Fi, BitLocker, mail | Yes — scriptable into a single pass-or-fail control |
| Handover, questions, small fixes | Little — this is the project's human time |
| Travel, waiting, interruptions | Yes — through organisation: a campaign per site |
The cost / benefit frame, for any third-party tool
On one side, the internal cost with no tool: the number of person-days needed, times a technician's average loaded daily cost. On the other, the cost with the tool: the licence or subscription, plus the person-days that remain — pilot, exceptions, support, machines too old.
The tool is worthwhile if the second is clearly lower than the first — "clearly", because the gap also has to cover the schedule and quality risk that raw arithmetic does not capture. And there is a figure almost nobody works out: the price above which the tool stops repaying what it saves. That is the one to hold a quotation up against, and it is the one the tool above gives you.
What is left to do before deciding
- Run the internal scenario's pilot — 20 to 30 machines, four user profiles — it is the baseline of every threshold calculation.
- Ask for a real quotation in parallel — one or two vendors, on the exact scope, with a test on ten to twenty machines.
- Compare the two on the same batch — the only way to decide on measured rather than estimated figures.
- Do not decide on the tool before the pilot's figure — it is what sets the denominator — person-days saved — of the whole calculation.