Have you tried the instructions in the Import data from another browser article?

No have option for "Opera" only IE and Chrome!

I found a solution for this problem. It is not so simple, but for me (and for many other people I think) is very important to have passwords imported.

1) Install OperaPassView.

2) Run OperaPassView and you will see all your passwords which are saved in Opera.

3) Select all entries (Ctrl + A) and click to save icon, fill your file name and select type "XML file".

4) Now there is the main problem – you have to transfer this file to different formating, because export from OperaPassView looks like this:

<opera_passwords_list>
<item>
<url>https://www.example1.com</url>
<password_type>Web Form</password_type>
<user_name>YouUserName</user_name>
<password>YourPassword</password>
<user_name_field>htmlFieldForName</user_name_field>
<password_field>htmlFieldForPassword</password_field>
<password_strength>Your password strange</password_strength>
</item>
<url>https://www.example2.com</url>
<password_type>Web Form</password_type>
<user_name>YouUserName2</user_name>
<password>YourPassword2</password>
<user_name_field>htmlFieldForName2</user_name_field>
<password_field>htmlFieldForPassword2</password_field>
<password_strength>Your password2 strange</password_strength>
</item>
.
.
.
</opera_passwords_list>

And we need format which looks like this:

<xml>
<entries ext="Password Exporter" extxmlversion="1.1" type="saved" encrypt="false">
<entry host="https://www.example1.com1" user="YouUserName" password="YourPassword" userFieldName="htmlFieldForName" passFieldName="htmlFieldForPassword" />
<entry host="https://www.example2.com1" user="YouUserName2" password="YourPassword2" userFieldName="htmlFieldForName2" passFieldName="htmlFieldForPassword2" />
.
.
.
</entries>
</xml>

So you have to open exported file and edit it:

1. As you can see you can remove lines containing <password_type> and lines containing <password_strength>.
2. After that you have to do some find and replace tricks in your favourite text editor to do this transformation, for example:

• replace all '<item>' by '<entry '
• replace all '</item>' by ' />'
• replace all '<url>' by 'host="'
• replace all </url> by '"'
• etc.

5) Save your new XML file.

6) In Firefox, install Password Exporter extension.

7) In Password Exporter extension click to import button and choose file you created.

8) You are done!

Note: if import fails, try to:

1. remove duplicate lines
2. check if your XML file is well-formed

For search-replace in Windows, I used "super sed" (ssed) - its zipped executable is here: "Super Sed" (ssed).

[Changed the link to the download page - please do not post direct download links - c]

The needed search-replace patterns (which were referred to as "etc." in the above post) are the following [You may want to save these patterns to a file and use it as a sed-script]:

s/<opera_passwords_list>/<xml><entries ext=\x22Password Exporter\x22 extxmlversion=\x221.1\x22 type=\x22saved\x22 encrypt=\x22false\x22>/

s/<\/opera_passwords_list>/<\/entries><\/xml>/

s/<item>/<entry/

s/<\/item>/\/>/

s/<url>/ host=\x22/

s/<\/url>/\x22/

s/<user_name>/ user=\x22/

s/<\/user_name>/\x22/

s/<password>/ password=\x22/

s/<\/password>/\x22/

s/<password_field>/ passFieldName=\x22/

s/<\/password_field>/\x22/

s/<user_name_field>/ userFieldName=\x22/

s/<\/user_name_field>/\x22/

Putting all together, in Windows "DOS" shell (cmd.exe) you can transform your OperaPassView-saved XML file (here: "wand.opv.xml") to a Mozilla-compatible XML file (here: "wand.moz.xml") using a few "find" commands to exclude unneeded lines, and the above sed-script (here: "o-to-m.sed") like this in one command line:

type wand.opv.xml | find /V "<password_type" | find /V "<password_strength>" | ssed -f "o-to-m.sed" > wand.moz.xml

Then you should be able to import your "wand.moz.xml" password file into Mozilla with the Password Exporter extension - except for some empty and duplicate passwords.

N.B. 1) Please note that OperaPassView and Opera Password Decryptor are incomplete, and may not extract all passwords. Both apps may make errors in retrieving passwords, for example, mix field names (e.g., the password field name with the actual password, or the actual password with another website location, etc.). So do NOT delete your original Opera wand.dat file, as you may still need to use Opera to login to some sites.

N.B. 2) You may also try the Opera wand.dat Passwords Retrieve Utility or the Unwand app - even though they do not have a fancy interface, but they retrieve all fields completely. Unfortunately, they cannot save the field in column format and/or export as CSV/XML, so you will have to copypaste by yourself. Nevertheless, they do not make any errors (although the field numbers and their interpretation are not obvious).

N.B. 3) The Mozilla Firefox Password Exporter extension does not handle properly duplicates, i.e., if you have more than one username/password fields within the same website (e.g., on different subpages). In these cases, only the first username/password combination will get imported. Check the importing errors (under View Details) if the number of imported passwords does not equal to the total number of passwords. You may work around by inserting manually "www." in front of some URLs, so that it would look like a different website and thus trick the importer app.

1) It is possible, but I have not found any missing password yet.

3) I don't agree. I have many sites with multiple login and everything works.

Hello Jakub!

I agree with your claim that multiple passwords work well - assuming that those passwords are for different users within the same subpage of a website (which is indeed the most usual case). However:

The raw (text) output of Unwand shows that there is a different number of fields per entry. Starting with a timestamp, fields include not only the username and password variable names, and the actual usernames and password, but may also hold additional field names and values, such as the page URL (required), the submit button name (optional), the subpage URL (optional), etc. Unfortunately, none of the wand.dat decrypting apps can interpret these fields. OperaPassView and Opera Password Decryptor output their XML with a fixed number of fields, thus you may easily run into problems with different situations.

The biggest problem is in cases when you have previously told Opera to NEVER remember passwords for certain sites. In these cases, the raw output has only 2 fields - the URL and an additional variable - and the wand.dat decrypting apps just start reading the next variables belonging already to the next entry! This messes up 2 entries at the same time. You may have been lucky in not using "Never remember password on this site" option - but if you did, you will have mashed up entries!

Additionally, the wand.dat decrypting apps do not take into account the second, optional URL for entries. This may however make difference between two separate username/password pairs on different subpages within the same website. Optional fields also do not make a difference between two entries, so they will be counted as duplicates at importing.

Another source of error is when you have the same username with multiple passwords saved for the same website. The Password Exporter extension imports only the first one (although it is usually the older one), although shows a warning indeed.

The exact importing logic should be starting with the Unwand raw output, in where:

• Entries are separated with a timestamp
• If the entry is an URL only, then it's a "never remember" case
• If the entry is an URL plus one field, then it's also a "never remember" case
• If the entry's URL starts with an asterisk (*), then a HTTP Basic Authentication username/password pair follows
• ...which may or may not be followed by a 32-character hex string as the last line of the entry
• For other cases, look for multiple URLs within an empty, take the fields after the second(=last) one
• If there is an odd number of fields, then skip the first, and handle the rest as variable name&value pairs
• If there is an even number of fields, then handle them as variable name&value pairs

Wow, thanks for this great analysis! Where did you get so much knowledges about wand.dat? ;)

But I have to say that I hope that I won't have to use it. :) As I said, everything looks like it works, but if I have any problems, your text will help me, so again – thank you very much for this summary!

It's just a sort of "reverse engineering", based on the cases from my ~400 wand passwords :)

I have had plans to implement a fully correct importer logic in either Perl or Excel formulas, but unfortunately it looks impossible to implement automatically and 100% correctly. Although most websites store the "userFieldName"-"user" and "passFieldName"-"password" pairs as first four variables, but not all of them do this. Importing could work if Firefox stored all the variable pairs, but it only attempts to store only these two pairs for logging in - if they are not in the beginning, then it is impossible to guess which variable pairs to use.

Eventually, I imported the raw Unwand output to a huge Excel sheet and did the above logical steps manually... it took many hours, but now I have fully correct passwords in Firefox.

This program helped me reveal all saved passwords from my Opera 18 browser. http://www.top-password.com/opera-password-recovery.html

It should also work for you. Good luck!

See also http://www.nirsoft.net/utils/opera_password_recovery.html

Please read my first post... ;) Only with OperaPassView you can't transfer passwords from Opera to Firefox.