I'm trying to migrate email from Google Workspace to Exchange and have come across some conflicting guidelines. The documentation states that a subdomain is necessary, but it often uses the same domain for both the source and target, which makes sense due to MX record and routing requirements. In my case, the user import CSV has the original domain in the username column, while the newly created mailboxes in Exchange are under a different domain. So, do I actually need to set up subdomains even if the root domains are completely different with their own MX records? I'm really hoping to avoid creating new domain entries if I can help it.
3 Answers
Honestly, if the documentation isn't clear and you're under a time crunch, I say go ahead and try it without subdomains. Especially since you're consolidating to a single tenant. Just have a backup plan in case you run into any routing issues later on!
You're right about the hassle of this process! If you're using the built-in migration wizard in Exchange, it should handle most of the heavy lifting. While it’s typically recommended to use subdomains when both source and target have the same domain, you might get away without them if the root domains are distinct. Just be mindful of your MX records for proper routing. If you get stuck, consider using a migration tool like MigrationWiz as a fallback!
It sounds like you're in a tricky situation! To clarify, are you migrating directly from Google to Microsoft 365? Because as far as I know, the requirement for subdomains typically comes into play when moving between the same domains. Since you're definitely using different domains, you might not need those subdomains after all. But just to be safe, double check the migration documentation specific to your setup to avoid any surprises!
Thanks for the tip! I was hesitant about creating subdomains since my domains are completely different, but it’s good to hear I might not need to.
I appreciate the advice! It's comforting to know I have options.