Enpass CSV import

[kzshantonu]

Hello devs,
Would really appreciate an Enpass CSV import option
The format is fairly simple:
Title, field_name1, field_value1, field_name2, field_value2, field_name3, field_value3......

Here's a sample:
https://pastebin.com/raw/jR3G1TAa
thanks

[perry-mitchell]

Thanks @kzshantonu. I must say that that export format is quite awful tbh.. The whole key-value system with optional notes at the end is bewildering. There's no way to know what are keys and what are values.. especially with the note-only item:

"just a secure note example","super secret secure note content here"

There's no indication of how this should be treated. The same goes for this one:

"website.com","Username","guyfawkes","Email","[email protected]","Password","3\9q,Fbr:4YR>Vh:Mg","Phone","123456789","URL","https://guy.fawkes.com","Security question","super secret question","Security answer","super secret answer","notes and stuff here"

The title is without a key at the beginning, And the key-value pattern stops when hitting the last item which is magically a note. I guess that last one follows the pattern specified in the header, but the note-only item above definitely does not.

Are we sure that all Enpass CSV exports follow the same pattern? I'd like to ignore the header and dive straight into the content.. which would only be possible if there are no other export options.

@kzshantonu Any way you could screen shot the export process?

[kzshantonu]

Hi,
Yes I do agree the format is pretty bad. It does follow the same pattern. the title, fieldname1, fieldvalue1, fieldname2, fieldvalue2,... is actually pretty great for custom field names (I have upto 21 fields in certain entries).

There's a TXT export format too that you might want to take a look at, example here - https://pastebin.com/raw/TcpktFQG

Here's a screenshot of the export process - http://i.imgur.com/6iwYzDO.png

[perry-mitchell]

Thanks @kzshantonu - I guess supporting the CSV first would work. The txt format is interesting as I think we could make a generic text import. Lists like:

key1: value1
key2: value2

and

key1=value1
key2=value2

are quite easily parsed, like ini files.

[kzshantonu]

I have to mention that any new lines in the notes area are new lines in the CSV too.
Example:

"Title","Field","Value","Field","Value",.........,"Note"
"website.com","Username","guyfawkes","Email","[email protected]","Password","_RG9wK9ZZ7>si#g}n-","URL","https://guy.fawkes","Security question","super secret question","Security answer","super secret answer","line1
line2
line3"
"regular note","note lines:
line2
line3
line4"

[perry-mitchell]

Good point. This affects the lastpass importer too.. need to fix that.

[NodokaMurmevent]

hello i don't know if it's the good place for this comment but if anybody want quit enpass for buttercup without wait you can use keepass for convert your file :
enpass -> export -> to TXT
Keepass -> create new database
Keepass -> import from enpass txt
Keepass -> save you database
And in buttercup you can import you new database

[Extarys]

@NodokaMurmevent trick still works. Thanks for that, finally liberated from Enpass. <3

[jautero]

Latest Enpass has support for .json format export, but I haven't looked into it.

[brunolellis]

As @jautero said, Enpass supports JSON format. I've exported one "facebook" entry just as an example: https://pastebin.com/raw/gX3RJdQt

I think "sensitive" attribute should be enough to identify password and sensitive fields.

[bigjdunham]

I found this guide really helpful. I was able to import an enpass .json into Buttercup using this work around. https://jsph.pl/migrating-from-enpass-to-keepass/