Howto for Windows

[quma]

Hallo,
can you extend the documentation with a how to convert enpass to keepass with a windows system ?

thank you

[joergschultzelutter]

Hi @quma ,

running the program on a Windows system does not differ from running the program on e.g. Linux or MacOS.

• First, install Python on your local machine. Use the version from https://www.python.org/. Alternatively, check if the Microsoft/Windows Store offers a Python installation. Afaik, they provide one, too.
• Switch to the console (cmd.exe) and navigate to a directory of your choice (ideally the one where you saved this repository's contents)
• Now I'd recommend installing a virtual Python environment (https://docs.python.org/3/library/venv.html). Run python -m venv venv which will create a directory called venv in your current directory
• Activate that virtual environment: enter .\venv\scripts\activate. This should change your DOS prompt and add a leading (venv) to it
• Now you can install the required packages: pip install -r requirements.txt

Your virtual environment is now ready and you can follow Step3 from the original instructions. Just remember that whenever you exit cmd.exe and want to rerun the program again, you need to activate the virtual environment, too.

Does that help?

[quma]

thanks, I will try it

[quma]

Hallo joerg
thank you very much I was finally able to import my passwords.
But one last question, is it possible to import also the created and last modifiyed date from enpass to?

[joergschultzelutter]

Great to hear ❤️

Regarding your question: the converter does take the "created_at"/"updated_at" timestamps into account, assuming that Enpass provides these as part of their database export.

tl;dr: The timestamp information should be present in the Keepass file. In case the "updated_at" timestamp was not present, I use the value from the "created_at" timestamp.

If this is not the case for you, we would need to take a look at your database export.

[quma]

Hallo
this is how the date looks like in Enpass:

and how it looks like in keepassxc:

This is the entry in my exported json file.

• uuid is diffrent, maybe gets new uuid`s in keepass?

 {
            "archived": 0,
            "auto_submit": 1,
            "category": "login",
            "category_name": "Login",
            "createdAt": 1219268188, <--------------------- 20.08.2008
            "favorite": 0,
            "field_updated_at": 1343600423, <-------------- 30.07.2012
            "fields": [
                {
                    "deleted": 0,
                    "label": "Username",
                    "order": 1,
                    "sensitive": 0,
                    "type": "username",
                    "uid": 10,
                    "updated_at": 1343600423, <-------------- 30.07.2012
                    "value": "xxx@xxx.com",
                    "value_updated_at": 1343600423 <-------- 30.07.2012
                },
                {
                    "deleted": 0,
                    "label": "E-Mail",
                    "order": 2,
                    "sensitive": 0,
                    "type": "email",
                    "uid": 12,
                    "updated_at": 1665324366, <---------------09.10.2022
                    "value": "",
                    "value_updated_at": 1665324366 <--------- 09.10.2022
                },
...
            "note": "",
            "subtitle": "xxx@xxx.com",
            "template_type": "login.default",
            "title": "User Acount",
            "trashed": 0,
            "updated_at": 1772133040, <-------------------- 26.02.2026 
            "uuid": "05cxxxxx-xxxx-xxxx-xxxx-xxxxxxx7e995"
        },

Have no idea why it shows me the wrong date 09.10.2022

[joergschultzelutter]

Thank you - I will have a look at this and transfer your timestamps to some of my export databases. This might take a few days as I am snowed-under at work (blame my employer). Nevertheless, that data is quite helpful.