Import and Exporting Data
Commands for importing and exporting vault records, folders and teams permissions.

Commands

Keeper Command Reference

Whether using the interactive shell, CLI or JSON config file, Keeper supports the following commands, each command supports additional parameters and options.
To get help on a particular command, run:
help <command>
Import and Export Commands
Command
Explanation
import
Import data from a local file or other password managers
export
Export vault records
download-membership
Download shared folder memberships

import command

Command: import
Detail: Import data to Keeper from a local file or other password managers.
If a record from the file already exists, it will not be added.
Keeper commander supports direct imports from LastPass using your LastPass email and password, no export file needed! See LastPass Import documentation for more details.
Parameters:
Path of file to import from.
*note: in file paths, backslash "\" needs to be escaped by using two in a row "\\"
Switches:
--format <{json, csv, keepass, lastpass, myki, manageengine, 1password}> file format (required)
  • myki import requires Commander v16.5.11+
  • 1password requires Commander v16.7.0+
--folder <FOLDER PATH OR UID> import into a specified folder
-s, --shared import folders from file as shared folders
-p, --permissions <PERMISSIONS> default shared folder permissions if importing folders as shared
folders
  • U - manage users permission granted
  • R - manage records permission granted
  • E - edit records permission granted
  • S - share permission granted
  • A - all permissions granted
  • N - no permissions granted
-dc, --display-csv show instructions for importing using the CSV format
-dj, --display-json show instruction for importing using JSON format
--record-type <RECORD TYPE NAME> import all records as the specified type (requires v16.5.7+)
Examples:
import C:\\records.csv --format csv
import C:\\records.csv --format csv --folder social
import C:\\shared-records.json --format json -s -p A
import C:\\lastpass\\passwords.csv --format lastpass
import --display-csv
import C:\\records.csv --format csv --record-type login
  1. 1.
    Import records from a "records" CSV file into the vault
  2. 2.
    Import records from a "records" CSV file into the "social" folder
  3. 3.
    Import records from a "shared-records" json file, importing and folders as shared folders with all permissions granted
  4. 4.
    Import passwords from a Lastpass export file
  5. 5.
    Show instructions and example for importing using CSV
  6. 6.
    Import records from a "records" CSV file as login type records

export command

Command: export
Detail: Export vault data to a file or the console
Parameters:
File name to export to, or nothing to export to console stdout
Switches:
--format <{json, csv, keepass}> file format (required)
*note: keepass format cannot be exported to the console
--max-size <SIZE> maximum size of file attachment to export
  • format: number followed by "K","M","G" (Kilobyte, Megabyte, Gigabyte respectfully)
  • e.g. "100k" , "10M" , "2G"
-kp, --keepass-file-password <PASSWORD> if exporting in keepass format, set the file's password
--folder <FOLDER NAME OR UID> select a folder as the export source
Examples:
export my-vault.csv --format csv
export --format json --max-size 10K
export keeper.kdbx --format keepass -kp 9EqfhCqbym-w
export socials.csv --format csv --folder "Socials"
  1. 1.
    Export the vault in CSV format to a file named "my-vault"
  2. 2.
    Export the vault in JSON format to the console, ignoring any file attachments over 10 Kilobytes
  3. 3.
    Export the vault in keepass format to a file named "keeper" and set the file's password
  4. 4.
    Export the records in the "Socials" folder

download-membership command

Command: download-membership
Detail: Download shared folder membership to a JSON file.
This command will create a JSON shared folder file based on the sharing permissions in a Keeper or remote LastPass vault. This file can then be used for subsequently sharing folders with Keeper users through the import command.
download-membership --source=lastpass
or
download-membership --source=keeper

Detailed Instructions

Importing Records into Keeper

To import records into your vault, use the import command. Supported import formats:
JSON import files can contain records, folders, subfolders, shared folders, default folder permissions and user/team permissions. CSV import files contain records, folders, subfolders, shared folders and default shared folder permissions. Keepass files will transfer records, file attachments, folders and subfolders. Option exists to make all folders as shared folders. File attachments are supported in both import and export with Keepass however they are limited to 1MB for each file based on Keepass' structure. LastPass import will transfer the vault passwords directly to Keeper retaining the folder structure. See LastPass Import documentation for more details.

JSON Record Import

Below is a JSON import file with 2 records. The first record is added to a folder called "My Servers". The second record is added to "My Servers" and also added to a shared folder called "Shared Servers".
The import file example below is an array of record objects which can import into private folders and shared folders. Note in the example that the Facebook record contains a TOTP seed which will render on the Vault user interface and Commander CLI.
{
"records": [{
"title":"Google",
"folders": [
{
"folder": "My Websites\\Online"
}
],
"login": "testing",
"password": "lk4j139sk4j",
"login_url": "https://google.com",
"notes": "These are some notes.",
"custom_fields": {"Favorite Food":"Cheetos"}
},
{
"title":"Facebook",
"folders": [
{
"folder": "Social Media"
},
{
"shared_folder": "Shared Social",
"can_edit": false,
"can_share": false
}
],
"login": "[email protected]",
"password": "123123123123",
"login_url": "https://facebook.com",
"notes": "This is our corporate shared record.",
"custom_fields": {
"Facebook Application ID":"ABC12345",
"TFC:Keeper": "otpauth://totp/Amazon:[email protected]?secret=JBSWY3DPEHPK3PXP&issuer=Amazon&algorithm=SHA1&digits=6&period=30"}
}]
}
Another example below first creates shared folders that are shared to users and teams, then imports records into the shared folders. The format of the file is slightly different and allows you to separate the creation of shared folder objects and records:
{
"shared_folders": [
{
"path": "My Customer 1",
"manage_users": true,
"manage_records": true,
"can_edit": true,
"can_share": true,
"permissions": [
{
"uid": "kVM96KGEoGxhskZoSTd_jw",
"manage_users": true,
"manage_records": true
},
{
"name": "[email protected]",
"manage_users": true,
"manage_records": true
}
]
},
{
"path": "Testing\\My Customer 2",
"manage_users": true,
"manage_records": true,
"can_edit": true,
"can_share": true,
"permissions": [
{
"uid": "ih1CggiQ-3ENXcn4G0sl-g",
"manage_users": true,
"manage_records": true
},
{
"name": "[email protected]",
"manage_users": true,
"manage_records": true
}
]
}
],
"records": [
{
"title": "Bank Account 1",
"login": "customer1234",
"password": "4813fJDHF4239fdk",
"login_url": "https://chase.com",
"notes": "These are some notes.",
"custom_fields": {
"Account Number": "123-456-789"
},
"folders": [
{
"folder": "Optional Private Folder 1"
}
]
},
{
"title": "Bank Account 2",
"login": "mybankusername",
"password": "w4k4k193f$^&@#*%2",
"login_url": "https://amex.com",
"notes": "Some great information here.",
"custom_fields": {
"Security Group": "Public",
"IP Address": "12.45.67.8"
},
"folders": [
{
"folder": "Optional Private Folder 1"
},
{
"shared_folder": "My Customer 1",
"can_edit": true,
"can_share": true
}
]
}
]
}
The format must be strict JSON or it will fail parsing. To import this file:
$ keeper import --format=json import.json
There are more complex import file examples that supports shared folders, folder permissions, user permissions and team permissions located in the sample_data/ folder. To import the sample JSON file into your vault, type this command:
$ keeper import --format=json sample_data/import.json.txt
The sample file contains "permissions" objects that contain email address or team names. If the email or team name exists in your Keeper enterprise account, they will be added to the shared folder, otherwise the information is ignored.

CSV Record Import

Keeper supports .csv text file import using comma delimited fields.
File Format: Folder,Title,Login,Password,Website Address,Notes,Shared Folder,Custom Fields
  • To specify subfolders, use backslash "\" between folder names
  • To set shared folder permission on the record, use the #edit or #reshare tags as seen below
  • Enclose fields in quotes for multi-line or special characters
  • Ensure files are UTF-8 encoded for support of international or double-byte characters
Below is an example csv file that showcases several import features including personal folders, shared folders, subfolders, special characters and multi-line fields.
Business,Twitter,[email protected],"a bad password",https://twitter.com,Some interesting notes!,,API Key,"131939-AAAEKJLE-491231$##%!",Date Created,2018-04-02
Subfolder1,Twitter,[email protected],xwVnk0hfJmd2M$2l4shGF#p,https://twitter.com,,Social Media\Customer1#edit#reshare
Subfolder2,Facebook,[email protected],TycWyxodkQw4IrX9VFxj8F8,https://facebook.com,,Social Media\Customer2#edit#reshare
,Google Dev Account,[email protected],"8123,[email protected]#4912fkk!--3",https://accounts.google.com,"Google Cloud ID 448812771239122
Account Number 449128
This is multi-line",Shared Accounts#edit#reshare,2FA Phone Number,+19165551212
To import this file:
$ keeper import --format=csv test.csv
4 records imported successfully
The resulting vault will look like this image

Keepass Import

Keeper supports importing the record and folder structure directly from an encrypted Keepass file. File attachments are also supported. Make sure to first follow these instructions to install the necessary keepass modules.
$ keeper import --format=keepass test.kdbx
You can optionally make all top level folders as shared folder object with default permissions.
$ keeper import --format=keepass --shared --permissions=URES test.kdbx
For more options, see the help screen:
$ keeper help import

LastPass Import

Keeper supports automatic import of your LastPass vault by providing your LastPass email, Master Password and 2FA code.
See the LastPass Import documentation for more information on importing directly from LastPass.

Myki Import

Keeper supports importing the records from a Myki CSV file.
$ keeper import --format=myki myki.csv

ManageEngine Import

ManageEngine Import requires Commander version 16.6.13+
Keeper supports importing the resources and connected accounts directly from a ManageEngine Password Manager Pro server. Importing file attachments from a File Store resource is also supported. You will need a ManageEngine user with API access and a generated token to use this import functionality.
$ keeper import --format=manageengine https://localhost:7272
Substitue https://localhost:7272 with your server URL and port. You will then need to enter your ManageEngine API token.

Exporting Records from Keeper

To export records from your vault, use the export command. Supported export formats:
JSON export files contain records, folders, subfolders, shared folders, default folder permissions and user/team permissions. CSV import files contain records, folders, subfolders, shared folders and default shared folder permissions. Keepass files contain records, file attachments, folders and subfolders.

Keepass Export

$ keeper export --format=keepass test.kdbx
You can optionally provide file password through command line option --keepass-file-password - this flag will only apply when --format=keepass is set. Master pasword is required for Keepass export - if none provided you will be asked during export and your input will be masked.
$ keeper export --format=keepass --keepass-file-password=file_password_here test.kdbx
Export as PDF
Copy link
On this page
Commands
import command
export command
download-membership command
Detailed Instructions
Importing Records into Keeper
Exporting Records from Keeper