Last modified: Sep 14, 2023 By Alexander Williams

How To Solve "Django makemigrations no changes detected"

The Django makemigrations command is used to create a new migration file for your Django project. In this file, you will find the SQL statements that are used to update your database schema.

Getting the message "No changes detected" when you run makemigrations means Django hasn't detected any changes to your models since you last ran the command.

In this article, we will discuss the most common causes of this error and how to fix it.


Django's project settings (usually found in include an INSTALLED_APPS setting that lists all the apps that are installed.

If you forget to add or include your app in this list, Django won't consider it when running the makemigrations command for that app. As a result, it will not detect any changes.

The solution to this issue is to make sure the app you are trying to migrate is properly added to your project's INSTALLED_APPS list. INSTALLED_APPS might look like this:

    # ...
    'myapp',  # Replace 'myapp' with the actual name of your app
    # ...

2. No Model Changes

Another reason for this message is that you haven't made any changes to your Django models.

makemigrations compares the current state of your models in your Python code with the previous state stored in migration files.

If there are no differences, it assumes there are no changes to be applied.

3. Unsaved Model Changes

Another potential reason for the "No changes detected" error in Django's makemigrations command is when you have made changes to your models but forgot to save those changes to your models file (typically

ensure that you save any modifications you make to your models by saving the file.

4. Migrations Already Applied

If all migrations for your app have already been applied to the database, running makemigrations again won't produce any new migration files because there are no pending changes.

You can check the status of migrations using:

python showmigrations

5. Wrong App Selected

You might mistakenly run the makemigrations command for an app that you didn't intend to make changes to. If there are no changes in the selected app's models, Django will correctly report "No changes detected."

To resolve this issue, make sure you run the makemigrations command for the correct app where you've made model changes.

For example, if you have two apps in your project, "app1" and "app2," and you made changes to models in "app1," you should run:

python makemigrations app1


The "No changes detected" error with Django's makemigrations command is a common issue, but it can be easily resolved by carefully examining your project and following the troubleshooting steps outlined above.