During cutover, are you focused on job completion percentages in MigrationWiz and missing the early warning signs that an entire batch is trending the wrong way?

Per-job progress percentage is usually the least actionable metric in an active cutover window. When the percentage finally looks off, the underlying issue has often been happening for hours.

The first metric worth tracking is items per hour. If items per hour drops and stays down by 50 percent or more within the first two hours of the cutover pass, it is a strong indicator that EWS throttling or service protection has kicked in. Finding that trend at hour two is still recoverable. Discovering it at hour eight typically means the maintenance window is already lost.

Second, watch failed item count in real time. A small number of errors in a large batch is normal, but a rising failure trend across many jobs at the same time usually points to a permission issue or a conditional access change impacting the service account, not ordinary throttling.

Third, look at the ratio of jobs in error versus jobs still progressing. If 20 percent of jobs are in a hard error state while 80 percent move normally, that is more consistent with a subset of accounts having a specific issue than with a tenant-wide throttling event.

Which metrics are you actively monitoring in MigrationWiz during your cutover window?

#BitTitan #MigrationWiz