Rekey

Move from mSecure to Bitwarden

Bitwarden has its own mSecure importer, so the CSV goes in as it is. What it does with the file is worth knowing before you delete mSecure: a few kinds of data change shape on the way.

Checked November 5, 2026

A key ring with labelled keys, one key being cut again E-MAIL 1 change first

Open your mSecure export

Two ways in

The two paths from mSecure to Bitwarden (checked November 5, 2026)
Bitwarden’s mSecure (csv) importRekey’s Bitwarden (json) file
LoginsWebsite, username, password, noteSame, plus every other field by name
Second password, PIN, security answers on a loginNot carried overCustom fields (secrets hidden)
Credit cardsCardsCards, extra fields kept
Bank accounts, notes, licencesSecure notes, fields as note textSecure notes, fields as named fields
One-time password secretsNot read as TOTPTOTP field (otpauth link)
TagsEach tag a folderFirst tag the folder, others listed in the note
PriceFreeRekey Pro, $8 once

The left column comes from Bitwarden’s importer code (linked below): for a login it reads only the website, username and password columns; a record that is not a login or a card becomes a note with its values pasted in.

Import the Rekey file

  1. Export from mSecure on a Mac (File > Export > CSV) or Windows (Settings > Backups); see export to CSV.
  2. Open it in Rekey and choose Bitwarden and KeePassXC file. You get bitwarden.json.
  3. In the Bitwarden web app, select Tools > Import, choose the vault, set the file format to Bitwarden (json), choose the file and import.
  4. Check a few items (a card, a login with a PIN), then delete the JSON file and the mSecure CSV and empty the trash.

Open my mSecure exportSee every record before you import it.

Bitwarden’s own importer is fine when

Your vault is mostly plain logins with a website, a username and a password, and you do not use mSecure’s extra fields. Then the free path is enough: choose mSecure (csv) in Bitwarden and skip the conversion. Rekey still helps afterwards with the order to change those passwords in.

Changing the passwords

mSecure’s November 3, 2026 notice asked users to protect everything stored in the app (Malwarebytes). The imported passwords are the old ones, so they still need changing. Rekey lists the logins with e-mail and money first and shows which ones share a password; see what to change first.

Questions

Does Bitwarden import mSecure directly?

Yes. In the Bitwarden web app: Tools > Import, choose mSecure (csv) as the file format, pick the file. Bitwarden’s importer is open source; it reads logins, credit cards and the rest as secure notes.

What does the built-in importer change?

In Bitwarden’s code, a login keeps its website, username, password and note; other fields on a login (a second password, a PIN, security questions) are not carried over. Records that are neither logins nor cards become secure notes with their fields pasted into the note text. Each mSecure tag becomes a Bitwarden folder.

What does the Rekey file do differently?

It is a Bitwarden JSON export: every extra field stays a named custom field (secrets as hidden fields), cards stay cards with number, expiry, code and name, one-time password secrets go into the TOTP field, and the first tag becomes the folder. It is a Pro feature.

Can KeePassXC use the same file?

Yes. KeePassXC imports Bitwarden .json files (Database > Import, then Bitwarden), as its user guide lists.

Is the JSON file encrypted?

No, it is plain text, like the mSecure CSV. Import it, check the vault, then delete both files and empty the trash.

Sources

Checked November 5, 2026. Rekey is an independent tool made by Peak Apps Studio. It is not affiliated with mSecure or mSeven Software, nor with Apple, Google, 1Password or Bitwarden.