Is there a guideline to migrate from obsoleta django-encrypted-fields?

[domdinicola]

django-encrypted-fields.

[hendrikschneider]

I think the easiest is to create a new temporary field, read all values from the current encrypted field, save them into the temporary field.

After this is done, rename the original field to a different name and rename the temporary field to the original field name. Afterwards the data should be properly there. Lastly, when everything works you can delete the field with the old data (Be Careful here).

[MrWeeble]

I don't believe that it is possible to do this directly.

The earliest version of this library requires Django >= 2.2 which requires Python 3 because Python 2 compatibility was dropped in 2.0
however django-encrypted-fields requires keyczar which only exists for Python 2
Hence there is not a combination of Django and python in which you can install both libraries in order to do a data migration to copy data from one field to another

As I see it there are a few options

1. Do a migration from django-encrypted-fields to another field type supported in Python 2 as @hendrikschneider suggested above. Perform upgrades, and then do a migration from that type to django-fernet-encrypted-fields
2. Extract the data decrypted, do the upgrade offline and then reimport the data

1 is more steps, 2 is less secure as you have a decrypted copy of the data lying around.

One possible intermediate field type would be the similarly named django-fernet-fields which has been abandoned for years, but does bridge the gap between Django 1.11/Python 2.7 and Django 2.2/Python 3.7