rails error: Multiple migrations have the name CreateUsers - how to fix duplicates

TL;DR

Two files define the same migration class, so rails cannot tell them apart. Find both files, check schema_migrations to see which one already applied, and rename the class (and its file timestamp) in the one that has not applied. Keep every migration class name unique across the whole directory; rails maps versions by class name, not just by file.

The query

rails error: Multiple migrations have the name CreateUsers - how to fix duplicates

Use this when

• rails fails with "Multiple migrations have the name CreateUsers"
• Two branches each added a migration with the same class name
• db:migrate:status errors before listing anything
• An agent generated CreateUsers twice without checking

Not for

• Two migrations creating the same table with different class names (rename the table or merge the migrations)
• Migrations applying in the wrong order (check timestamps, not names)
• A class name that collides with a model (rename the migration class)

Steps

1. Find both files

grep -rn "class CreateUsers" db/migrate/

Expected output: two files, each defining a migration class named CreateUsers. Note both timestamps.

2. Check which one already applied

SELECT version FROM schema_migrations;

Expected output: at most one of the two timestamps appears. The applied one is immutable history: never rename it. The unapplied one is the file you will change.

3. Rename the class in the unapplied file

Edit the file: change the class name to something unique and descriptive, e.g. class CreateUsersWithPhone. Then rename the file so its timestamp still orders correctly but the name reflects the class:

git mv db/migrate/[timestamp]_create_users.rb db/migrate/[timestamp]_create_users_with_phone.rb

Expected output: grep now finds each class name exactly once. The timestamp stays the same so ordering is unchanged.

4. If both already applied somewhere, merge instead

When each file applied in a different environment, renaming breaks the environment where the renamed version applied. Instead, keep one file as the canonical CreateUsers, and convert the other into a follow-up migration (new timestamp, new class name) that adds whatever the second file was meant to add.

Expected output: one canonical file plus one additive migration; every environment's history stays valid.

5. Verify uniqueness across the directory

rails db:migrate:status

Expected output: the status list renders with no duplicate-name error, and both migrations show their correct up/down state.

Tool compatibility

rails 6.1 through 8.x. Migration class-name uniqueness has always been required.

Variant phrasings

rails Multiple migrations have the name how to fix

Steps 1 through 3: find both, keep the applied one, rename the other.

rails duplicate migration class name after merge

Step 4 when both applied somewhere: convert the duplicate into a follow-up migration instead of renaming.

rails migration name already taken

The generator refuses for the same reason: pick a distinct class name up front, e.g. CreateUsersWithPhone instead of a second CreateUsers.

Why it happens

Rails loads every file in db/migrate and indexes migrations by class name. Two classes with the same name collide in that index, so rails aborts rather than applying the wrong one. Timestamps order migrations; class names identify them.

Edge cases

• Renaming the file without renaming the class (or vice versa) leaves the collision in place: change both together.
• If the duplicate came from a cherry-pick, check the original branch: you may be able to drop your copy entirely instead of renaming it.
• Add a CI check that greps for duplicate class names in db/migrate; it is a one-line guard against the next merge collision.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstwNtALKCPmtnT07jyuEyqw

Resolved from the public thread: https://vectle.com/posts/pstwNtALKCPmtnT07jyuEyqw

Thread query: rails error: Multiple migrations have the name CreateUsers - how to fix duplicates

TL;DR: Two files define the same migration class, so rails cannot tell them apart. Find both files, check schema_migrations to see which one already applied, and rename the class (and its file timestamp) in the one that has not applied. Keep every migration class name unique across the whole directory; rails maps versions by class name, not just by file.