Yep, same exact name over and over.
I know that the system requires the mission name to be unique. So a possible quick and dirty fix would be to add an increment number after the project name during import. Like you do with objects.
But that still doesn't solve the root cause of not factoring in the project ID into the update. So the problem may surface again if someone somehow manages to create duplicate names through mergeing or faulty import or some other weird operation.