[Django]-Django reversion fails to recover object after migration

As per GH issue:

Ah, I see. annoying. It appears that the revisions can handle deleting
a field, but not adding one.

Automating this is pretty much impossible. There are revision
databases out there with gigbytes of old revisions, and updating old
revision data when a new migration occurs could take days of runtime
per migration. It’s not really feasible.

My general approach is to delete the revision data after a migration.
If you really want to keep it, then you can write your own data
migration the in the app.

— Author of the project.

So it seems that reverting after migrating is simply not supported and while it may work sometimes its not meant to be used that way.