Display My device page screenshoot for Macs that are not in ABM during migration

[noahtalerman]

Fleet version: Observed in dogfood (commit 6e9d462)

Web browser and operating system: macOS 26.2

---

💥  Actual behavior

This Mac in dogfood sees the end user experience for ABM Macs:

🛠️ To fix

• @noahtalerman: For Macs that aren't in ABM (not DEP capable) I think we want to show the end user the window with this screenshot:

• Clicking "Start" should open the My device page in the default browser.

🧑‍💻  Steps to reproduce

1. Enroll a device into another MDM solution
2. Install Fleet desktop and orbit enroll the device into Fleet
3. Wait for Migrate to Fleet shows up in Fleet desktop
4. Remove the MDM profile from the other vendor
5. Click migrate to fleet (without refetching the device)
6. See images related to ABM devices.

[noahtalerman]

🛠️ To fix

• @noahtalerman: For Macs that aren't in ABM (not DEP capable) I think we want to show the end user the window with this screenshot:

• Clicking "Start" should open the My device page in the default browser.

@marko-lisica please correct me if I'm wrong.

[github-actions]

This issue has been automatically tagged as unreleased. If this is is incorrect, you may replace the label with ~released-bug. If this is correct, or might be correct, move this bug onto the appropriate product board to get a fix underway.

[marko-lisica]

@JordanMontgomery, I'm not sure if this is an unreleased bug. Do you think this was broken in 4.81?

[JordanMontgomery]

@marko-lisica I do not think this was broken in 4.81. I will follow up with @noahtalerman here https://fleetdm.slack.com/archives/C03C41L5YEL/p1770214165011249 but my honest suspicion is that in certain scenarios timing can cause fleet to think the wrong migration type is in-progress and show the ADE dialog when a manual migration is happening due to the fact that the manual migration state only gets detected if the profile is still manually installed and I bet it's possible to remove the profile then trigger the migration and see this in some scenarios.

[marko-lisica]

@JordanMontgomery, maybe we can timebox this one to investigate?

[JordanMontgomery]

Timeboxing this as a 3 - We will have to investigate and try to find a repro as we haven't seen this in recent testing but it likely can happen if the user is doing multiple migrations or perhaps removes the profile right before clicking migrate