Does file importer ignore column headers?
I'm trying to help introduce a family member to 1password. She's using firefox (FF) and since 1P won't import from FF and she's not technical, I figured I'd do a quick test to save her from beating her head against the wall. So I made a test account in FF (because I don't normally use FF) and then I exported a CSV file from FF. In that file, I replaced the column names as described by:
https://support.1password.com/import-mac/
The 1P importer didn't recognize the column headers and instead used them as an account. So I ended up with a 1P account titled "Title" with username "Username" and so on. Actually, it was worse than that because FF exports the columns in a different order than the example document. After several more experiment failures, I deduced 1P was never going to recognize the column headers as the document describes so I swapped the columns to mimic the order in the example.
That worked. (Well, kinda. FF doesn't appear to have any concept of useful account titles but I guess there's nothing 1P can do about that. Or am I missing something?)
Either:
1) the 1P documentation needs to be fixed - not just for FF but for any CSV that was generated with columns in a different order than the example, or
2) the importer needs to be fixed so it recognizes the column headers, or
3) explain to me how to spell "Title" because evidently I'm not spelling it correctly, or
4) I've completely missed an easier method for FF users to import their accounts into 1P.
1Password Version: 7.8.5
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Comments
-
Your own example file is:
Title,Website,Username,Password,Notes,Member Number,Recovery Codes
Envato,https://account.envato.com,wendyaplsd,"H^4[q,yc-$dg",This is a login item with comma in the password,,
www.etsy.com,www.etsy.com,,aNfbg'>o(p4,This item does not have a title or username,,
Airbnb,https://www.airbnb.ca,wendy@appleseed.com,V#k#ESBRJ3,,,
Instagram,https://www.instagram.com,helloitswendy,"elz|^<_,7B",,,
MEC,https://www.mec.ca,wendythecanadian,h-pLM?fas*L,This item has a custom field recording a member number for this co-op,1234567,
GitLab,https://www.gitlab.com,wendycodes,SJcv;W*$S,This item has a custom field recording 2FA recovery codes,,"c584debad339c771
a9238ce3f9e96abc
925b98f25ec7ec76
df32e0d015285b36"After uploading, 1P shows the column headers have been interpreted as an account:
Not surprisingly, my own examples with correct column headers don't work either. Consider the following example CSV file:
Website,Username,Password,Title
fakeURL,fakeUN,fakePwd,fakeTitleImporting into 1P has this result:
Again, the column headers appear as an account. In addition, the fields don't follow the column headers. For example, the username field has "fakePwd".
This seems pretty compelling that your uploader is paying no attention to column headers or is looking for different column headers than your documentation describes.
0 -
I accept that the downloader has always used "strict column order" but the document certainly doesn't say that. To the contrary, the document says "The first line can be a list of the field names" but that's a silly statement if it's just going to treat the names as an account.
0 -
It’s an old guide, @clarino, and it’s had many hands touching it over the years. It’s never been very accurate, nor as clear as it could be.
Some importers will always treat a first row as a header, and will not add that line as data. I think the author’s intended meaning was that 1Password will always treat row 1 as data.
0 -
Indeed, that document is from the time where importing could only be done in the 1Password for Mac app. Now we also offer the option to import on the 1Password website, so that page might be a bit more accurate:
Move your data into your account on 1Password.com
0
