Are you burning hours waiting for BitTitan support because your case was opened without the details they always request up front?

When a MigrationWiz job fails during a cutover window and you have to engage BitTitan support, the initial reply from the queue almost always asks for the same information. If you include it when you open the ticket, you remove an entire back-and-forth from a process where you usually do not have time to spare during a maintenance window.

Expect support to ask for the MigrationWiz project ID, the impacted source and destination UPNs, and the specific MigrationWiz job ID tied to the failing migration. They will also want the error code and the full error message text from the item-level report export, along with the timestamp of the failure, and they will ask whether the issue impacts every account in the batch or only a subset.

You can pull the project ID directly from the browser URL while inside the project in the MigrationWiz portal. The job ID appears in the user list view next to each account row. Before you open the ticket, capture the exact error text from the item report. A screenshot works. Writing a prose description instead of supplying the error code typically adds at least one more exchange to the case.

Do you already have a MigrationWiz support escalation template with these fields filled in before your cutover window starts?

#BitTitan #MigrationWiz