What is a one sentence summary of your feature request?
Introduce a dedicated client migration dashboard with staged rollout and optional rollback capability for large-scale EPP migrations.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
In large enterprise environments with 1,000+ endpoints, the current EPP Client Migration feature works from a functional standpoint, but it lacks operational visibility and structured control during the migration process. At the moment, migration status is mainly confirmed through “Migration SUCCESS” log entries, and there is no centralized dashboard that shows overall progress such as how many endpoints were selected, how many have successfully migrated, how many are still pending or offline, or whether any failures occurred. Monitoring requires manual comparison between the old and new server endpoint lists, which becomes inefficient and error-prone at scale. Additionally, there is no built-in staged or batch migration capability, meaning large numbers of endpoints may reconnect simultaneously, potentially causing performance spikes. There is also no structured rollback option if post-migration issues arise, such as policy misconfiguration or connectivity problems. In enterprise environments operating under change management frameworks (such as CAB or ITIL), migration progress needs to be measurable, reportable, and controlled. Introducing a dedicated migration dashboard, staged rollout options (by group, OU, or batch size), and an optional rollback window would significantly improve transparency, reduce operational risk, align with governance requirements, and enhance overall enterprise readiness of the product.
How do you currently solve the challenges you have by not having this feature?
Right now, we handle migration validation manually. We have to compare the list of endpoints on the old and new servers to see which devices have reconnected, check their online status individually, and review “Migration SUCCESS” log entries to confirm completion. We also verify license usage separately to make sure everything is aligned after migration. In larger environments, we try to reduce risk by migrating smaller groups of devices in phases, but this requires manually selecting groups, monitoring their reconnection, validating policy application, and then repeating the same process for the next batch. This approach works, but it involves a lot of cross-checking, constant monitoring, and manual verification across multiple screens. There is no single place that shows overall migration progress, pending devices, or failures, which makes the process time-consuming and operationally heavy during large-scale deployments.