The JumpCloud Active Directory Migration Utility (ADMU) migrates Active Directory or Entra ID / Azure AD–joined Windows users to local accounts so the JumpCloud agent can manage them. Domain accounts cannot be taken over directly by the agent; they must be converted to a local profile first. ADMU automates profile, registry, permissions, and optional domain-unbind / agent steps that would otherwise be manual.
Detailed guides, limitations, and troubleshooting live in the Wiki. Good starting points:
| Topic | Wiki |
|---|---|
| Planning and first run | Getting Started |
| Tool Options + GUI | GUI Parameters |
| Known constraints (certs, credentials, defaults, etc.) | Limitations |
| Logs and failures | Logging, Troubleshooting |
| Remote migration (CLI, JumpCloud Commands, bulk) | Invoke admu from JumpCloud Agent |
- GUI and CLI: Download the latest build from Releases. Each release includes
gui_jcadmu.exe(interactive GUI and CLI in one binary) anduwp_jcadmu.exe, which migration deploys into the Windows directory to fix UWP Appx package issues.
Only the gui_jcadmu.exe file is required for the ADMU, double click to run the GUI or pass parameters for scripted CLI use. The uwp_jcadmu.exe file is automatically downloaded and deployed into the Windows directory during migration to fix UWP Appx package issues.
Questions, bugs, and feature requests: GitHub Issues on this repository, support@jumpcloud.com, or the feedback form.
This project is licensed under the MIT License.