Even though you don’t see a database with the same name, the error suggests that a database with the target name was already created before the import, and that's the issue — BACPAC imports require the database to not exist at all.
Even though you didn't create a database manually, the import process might still hit that error if:
- The target database already exists, even if it’s empty.
- A database with the same name got created due to a previous failed import.
- Or the tool creates the DB first, then attempts to import and fails if anything at all is present.
Open the BACPAC file and review its contents to make sure it only includes the schema and data from the source database. It shouldn't contain user-specific objects like logins, users, roles, or anything else tied to particular accounts.