The messages you might see, what they mean, and what to do. Most of them are the platforms talking; MigrateX passes the reason through so you can act on it.
| You see | It means | Do this |
|---|
| Permissions pending / N of M granted | Consent is propagating or was partial | Wait a minute, Re-check; then Grant consent again |
| Source and target are the same tenant | You signed in to the wrong tenant for the second connection | Use a private window and sign in as the other tenant's admin |
| Scope failed (Google) | One scope is missing or mistyped in domain-wide delegation | Edit the existing entry; copy the scopes from MigrateX again |
| Every scope failed: unauthorized_client (Google) | The Workspace has no Google Cloud organization yet, so delegation is refused | A super administrator signs in at console.cloud.google.com once and accepts the terms; wait a few minutes, then Verify again |
| “… asked us to slow down — resuming in N min” | The platform rate-limited this mailbox or drive. Each refusal in a row waits longer than the last (up to 15 minutes), so a busy tenant is not hammered | Nothing. The pass continues by itself; the wait resets as soon as a slice finishes |
| “… kept refusing this work for over 90 minutes” | Twelve refusals in a row with no progress — usually a quota that resets daily, or one item the platform cannot process | Open “Items that need a look” for the item's own error. Press Resync later; a daily quota clears within 24 hours |
| “Excluded from the migration while a pass was running” | Someone was excluded on the Users tab mid-pass; their parts stopped at the next slice | Nothing, unless it was a mistake: include the person again and press Resync |
| “the target folder for … is missing; recreating it” | A folder (or label, contact folder, calendar) was deleted in the target while the migration ran | Nothing. It is recreated on the next slice and the pass continues; what was already copied is not copied again |
| “The message was copied, but not all of it: …” | The message is in the target, but an attachment or a flag could not be added | Open the item in the target to check; the note stays under “Items that need a look” and the message is never copied twice |
| “The user list and progress from the previously connected tenant were cleared” | A side of the project was connected to a different tenant than before; the old tenant's matches and progress would have pointed at accounts that do not exist there | Run the assessment again and match users; nothing in either tenant was changed |
| “has no OneDrive yet and it could not be created automatically (SharePoint POST failed (401) …)” | The target user has never opened OneDrive, and the SharePoint admin service refused to create one for MigrateX | Ask the person to open OneDrive once (it is created on first sign-in), then press Resync. If this happens for every user, the MigrateX staff must add the SharePoint application permission to the app registration |
| “Creating the OneDrive — Microsoft takes a few minutes” | The target user has never opened OneDrive, so it does not exist yet. MigrateX asked Microsoft to create it and is waiting | Nothing — the pass continues by itself, usually within 5–15 minutes |
| “has no OneDrive yet … could not be created automatically” | The target user has no license that includes OneDrive, or sign-in is blocked | Assign a license with OneDrive (or unblock sign-in), then run a delta pass for that user |
| IMAP sign-in failed (Zoho) | Wrong or expired app-specific password, IMAP not enabled for that mailbox, or two-factor off | Generate a new app password (accounts.zoho.com → Security → App Passwords), enable IMAP for the user, upload the CSV again |
| No address book / calendar reachable over DAV (Zoho) | The CardDAV/CalDAV address does not match your Zoho region or account layout | Adjust the address on the Zoho connection page (region hosts: contacts.zoho.eu / calendar.zoho.in …) or clear it to skip contacts or calendars |
| Queued work is waiting for a migration worker | No worker process has checked in for over a minute | Usually clears by itself within a minute (workers start on demand). If it stays, contact support |
| You see | It means | Do this |
|---|
| Waiting for a worker to pick this up | The job is queued behind others, or the service is catching up | Give it a few minutes; if it stays there, contact support |
| 429 / throttled, continuing shortly | The platform asked for a pause | Nothing — the rate governor waits and resumes |
| 413 message too large | Larger than the target accepts | Listed by name; move it by hand if it matters |
| 423 file locked | Someone had it open in the target | Retry later; retries handle it automatically |
| Stopped (a user) | A part failed five times | Open the Migration tab, read the reason, fix, retry |
| Items that need a look | Notes and failures | Failures: Retry. Notes: read; they list what can't move |