Failed Tasks Are Part of Every Migration

Every MigrationWiz project will have failed tasks. The goal isn’t to avoid them entirely. It’s to diagnose and resolve them fast before they compound.

Start With the Right Questions

Before touching any settings, understand what actually failed.

What does the error message or code say? Is the failure related to connectivity, access permissions, or data? Are multiple users hitting the same error or is it isolated? Is the failure originating in the source environment or the destination? Can it be resolved through configuration changes or does it require manual intervention?

The answers to these questions determine the fix. Retrying without answering them produces the same failure.

Work Through Failures Systematically

Check the error details in the MigrationWiz dashboard first. Error messages are often specific enough to identify the problem without further investigation.

Group errors by type before resolving anything. If multiple mailboxes failed due to an authentication error, fix the credentials for all of them before resubmitting any. Resolving them one at a time while the underlying issue remains is wasted time.

Use the Retry function for transient failures. Throttling issues and temporary connectivity problems often resolve on resubmission without any configuration change. Persistent failures after retry need deeper investigation.

Check the BitTitan Knowledge Base before opening a support ticket. Every error code is documented and most searches return specific resolution steps that can be applied immediately.

Submit a support request when the issue is complex or backend. BitTitan support can resolve issues that aren’t accessible from the customer side. Don’t spend hours on a problem that a support ticket resolves in minutes.

Resuming Failed Jobs

MigrationWiz picks up where it left off when failed items are resubmitted. The platform doesn’t restart the entire job. It continues from the point of failure, which means resolving and resubmitting failed tasks doesn’t require re-migrating data that already transferred successfully.

A failed task is information. It tells you something about the source environment, the destination configuration, or the migration settings that the pre-migration assessment didn’t surface. Address it systematically and the project stays on track.