Migration error fixes

A Jira Cloud Migration Assistant pre-migration check found more than 10 user aliases tied to one primary email address.

A Jira board lists administrator groups that are not valid, so the Jira Cloud Migration Assistant cannot prepare it for migration.

A Jira permission scheme names a user who does not exist, so the Jira Cloud Migration Assistant cannot import the scheme.

A Marketplace app hit an error on the server side during app migration, which can stall or time out the app migration.

The Confluence migration could not add users to groups because the account running it is not an admin on the cloud site.

The Confluence Cloud Migration Assistant could not export space data from the server, usually due to disk space, memory or open file limits.

A Migration Manager agent could not submit a migration job to SharePoint, which Microsoft links to antivirus software on the agent machine.

The Migration Manager agent cannot read the source file share because it is not a network share or the agent account lacks permission.

Migration Manager cannot find the destination SharePoint site, subsite or OneDrive you set for the task.

Migration Manager cannot read the cloud source because the Microsoft 365 migration app is not authorised in the source account.

Migration Manager could not call the Google Drive API because the access token is invalid or expired.

azcopy login is blocked because a Conditional Access policy only allows sign-in from certain device types.

AzCopy cannot reach Azure because the proxy server it has been told to use cannot be found.

AzCopy does not trust the TLS certificate it receives, usually because a proxy is inspecting the traffic.

An AzCopy copy between two storage accounts fails because the destination account cannot reach the source over the network.

Azure Storage is throttling AzCopy because the transfer is sending more requests or data than the account allows.

Your shell cannot find the aws program, so the AWS CLI is not installed properly or is not on your PATH.

The AWS CLI ran, but the identity it used is not allowed to call the S3 API the command needs.

The access key the AWS CLI sent is not a valid key, so AWS rejected the request.

AWS could not verify the request signature, usually because the computer clock is wrong or the secret key is mishandled.

The AWS CLI does not trust the TLS certificate it receives, often because a corporate proxy is inspecting traffic.

Agentless VMware replication fails because the NFC buffer on the ESXi host is too small for the number of disks being replicated.

An agentless VMware replication cycle timed out because the source server is busy.

Deploying the Azure Migrate appliance OVA in vSphere fails because the download is corrupt or incomplete.

The appliance cannot register with the Azure Migrate project.

AWS Application Migration Service (MGN) is not hearing from the replication agent on the source server.

MGN replication backlog keeps growing because data is written to the source faster than it can be sent.

MGN cannot take a consistent EBS snapshot of the replicated disks.

An MGN test or cutover launch fails because the EC2 launch template does not name a valid subnet.

The mailbox move stopped because it found more corrupt or missing items than the move request allows.

A hybrid move from Exchange Server stalls and the move report shows MapiFxProxyTransientException: the data export was cancelled due to a timeout.

Moving a cloud mailbox back on-premises fails because the on-premises remote mailbox does not have the matching ExchangeGUID.

Offboarding a mailbox from Exchange Online to on-premises fails because the on-premises user still has mailbox attributes set.

The migration found some data loss and will not complete until an admin reviews and approves the skipped items.

The migration request fails or skips messages that are bigger than the maximum message size allowed in the target mailbox.

A cutover migration cannot create its Outlook Anywhere migration endpoint, often with Error 0x6ba (The RPC server is unavailable).

A cross-tenant mailbox move fails because the user does not have a Cross-tenant User Data Migration licence.

A cross-tenant mailbox move fails because the source mailbox is not in the scope the source tenant published for migration.

A cross-tenant mailbox move fails because the target MailUser has a proxy address in a domain the target tenant does not own.

A cross-tenant mailbox move fails because the source mailbox is larger than the quota the mailbox will have in the target tenant.

A cross-tenant mailbox move fails because the target MailUser does not have the ExchangeGuid of the source mailbox.

A hybrid move to Exchange Online fails because an active or orphaned move request already exists for the user.

A hybrid remote move fails because a soft-deleted or inactive mailbox in Exchange Online has the same email address.

Hybrid moves to Exchange Online fail because the on-premises hybrid server computer account is in a protected Active Directory group.

Hybrid mailbox moves keep retrying because an on-premises Forefront TMG server is blocking HTTP requests from Microsoft 365.

An IMAP migration to Exchange Online cannot sign in to the source mailbox with the user name and password in the CSV file.

An IMAP migration endpoint or batch cannot reach the source mail server because the server name is wrong or does not resolve in public DNS.

A Gmail or Google Workspace mailbox migration to Microsoft 365 fails because the Google account needs an app password for IMAP.

Google's data import from Exchange Online could not sign in to the Microsoft 365 source, or access was denied.

The import cannot write to Google Workspace because domain-wide delegation is missing scopes or access was revoked.

The target Google Workspace user ran out of storage during the import.

An email, contact or other item was too large for Google Workspace to import.

Google Workspace Migration for Microsoft Exchange (GWMME) cannot find or access the target Google user.

Google Workspace Migrate hit the daily API quota for the project it uses.

Google Workspace Migrate is sending more requests than a source or target system will accept.

SPMT or Migration Manager skipped a file because its full path in SharePoint would be too long.

A folder could not be migrated because its name is not allowed in SharePoint or OneDrive.

The migration computer ran out of space in its working folder while packaging a file for upload.

SPMT skipped a file because it is bigger than the tool or service allows.

SPMT could not read a file from a SharePoint Server source because someone has it checked out.

Migration Manager skipped a file whose name contains characters SharePoint does not allow.

The OneDrive sync app cannot sign in because it is having trouble connecting to the cloud.

A native cross-tenant OneDrive move shows Failed because the user already has a OneDrive in the target tenant.

Entra Connect tried to soft match an on-premises object to a cloud object that is already linked to a different on-premises object.

A sync export failed because the mail, proxyAddresses, signInName or userPrincipalName value already belongs to another object.

Soft matching found a user, group or contact of a different type with the same address.

An object exceeds an Entra ID size or count limit, most often because of too many userCertificate values.

Entra ID blocked Entra Connect from taking over a cloud user because that user is protected.

A synced user has the same userPrincipalName as a cloud user that holds an admin role, so Entra Connect will not soft match them.

Users cannot sign in to Teams because Teams is not turned on for them.

A Teams channel or chat is stuck in migration mode after a message import.

Microsoft 365 will not remove a domain because users, groups, email addresses or SIP addresses still use it (DomainNotEmptyException).

You cannot add a custom domain to the new tenant because it is still verified in another Microsoft 365 or Entra tenant.

Group-based licensing could not assign a product to some members because the tenant has run out of that licence.

A licence cannot be assigned because one of its service plans clashes with a plan the user already has from another product.

A licence was not assigned because the user has no usage location or one where the service is not offered.

Assigning an Exchange Online licence fails because another object already has the same proxy address.

Entra cross-tenant synchronization leaves the mail attribute unchanged on a target user who has an Exchange licence.

WordPress cannot connect to its MySQL or MariaDB database, so no page loads.

A PHP fatal error stopped WordPress loading. Some sites show a blank white screen instead.

The home page loads but every post and page returns 404, because the rewrite rules did not come across.

The browser reports a redirect loop after you move WordPress behind a load balancer, reverse proxy or CDN that handles SSL.

The migrated site sends visitors or the admin login back to the old address because the site URLs in the database were not updated.

Uploads, including large site backups for import, fail because PHP limits the size of each uploaded file.

The site is stuck in maintenance mode after an update or migration was interrupted.

PHP ran out of memory while loading WordPress, often on a new host with a lower memory limit.

The recipient's server bounced your message because it failed the SPF check for your domain.

A security or delivery restriction is blocking the message. After a cutover this is often a bad MX or SPF record or a connector problem.

SPF returns a permanent error because the domain has more than one SPF record or the record needs more than 10 DNS lookups.

The message failed DMARC and the sending domain's policy is reject, so the receiver rejected it.

Microsoft 365 cannot turn on DKIM signing for a custom domain because it cannot find the selector CNAME records.

Mail forwarded or relayed by Exchange Online was rejected by the next server, often with 554 5.7.1 Relaying denied.

Domain setup in Microsoft 365 will not verify because it cannot see the MS= TXT record.

The TPM management console cannot see a TPM, so the PC fails the Windows 11 TPM 2.0 check.

The PC fails the Windows 11 Secure Boot check because the firmware boots in Legacy or CSM mode.

The Windows upgrade rolled back because of a driver problem.

Windows setup stopped because the PC may not meet the minimum requirements for Windows 11.

The Windows upgrade failed because the PC does not have enough free disk space.