Import and export Coming soon

Changing password manager doesn’t mean starting from scratch

Your company’s passwords are already somewhere: in another manager, in the browser, on someone’s phone. Kamzan Pass gathers them, tells you what was left out and doesn’t lock you in.

A serious import also says what didn’t get in

Officina Ferrero had logins saved in Chrome and a few codes on Google Authenticator. It chooses the file and reads the preview: how many items get in, how many are already there, how many stay out and why. The file is read in the browser, and only already-encrypted items reach the server. At the end Kamzan Pass reminds you to delete it: it contains passwords in plain text.

How it works

  1. Choose the file

    From “Import and export”, choose the file or the Google Authenticator QR, and if you belong to shared vaults, say where to save the items.

  2. Read the preview

    You see how many items get in and how many are already there: “Skip items already present” avoids duplicates. Excluded ones are listed with the reason, such as counter-based codes.

  3. Import and delete the file

    The result repeats what was left out. Then delete the file from the disk and the trash: its job is done, and it holds passwords in plain text.

Easy to get in, easy to leave: the passwords stay the company’s.

What you can do

  • Where they come from

    Bitwarden with the unencrypted .json, Chrome, Edge, Brave and Firefox with the .csv, Google Authenticator with the “Transfer accounts” QR, and encrypted Kamzan Pass files.

  • The file stays on your device

    It is read in the browser and not uploaded. Only already-encrypted items reach the server, like every other Kamzan Pass item.

  • Folders aren’t lost

    Bitwarden folders don’t become vaults, but they can arrive as labels. In a shared vault all members see those labels, folder names included.

  • Encrypted export

    A .kpass file protected by a password you choose on the spot, different from the master password. It can’t be recovered: keep the file and password in different places.

  • Plain-text export

    JSON or CSV to move to another program, readable by anyone who opens the file. CSV carries logins only. The company can switch it off with a rule, and the trash isn’t exported.

  • Who can do it

    It takes the “Import and export” privilege, and every export asks for the master password. One limit remains: anyone who can read an item can always copy it, and that can’t be prevented.

Frequently asked questions

Can an encrypted Bitwarden export be imported?

Not for now: you need the unencrypted .json format. Export again from Bitwarden choosing that format, and delete the file once the import is done.

What isn’t imported?

For example counter-based codes (HOTP), items that were in the trash and addresses that aren’t websites. The preview lists every exclusion with its reason, and the result repeats it.

Does the company know if someone exports?

The device declares it in the log, but it is a declaration: a modified client can stay silent. An export can’t be prevented for someone who can read, nor reliably recorded.

What if I lose the encrypted file’s password?

The file can no longer be opened: that password can’t be recovered, even with the master password. That’s why Kamzan Pass asks you to keep file and password in different places.

Want to see it before it arrives?

We show you Kamzan Pass on a test vault: how a password is shared, what happens when someone leaves the company and what the server doesn’t see. Half an hour, no strings attached.

Request a demo