How to Safely Revert/Undo Last Migration in Django

Last Updated: by

Django’s migration system is powerful tool for managing your database schema changes over time. However, there are situations where you may need to revert or undo the last migration due to issues or changes in your application requirements. In this blog, we will explore how to revert last migration in Django, complete with examples to guide you through the process

Note: Reverting migrations should be done with caution in production environments, as it can result in data loss.

Step 1: Identify the App and Migration

Before you can revert the last migration, you need to identify the app and the specific migration you want to revert. Use the showmigrations management command to list all migrations and their status:

python manage.py showmigrations

Identify the app and migration you want to revert. The migration name is usually in the format 000X_migration_name.py, where X is a number.

Step 2: Revert the Last Migration

To revert the last migration, use the migrate management command with the app_name and the migration_name specified as arguments. Here’s the general syntax:

python manage.py migrate app_name migration_name

Example: Let’s say you have an app named blog and you want to revert the last migration, which is named 0003_auto_20231001_1234:

python manage.py migrate blog 0002_auto_20230930_2359

Step 3: Confirm the Reversion

Django will ask for confirmation before applying the migration. Confirm by entering yes:

Unapplying blog.0002_auto_20230930_2359... OK

The migration will be unapplied, effectively reverting the last migration for the specified app.

Step 4: Check the Migration Status

After reverting the migration, you can use the showmigrations command again to verify that migration status has changed. The migration you reverted should now appear as not applied.

python manage.py showmigrations

Additional Considerations

  1. Data Loss: Reverting migrations can result in data loss if the migration you are undoing made changes to the database schema or data. Ensure you have backups or a plan to restore data if needed.
  2. Dependencies: If the migration you’re reverting has dependencies on other migrations, Django will also unapply those migrations to maintain consistency.
  3. Migration Conflicts: Be cautious when reverting migrations in a collaborative development environment, as it can lead to migration conflicts. Ensure that your team is aware of any migration reverts.

Conclusion

Reverting the last migration in Django is straightforward process, but it should be performed with caution. It can be helpful during development to correct issues or adapt to changing project requirements. By following the steps outlined in this blog,, you can effectively manage your database schema changes and maintain a stable and reliable database structure in your Django projects/.