Most migration problems are one of about six things, and all of them are quick to sort out. Find your message below.
"Azure authentication failed. Check the organization URL and Personal Access Token."
The usual suspects, in the order worth checking:
The token has expired. Azure tokens have an end date and expire silently. Create a fresh one.
The token is missing a permission. It needs both Test Management (Read) and Work Items (Read). One without the other isn't enough.
The token belongs to a different organization. Tokens are tied to the organization they were created in.
Something got clipped on the way over. Copy the token again - a missing character at the end looks exactly like a wrong token.
"Azure organization URL is invalid - enter the organization URL, not an email address"
You've pasted your sign-in name instead of a web address. What's wanted is something like https://dev.azure.com/your-organization.
"Azure organization URL must include the organization"
The address is missing the organization part. https://dev.azure.com on its own doesn't say which organization, add yours on the end.
"Azure project not found: …"
Almost always spelling. Azure project names are case-sensitive and may contain spaces, and TestCollab sends the name exactly as you typed it, it won't quietly correct payments web to Payments Web.
Open the project in Azure and copy the name straight from there.
"Project … was already imported into this TestCollab project"
This is a guard, not a fault. A migration is a one-time move, and re-running it into the same project would give you a second copy of everything.
If you want another attempt - different options, a cleaner result - create a new TestCollab project and migrate into that one. Migrating the same Azure project into a different TestCollab project is perfectly fine.
"An import for this source project is already running"
The same migration is already in progress, probably in another tab. Find it and watch it there. If you genuinely want to stop it, use Cancel Import on that screen.
The counts on the preview don't match what arrived
Two harmless explanations:
Very large libraries. The number shown when you validate the project is a quick estimate so you're not left waiting on the screen. It can read a little high. The migration itself always walks the whole project, so trust the Summary screen's numbers over the preview's.
Test cases that aren't in any test plan. If you left that option unticked, those cases were skipped on purpose, the confirmation screen told you how many. To bring them across, start a fresh migration into a new project with the box ticked.
The migration finished, but a few items are listed as failed
Open Failed import items on the Summary screen. Each row names the item and the reason it couldn't be created. Everything else came through normally, one awkward test case doesn't stop the rest.
If the reasons don't make sense to you, send us a screenshot of that list and we'll take a look.
The migration failed partway through
If Azure stops responding for long enough that we can't reliably finish, the migration stops and reports the failure rather than finishing early and leaving you short. That's intentional, a migration that quietly omits three hundred test cases is far worse than one that tells you it didn't work.
Whatever had already arrived stays in the project. Wait a few minutes and start a fresh migration into a new project. If it happens again, get in touch and include the failure message.