During file imports, a potential conflict can arise if a file with the same name but a different hash already exists in the migrations directory (This may happen because sometimes we change existing migration files).

The current error message simply indicates a file name collision without providing details on diff between files or origin.

This lack of information makes it difficult for developers to determine the cause of the conflict and deciding whether to make changes or whether they are not required