You can order the columns how you want, label them (according to the README.pdf) and identify which of email / login columns should go into your Login's username field, and have the other placed into a custom-named field. If you want a more robust conversion of your CSV export, use the csv converter in the converter suite. This is what happens when you have a Login created by the 1Password extension, for example. Place in the "username" field whatever you'd use when you log into the site. A "username" and an "email" are often the same, and email addresses have become the preferred login credential used by most sites. Correct in terms of form-fill w/Logins.The importer is looking for a specific format. You cannot change the Dashlane CSV export structure and have the importer work (since the file is now no longer a "Dashlane" export - its your own CSV).Furthermore, the CSV must be exported as UTF-8. Be sure to follow the instructions in the linked article if you are going to use CSV. The "imported everything as one field" also implies a formatting problem. The columns in a CSV import are defined in the How to create a 1Password compatible CSV file article. You do need all items to be the same in the CSV (e.g. No need to remove the Notes field from a CSV (in case that's what you meant) for a CSV import using the CSV importer of the native app.I believe is doing a best-attempt effort, but when the CSV is broken, I don't think it handles the situation well. I've commented in several threads here about Dashlane's CSV export issues. Very nice info This would indicate there's a formatting issue with the Dashlane CSV export. I am currently merging whatever logins don't have separate emails and usernames, but the ones that do, I cannot afford to remove, as those are essential to the accounts. Thus, the CSV having a field for each, makes it so that it bumps the password and replaces it with the email field. I have found that 1Password does not distinguish (or add a field) between a username, an email, and credentials that have both.I changed the CSV format to a legacy version, and now my emails are all in the password fields when being imported (still in the MacOS version, as the web import does not work.It imported everything as one field and exposed all my passwords. I modified the CSV to remove notes and identity info, and used the Mac client to import.I exported a CSV from MacOS and input that into the Web client of 1Password and received the error about no importable items being found.Personal 1Password with whatever the latest versions are for each of those.
0 kommentar(er)
