Direct import from lastpass is failing. Tells me to send diagnostic. I did yesterday but nothing.

The lastpass importer will create a record Imported Unknown Data which includes several sections for lists of field values that have not yet been mapped or appropriately ignored. One of those sections is labeled as NEVR, and includes a list of domains. These are likely never-fill domains.

There are also other sections such as LPFF, which is LastPass Form Fill (these values get mapped into corresponding Identity, Bank Account and Credit card entries), and the FFCF section is Form Fill Custom Fields (these do not yet seem to be mapped into any records).

Thanks for letting me know, lesster - Please let us know if you run into any other troubles.

Sorry, I deleted the weird item, didn't want it to confuse my non-techie family member. I'd do the import again, but I've already verified the imported data, and spent lots of time on this, I'm going to have to pass.

Hello again lesster,

Happy to hear the direct import worked well for your family members.

With regard to that one imported item that included extra URL/domain names in fields, where they same across each extra field and are those fields directly related to data from the original item?

This is something I've personally not seen reported before. If you see this behaviour with any other items could you let us know and send along a screenshot? Here is a handy guide on how to take screenshots on different platforms: https://www.take-a-screenshot.org - When sending a screenshot, please be sure to redact any personal or private information. Thanks!

FYI, direct import from LP worked great for my family member's data with the current 1P8 beta.
I checked that all entries came over, verified the data details on some, looks good.

Only weird thing was one entry with many many unknown fields, whose values were all or at least mostly URLs or domain names.
Does that ring a bell with anyone?

Happy to help, lesster. 😊

Thanks, I figured, good to confirm.

Hello lesster,

Thank for getting back to me with this question. Regardless of the version you are using, your data can be pulled from 1Password.com (or .ca/.eu) and shouldn't cause any concerns.

If you would like to revert back to a stable version, you can return to Production by following the steps here to use 1Password beta releases. 1Password will then return to the stable version when it surpasses the beta version currently installed.

Provided all of your data is up-to-date and present on 1Password.com, should like you like to return to a production version immediately, you can follow this guide to learn how to reset the 1Password app on a specific device. Signing in to the app anew, will sync that data to the app.

I hope this information helps, but we'll be here to help if you have more questions.

ag_mike_d, is there any concern that if we install a 1P beta, our data will be "upgraded" in a way that makes it incompatible with the stable release?

@olderman and others working with unencrypted password files on Windows:
The best thing isn't just to empty the recycle bin, it's to use an actual secure deletion tool, for instance Microsoft's https://learn.microsoft.com/en-us/sysinternals/downloads/sdelete.
Those sorts of programs overwrite the bits on disk with random garbage, multiple times, making it virtually impossible to recover, even with data forensics tools.
Probably not an actual issue for most of us, but it's easy.