DB error on migration

[ynpmoose]

I saw the following error while migrating from 0.9.11 to 1.5. Is this cause for concern? If so, how do I fix it?
The system seems to be working properly from what I can tell.

webserver_1  | Apply database migrations...
db_1         | 2021-10-24 12:39:49.019 UTC [36] ERROR:  column documents_document.archive_filename does not exist at character 452
db_1         | 2021-10-24 12:39:49.019 UTC [36] STATEMENT:  SELECT "documents_document"."id", "documents_document"."correspondent_id", "documents_document"."title", "documents_document"."document_type_id", "documents_document"."content", "documents_document"."mime_type", "documents_document"."checksum", "documents_document"."archive_checksum", "documents_document"."created", "documents_document"."modified", "documents_document"."storage_type", "documents_document"."added", "documents_document"."filename", "documents_document"."archive_filename", "documents_document"."archive_serial_number" FROM "documents_document" WHERE "documents_document"."storage_type" = 'gpg' ORDER BY "documents_document"."created" DESC LIMIT 1
webserver_1  | Operations to perform:
webserver_1  |   Apply all migrations: admin, auth, authtoken, contenttypes, django_q, documents, paperless_mail, sessions
webserver_1  | Running migrations:
webserver_1  |   Applying django_q.0014_schedule_cluster... OK
webserver_1  |   Applying documents.1010_auto_20210101_2159... OK
webserver_1  |   Applying documents.1011_auto_20210101_2340... OK
webserver_1  |   Applying documents.1012_fix_archive_files... OK
webserver_1  |   Applying documents.1013_migrate_tag_colour... OK
webserver_1  |   Applying documents.1014_auto_20210228_1614... OK
webserver_1  |   Applying documents.1015_remove_null_characters... OK
webserver_1  |   Applying documents.1016_auto_20210317_1351... OK
webserver_1  |   Applying paperless_mail.0006_auto_20210101_2340... OK
webserver_1  |   Applying paperless_mail.0007_auto_20210106_0138... OK
webserver_1  |   Applying paperless_mail.0008_auto_20210516_0940... OK

[TobenderZephyr]

I did not do a migration myself, but I guess, all neccesary migration steps have been successfully applied automatically.

(The output of db_1: column documents_document.archive_filename seems to correlate with the line from webserver_1: Applying documents_1012_fix_archive_files)

I wouldn't worry as long as there were no documents archived, I guess?