Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
3 years agoConvert DB from Passowords Plus to 1Password
I want to migrate to 1Password. Is there any advice on importing my Passwords Plus database into 1Password (to be used on WIN10/11, Android and iPad systems)? I have search the knowledge base for c...
MrC
3 years agoSuper Contributor
Hello @jsdyer
Sorry for the late reply, I didn't see your post until this evening.
You've asked good questions; let's see if my answers help.
As to your first question, the converter instructions advise / assume you place your export file on your Desktop. And the instructions also advise / assume you place the mrc-converter-suite folder on your Desktop. Your working directory will be within that converter suite folder, and the ..\ portion of the export file path means "one folder / directory up the folder tree" (e.g. the parent directory). You are welcome to use a full path to the export file on the command line. The suggested ..\pm_export path is just easier to type (and to write instructions).
The converter can most likely be customized to match your custom templates / fields. There are limitations when export data contains ambiguous data. This converter looks for field labels, counts them, and allows certain labels to trigger category detection. For example, the "website" category (which maps to 1Password's Login category) requires three labels, the usual suspects of Username, Password, and URL. This requirement is because the export data contains no indication of a record's category, only the field labels are available, and other categories use the exact same labels. The 'website' definition looks like this:
What's required is adjusting those labels (and possibly the counts - the 3 you see) to cause matches and category detection. There are additional definitions for each of the stock categories; more can be added, mapping the category and the fields to the relevant 1Password target records. If you've changed your Username field in your website category to be something unique across your records, such as Login Email, than it may suffice to change the Username pattern to match that label, and reduce the count from 3 to 1.
So if the converter can be customized to match a large percentage of your needs, then it's worth doing. It will save time, and more importantly, be less error-prone than manual data migration.
I'm happy to help get you a customized converter. It's usually best to start with the big wins, like Login records. Then, the process is a matter of small adjustments until you're satisfied with the results.
We can work online here or offline via email - your choice. Either way, don't share any of your sensitive data. Let me know what you'd like to do.