No Target SID Found for Profile Translation
Resolve profile translation failures during device migration.
Overview
Error Message
"No target SID found for profile translation, exiting."
This error occurs during device migration when the Cloudiway agent cannot locate the target user's Security Identifier (SID) to translate the Windows profile.
Profile Translation Process
Root Cause
Target Email Does Not Match UPN
The Cloudiway agent looks up the target user using the Target Email field from your mapping. If this email doesn't match the user's UserPrincipalName (UPN) in Azure AD, the SID lookup fails.
Common Scenario
Target Email in Cloudiway: john.doe@company.com
Actual UPN in Azure AD: jdoe@company.onmicrosoft.com
Why This Happens
- • User's primary email differs from their UPN
- • UPN uses the onmicrosoft.com domain
- • Email aliases are used instead of UPN
- • Domain changes after user creation
Solution
Update Target Email to Match UPN
Find User's UPN in Azure AD
Navigate to Microsoft Entra admin center → Users → Select user → Check the User principal name field
Update Cloudiway Mapping
In the Cloudiway portal, update the Target Email to match the user's exact UPN from Azure AD
Retry Migration
Re-run the device migration. The agent should now successfully locate the target user's SID
Bulk Update
Verification
Confirm UPN via PowerShell
Azure AD PowerShell
Get-AzureADUser -ObjectId "user@domain.com" | Select-Object UserPrincipalNameMicrosoft Graph PowerShell
Get-MgUser -UserId "user@domain.com" | Select-Object UserPrincipalNameAlternative: Change User's UPN
If needed, you can change the user's UPN in Azure AD to match the email:
Set-AzureADUser -ObjectId "old-upn@domain.com" `
-UserPrincipalName "new-upn@domain.com"