See any of the following errors when using the Backlog migration tool? Here’s how to fix them.
Error 1: Couldn’t convert user “Username"
Why it happens: The user with the “username” doesn’t exist in the “users.csv file.”
How to fix it: Add a row for the username to the “users.csv” file.
If the message User could not be converted. “John Smith” is displayed, add “John Smith", “John Smith”, “”, “””” to the “users.csv” file.
Users involved in migration (e.g., as assignees or notification recipients) are listed in the exported “users.csv” file. If the user account has already been deleted from the source space, add a temporary user to the destination. After the migration is complete, you can delete the temporary user without any problems.
Why it happens: The file's character code is not UTF-8.
How to fix it: Convert the file's character code to UTF-8.
Error 2: The maximum number of status are 12 per project
Why it happens: “Add Status” and “Edit Status Name” have been performed nine or more times in the “Statuses” section in the source project’s settings.
How to fix it: If this error appears, the project can’t be migrated. Unfortunately, there’s no way to check before migration if the above was performed for a given project.
Error 3: No such attachment
Why it happens: An attachment referenced in the source assignment has already been deleted.
How to fix it: There’s no action needed. The assignment itself is migrated successfully, even if its attachments are missing.
Error 4: project.EditProject.err.exist.key
Why it happens: A project with the specified --projectKey already exists in the destination, or the user associated with the destination API key is not a member of the destination project.
How to fix it: Confirm that the API key used belongs to a user who’s a member of the destination project. Then, rerun the Backlog migration tool.
Error 5: You can upload to 500 attachments.code - 9
Why it happens: The migration exceeded the system limit of 500 attachments.
How to fix it: Use the --filter option to break down the migration into smaller chunks (by issue count or offset), then run the migration in parts.