Laravel migration rollback not working — tables remain unchanged

[clarkeex]

I’m working on a Laravel project and I created several migrations.

When I run everything works fine and the tables are created.

php artisan migrate

But when I try to rollback :

php artisan migrate:rollback

nothing happens — the tables are still there. Even when I run:

php artisan migrate:reset

the database doesn’t change. Why is rollback not working, and how can I fix this?

[selcukcukur]

This happens because rollback only works if your migrations have a proper down() method defined. By default, Laravel’s migration stubs include both up() and down(). If you only wrote the up() method and left down() empty, Laravel has no instructions on how to reverse the migration.

Solution:

1. Check your migration files:

   public function up()
   {
       Schema::create('posts', function (Blueprint $table) {
           $table->id();
           $table->string('title');
           $table->timestamps();
       });
   }
   
   public function down()
   {
       Schema::dropIfExists('posts');
   }

   • If down() is missing or empty, rollback won’t drop the table.

2. Run rollback again:

   php artisan migrate:rollback

   • This will undo the last batch of migrations (the last group run together).

3. Reset all migrations:

   php artisan migrate:reset

   • This will call down() on all migrations.

4. Refresh migrations (drop + re-run):

   php artisan migrate:refresh

   • Drops all tables and re-runs all migrations. Useful for development.

5. Common pitfalls:

   • If you renamed or deleted migration files manually, Laravel’s migration history in the migrations table may not match.
   • If you changed the up() method but didn’t update down(), rollback won’t behave as expected.
   • Always ensure Schema::dropIfExists() is used in down() for safety.

[clarkeex]

@selcukcukur thanks