Fix SMTP Proxy Address Errors in G Suite to Microsoft 365 Migration
Question details
Resolve a G Suite to Microsoft 365 migration failure caused by a target mailbox SMTP address mismatch or an incorrect target delivery domain.

- Product
- Google Workspace (formerly G Suite) and Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- Migrating Google Workspace mailboxes to Exchange Online using a migration batch with a target delivery domain.
- Observed behavior
- The migration reports that the target mailbox lacks an SMTP proxy address matching the domain specified in the error. A mistyped target delivery domain can cause this mismatch.
Copy the exact domain and affected mailbox address from the migration error, and have an administrator account with access to Google Admin and the Exchange admin center. Check the migration batch's configured target delivery domain before changing any mailbox addresses.
Verify the source address and target mailbox SMTP aliases
Use this check to determine whether the affected Exchange Online mailbox has the expected address and an alias matching the intended delivery domain.
Open the Google Admin console, go to Directory > Users, and select the affected user. Review the primary email address and alternate email addresses, then compare them with the source address used in the migration batch.
Open the Exchange admin center, go to Recipients > Mailboxes, and select the target user. Open the email address management section and inspect the primary SMTP address and aliases. Compare their domain suffixes with the domain shown in the migration error.
In an Exchange Online PowerShell session, run Get-Mailbox -Identity "user@yourdomain.com" | Format-List PrimarySmtpAddress,EmailAddresses, replacing the example address with the target mailbox address. Review the SMTP entries for the intended routing domain.
If the intended delivery domain is correct but the mailbox lacks the required alias, use the mailbox's email address management section to add the verified SMTP alias. If the domain in the error is misspelled, correct the batch configuration instead of adding an alias for the typo.

Recreate the migration batch with the correct target delivery domain
Use this solution when the batch contains a misspelled or incorrect delivery domain. The reported issue was resolved by creating a new batch with the correct domain.
Use WPS Office for Documents During Your Microsoft 365 Transition
WPS Office is a free, lightweight, easy-to-use alternative for document work, with a familiar interface and Microsoft Office format compatibility for seamless migration of everyday files. It does not repair Exchange Online SMTP aliases or perform Google Workspace mailbox migrations.

Frequently Asked Questions
What does a missing SMTP proxy address error mean during migration?
It means the target mailbox does not have an SMTP address matching the domain expected by the migration configuration. In the Exchange admin center, open Recipients > Mailboxes, select the user, and review the email addresses. Also check the batch's target delivery domain for a typo.
How can I list a mailbox's SMTP aliases in PowerShell?
Connect to Exchange Online PowerShell and run Get-Mailbox -Identity "user@yourdomain.com" | Format-List PrimarySmtpAddress,EmailAddresses. Replace the example address with the affected mailbox. The EmailAddresses output includes its SMTP proxy addresses.
Should I add an alias for the domain shown in the error?
Only if that domain is the verified, intended delivery domain for your organization. If it is misspelled or incorrectly configured in the batch, correct the batch instead. Do not add an alias solely to match a typo.
Do I need to change the user's primary email address?
Not necessarily. The target mailbox can have a routing alias separate from its primary SMTP address. Check both fields in the mailbox's email address management section before making changes.
Can WPS Office fix this mailbox migration error?
No. This error requires changes in Exchange Online mailbox addressing or migration batch configuration. WPS Office can help with migration documentation and spreadsheets, but it does not manage SMTP proxy addresses or Exchange migration batches.




