pimport(1)

✨ pimport(1) ✨

okay bestie, you found the manual page for pimport(1) and it's literally the swiss army knife of password importers. no cap. πŸ’…


🌸 NAME 🌸

pimport β€” a passwords importer swiss army knife. that's the whole name, periodt. πŸŽ€


✨ SYNOPSIS ✨

pimport [options...] dst src [src]

πŸ’– DESCRIPTION πŸ’–

okay so pimport is a passwords importer swiss army knife that lets you import your password database to a password store repository conveniently. it natively supports import from 62 password managers, and export to 8 destination password managers. more manager support can easily be added. slay. πŸ’…

passwords are imported into the existing default password store, so bestie, the password store must have been initialized before. no initialized store = no import, periodt. πŸ›‘

by default, pass imports entries at the root of the password store and only keeps the main data (password, login, email, URL, group). this behaviour can be changed using the provided options. it handles duplicates and imports OTP secret. πŸ”


πŸŽ€ COMMAND πŸŽ€

pimport [options...] dst src [src]
  • dst β€” refer to one of the supported destination password managers to which you want to export your data. the complete list of supported destination managers can be found in the section SUPPORTED DESTINATION MANAGERS. it can also be found with pimport --list-exporters. πŸ’–
  • src [src] β€” can refer to two things: the path to the data to import or to the password manager name followed by the path to the data to import. if only the path to the data to import is given, pass-import automatically detects the data format to import. the complete list of supported managers can be found in the section SUPPORTED MANAGERS. it can also be found with pimport --list-importers. ✨

now the options, bestie:

  • --out=<prefix>, or -o <prefix> β€” provide a path where the destination password manager lives. it can be a file, a directory, or even a login depending on the manager. πŸ“
  • --root=<path>, -r <path> and --path=<path>, -p <path> β€” specific root source and destination directory to use in the password store. where --root refer to the source repository and will only import the password from a specific subfolder. --path refer to the destination repository and will import the passwords to a specific subfolder. πŸ—‚οΈ
  • --key=<path>, -k <path> β€” if required by a password manager, a key file can be given using the --key or -k option along with the path to the keyfile to use. πŸ”‘
  • --all, -a β€” conserve and import all the data present in the backup file. otherwise, only title, password, login, URL, comments, and group data are imported. πŸ’―
  • --force, -f β€” the import process will overwrite existing password entry if it already exists. πŸ”₯
  • --clean, -c β€” clean the password path in order to be more command line friendly. 🧼
  • --convert, -C β€” convert the invalid characters present in the paths before import. invalid characters for both Windows and Unix systems are supported. the default separator replaces the invalid characters: - πŸ”„
  • --sep=<char> β€” provide a character of replacement for the path separator. default: - ✨
  • --del=<char> β€” provide an alternative CSV delimiter character. default: , πŸ“
  • --cols=<char> β€” set the expected CSV columns to map columns to credential attributes. only used for the generic csv importer. πŸ“Š
  • --config=<path> β€” pass-import will consider this config file instead of the default one .import. βš™οΈ
  • --list-importers, -l β€” print the list of the available source password manager. with the verbose option (-v) it provides the python class name to use to be given as src. it can be useful to bypass the automatic format detection. also support the quiet option (-q). πŸ“‹
  • --list-exporters, -e β€” print the list of the available destination password manager. support the quiet option (-q). πŸ“€
  • --help, -h β€” print the program usage. if the option is specified along with an argument and if this argument is a supported password manager, prints usage for this manager. πŸ†˜
  • --verbose, -v β€” be more verbose. this option can be specified multiple times to set the verbosity level. πŸ—£οΈ
  • --quiet, -q β€” be quiet 🀫

🌈 BASIC USAGE 🌈

to import password from any supported password manager simply run:

pimport <new_pm> path/to/passwords --out path/to/destination/pm

if pimport is not able to detect the format, you need to provide the password manager you want to import data from:

pimport <new_pm> <former_pm> path/to/passwords --out path/to/destination/pm

if you want to import data to a pass, run:

pass import <pm> path/to/passwords

πŸ”₯ EXAMPLES πŸ”₯

πŸ’– Import Lastpass file to a keepass kdbx db

pimport keepass lastpass.csv --out keepass.kdbx
(*) Importing passwords from lastpass to keepass
 .  Passwords imported from: lastpass.csv
 .  Passwords exported to: keepass.kdbx
 .  Number of password imported: 6
 .  Passwords imported:
          Social/mastodon.social
          Social/twitter.com
          Social/news.ycombinator.com
          Servers/ovh.com/bynbyjhqjz
          Servers/ovh.com/jsdkyvbwjn
          Bank/aib

πŸ’– Import a password store to a CSV file

pimport csv ~/.password-store --out file.csv`

(yeah bestie, that backtick at the end is in the original, we don't make the rules πŸ’…)

πŸ’– Import passwords from keepass to bitwarden in a subfolder

pimport bitwarden  keepass.kdbx --out <login> -p Import/
(*) Importing passwords from keepass to bitwarden
 .  Passwords imported from: keepass.kdbx
 .  Passwords exported to: <login>
 .  Root path: Import
 .  Number of password imported: 6
 .  Passwords imported:
          Import/Social/mastodon.social
          Import/Social/twitter.com
          Import/Social/news.ycombinator.com
          Import/Servers/ovh.com/bynbyjhqjz
          Import/Servers/ovh.com/jsdkyvbwjn
          Import/Bank/aib

πŸ’– Other examples

  • if the manager is not correctly detected, you can pass it at source argument
pimport pass dashlane dashlane.csv --out ~/.password-store
  • import NetworkManager password on default dir
pimport pass networkmanager --out ~/.password-store
  • import a NetworkManager INI file
pimport pass nm.ini --out ~/.password-store
  • import a One password 1PIF
pimport pass 1password.1pif
  • import a One password CSV
pimport pass 1password.csv
  • import a Passman JSON file
pimport pass passman.json
  • import Lastpass file to a keepass db
pimport keepass lastpass.csv --out keepass.kdbx
  • import a password store to a CSV file
pimport csv ~/.password-store --out file.csv

πŸ”’ SECURITY CONSIDERATION πŸ”’

πŸ›‘οΈ Direct import

passwords should not be written in plain text form on the drive. therefore, when possible, you should import it directly from the encrypted data. for instance, with an encrypted keepass database:

pimport pass keepass file.kdbx --out ~/.password-store

🧹 Secure erasure

otherwise, if your password manager does not support it, you should take care of securely removing the plain text password database:

pimport keepass lastpass data.csv
shred -u data.csv

πŸ” Encrypted file

alternatively, pimport can decrypt gpg encrypted file before importing it. for example:

pimport keepass lastpass lastpass.csv.gpg

πŸ›‘οΈ Mandatory Access Control (MAC)

AppArmor profiles for pimport are available in apparmor.d. if your distribution support AppArmor, you can clone the repository and run:

make
sudo make install pass-import

to only install these apparmor security profiles.

🌐 Network

pimport only needs to establish network connection to support cloud based password manager. if you do not use these importers you can ensure pimport is not using the network by removing the network rules in the apparmor profile of pass-import.


βš™οΈ CONFIGURATION FILE βš™οΈ

some configurations can be read from a configuration file called .import if it is present at the root of the password repository. the configuration read from this file will be overwritten by their corresponding command-line option if present.

example of the .import configuration file for the default password repository

zx2c4@laptop ~ $ cat .import

---

# Separator string
separator: '-'

# The list of string that should be replaced by other string. Only activated
# if the `clean` option is enabled.
cleans:
  ' ': '-'
  '&': 'and'

# The list of protocol. To be removed from the title.
protocols:
  - http://

# The list of invalid characters. Replaced by the separator.
invalids:
  - '<'
  - '>'

πŸ‘‘ SUPPORTED DESTINATION MANAGERS πŸ‘‘

πŸ“ csv (csv)

you should use the –cols option to map columns to credential attributes. the recognized column names by pass-import are the following: `title', `password', `login', `email', `url', `comments', `otpauth', `group' title and group field are used to generate the password path. if you have otp data, they should be named as otpauth. these are the standard field names. you can add any other field you want.

command: pimport csv src [src]

πŸ¦‹ gopass (gopass)

website: https://www.gopass.pw/

command: pimport gopass src [src]

πŸ”‘ keepass (kdbx)

website: https://www.keepass.info

command: pimport keepass src [src]

πŸ”‘ keepassx2 (kdbx)

website: https://www.keepassx.org

command: pimport keepassx2 src [src]

πŸ”‘ keepassxc (kdbx)

website: https://keepassxc.org

command: pimport keepassxc src [src]

πŸ”’ lastpass (cli)

website: https://www.lastpass.com

command: pimport lastpass src [src]

πŸŽ€ pass (pass)

website: https://passwordstore.org

command: pimport pass src [src]

✨ sphinx

website: https://github.com/stef/pwdsphinx/

command: pimport sphinx src [src]

🌈 SUPPORTED SOURCE MANAGERS 🌈

Okay bestie, this is the whole roster of source managers you can import from. I kept every website, every export path, and every command exactly as it should be, no cap. Scroll responsibly, hydrate, and don't skip a single one. πŸ’–


πŸ’– 1password (csv) v8

πŸ’– 1password (1pif) v4

πŸ’– 1password (csv) v4

πŸ’– 1password (csv) v6

✨ aegis (json)

✨ aegis (json)

πŸŽ€ andotp (json)

πŸ“ apple-keychain (keychain)

πŸ¦‹ bitwarden (csv)

  • Website: https://bitwarden.com
  • Export: go to Tools> Export Vault> File Format: .csv
  • Command: pass import bitwarden file.csv

πŸ¦‹ bitwarden (csv)

  • Website: https://bitwarden.com
  • Export: go to Tools> Export Vault> File Format: .csv
  • Command: pass import bitwarden file.csv

πŸ¦‹ bitwarden (json)

  • Website: https://bitwarden.com
  • Export: go to Tools> Export Vault> File Format: .json
  • Command: pass import bitwarden file.json

πŸ¦‹ bitwarden (json)

  • Website: https://bitwarden.com
  • Export: go to Tools> Export Vault> File Format: .json
  • Command: pass import bitwarden file.json

🌸 blur (json)

  • Website: https://abine.com
  • Export: go to Settings: Export Data: Export Blur Data
  • Command: pass import blur file.json

🌸 blur (csv)

  • Website: https://abine.com
  • Export: go to Settings: Export Data: Export CSV: Accounts: Export CSV
  • Command: pass import blur file.csv

πŸ’… buttercup (csv)

  • Website: https://buttercup.pw
  • Export: go to File > Export > Export File to CSV
  • Command: pass import buttercup file.csv

🌈 chrome (csv)

🌈 chrome (csv)

πŸ’œ clipperz (html)

  • Website: https://clipperz.is
  • Export: go to Settings > Data > Export: HTML + JSON
  • Command: pass import clipperz file.html

🧚 csv (csv)

Okay bestie, this one is special. You should use the –cols option to map columns to credential attributes. The recognized column names by pass-import are the following: `title', `password', `login', `email', `url', `comments', `otpauth', `group' title and group field are used to generate the password path. If you have otp data, they should be named as otpauth. These are the standard field names. You can add any other field you want.

  • Export: nothing to do, bestie
  • Command:
pass import csv file.csv –cols `url,login,,password'

πŸ“ dashlane (csv)

  • Website: https://www.dashlane.com
  • Export: go to File > Export > Unsecured Archive in CSV
  • Command: pass import dashlane file.csv

πŸ“ dashlane (json)

  • Website: https://www.dashlane.com
  • Export: go to File > Export > Unsecured Archive in JSON
  • Command: pass import dashlane file.json

πŸ”₯ encryptr (csv)

πŸ‘‘ enpass (json) v6

  • Website: https://www.enpass.io
  • Export: go to Menu > File > Export > As JSON
  • Command: pass import enpass file.json

πŸ‘‘ enpass (csv)

  • Website: https://www.enpass.io
  • Export: go to File > Export > As CSV
  • Command: pass import enpass file.csv

🦊 firefox (csv)

🦊 firefox (csv)

πŸ’€ fpm (xml)

πŸŽ€ freeotp+ (json)

🐧 gnome (libsecret)

  • Website: https://wiki.gnome.org/Projects/GnomeKeyring
  • Note: You can provide a gnome-keyring collection label to import. It can be empty to import all collections.
  • Export: nothing to do, bestie
  • Command: pass import gnome-keyring

🐧 gnome-auth (json)

🫢 gopass (gopass)

🦍 gorilla (csv)

πŸ’€ kedpm (xml)

πŸ” keepass (kdbx)

πŸ” keepass (csv)

πŸ” keepass (xml)

πŸ”‘ keepassx (xml)

  • Website: https://www.keepassx.org
  • Export: go to File > Export to > Keepass XML File
  • Command: pass import keepassx file.xml

πŸ”‘ keepassx2 (kdbx)

πŸ”‘ keepassx2 (csv)

πŸ”‘ keepassxc (kdbx)

πŸ”‘ keepassxc (csv)

  • Website: https://keepassxc.org
  • Export: go to Database > Export to CSV File
  • Command: pass import keepassxc file.csv

πŸ‘‘ keeper (csv)

πŸ•ΆοΈ lastpass (cli)

πŸ•ΆοΈ lastpass (csv)

  • Website: https://www.lastpass.com
  • Export: go to More Options > Advanced > Export
  • Command: pass import lastpass file.csv

πŸ“ myki (csv)

🌐 network-manager (nm)

───────────────────────────────────
- From directory of ini file: pass
import networkmanager dir/.
- From ini file: pass import
networkmanager file.ini.
  • Export: Also support specific networkmanager dir and ini file
  • Command: pass import networkmanager

🧊 nordpass (csv)

  • Website: https://nordpass.com/
  • Export: go to Settings > Export Items
  • Command: pass import nordpass file.csv

πŸ”’ padlock (csv)

  • Website: https://padloc.app
  • Export: go to Settings > Export Data and copy text into a .csv file
  • Command: pass import padlock file.csv

🫢 pass (pass)

🧜 passman (csv)

  • Website: https://passman.cc
  • Export: go to Settings > Export credentials > Export type: CSV
  • Command: pass import passman file.csv

🧜 passman (json)

  • Website: https://passman.cc
  • Export: go to Settings > Export credentials > Export type: JSON
  • Command: pass import passman file.json

πŸ“¦ passpack (csv)

  • Website: https://www.passpack.com
  • Export: go to Settings > Export > Save to CSV
  • Command: pass import passpack file.csv

πŸ₯§ passpie (yaml) v1.0

πŸ” pwsafe (xml)

  • Website: https://pwsafe.org
  • Export: go to File > Export To > XML Format
  • Command: pass import pwsafe file.xml

πŸ‘οΈ revelation (xml)

πŸ€– roboform (csv)

  • Website: https://www.roboform.com
  • Export: go to Roboform > Options > Data & Sync > Export To: CSV file
  • Command: pass import roboform file.csv

☁️ safeincloud (csv)

πŸ›‘οΈ saferpass (csv)

  • Website: https://saferpass.net
  • Export: go to Settings > Export Data: Export data
  • Command: pass import saferpass file.csv

πŸ“š upm (csv)

☁️ zoho (csv)

  • Website: https://www.zoho.com/vault
  • Export: go to Tools > Export Secrets: Zoho Vault Format CSV
  • Command: pass import zoho file.csv

☁️ zoho (csv)

  • Website: https://www.zoho.com/vault
  • Export: go to Tools > Export Secrets: Zoho Vault Format CSV
  • Command: pass import zoho file.csv

πŸ‘€ SEE ALSO

pass(1), pass-tomb(1), pass-update(1), pass-otp(1), pimport(1), pass-audit(1)


πŸ’– AUTHORS

pimport was written by Alexandre Pujol (alexandre@pujol.io).


This page is from February 2024 and it's for pimport(1) β€” mwah, bestie. Go import your little heart out. πŸ’…βœ¨

πŸ“¦ where this page comes from