We built MigrationWiz to handle all types and sizes of migration projects. It’s fast and easy for standard data and mailbox migrations; full-featured and customizable for more complex scenarios. Our MigrationWiz Master Class series introduces you to options and techniques that will boost your expertise so you can deliver a smooth migration every time.
Recipient Mapping: Everything Where it’s Supposed to Be
If there’s one thing you need to make sure of when you’re doing a migration, it’s that everything gets to the right place. Recipient mapping puts you in control during mailbox migrations, so nothing is lost. Here’s what you need to know:
What is it? Recipient mapping is used in mailbox migrations to ensure that user information maps properly from the source to the destination.
When will I use it? Use recipient mapping when the username or domain name is different between your source and destination. In addition, every Microsoft 365 tenant-to-tenant migration will require recipient mapping to ensure that user information maps properly from the Source to the Destination when the username or domain name have changed.
Where do it find the feature? In Advanced Options/General Options.
How do I learn to use it? Read MigrationWiz- Advanced Options and General Options on the BitTitan Help Center
Is there anything else I should know? If you’re going to be using recipient mapping on a large migration with 5,000 or more users, be sure to refer to the Help Center article for instructions on how to mitigate performance loss.
What are some examples? Recipient mapping is used in migrations that result from a merger, acquisition, or divestiture when the destination domain is different from the source. You’ll also use it for name changes (such as Bob to Robert) or changes in naming convention (like SueBee to Susan.Bee).