2) Exporting passwords from KeePass for Pleasant Password Server

See why customers choose Pleasant Password Server with a KeePass client

It is possible to export a user's set of passwords, by using KeePass for Pleasant Password Client.  It is also possible to copy entries from one KeePass to another KeePass instance (option: "Copy Whole Entries").

Creating a file export can be beneficial for storing and manipulating the information in a different format.

Note: When making a copy of secured vault passwords, ensure that the new file location is properly secured.

Have Questions?  Contact Us!

Enabling Export

By default the Export functionality has been turned off. However, any user will be able to re-enable if the client config, is not enforced (see below: Restrict Password Export). At the same time you may wish to lock the option ("Copy Whole Entries").

To re-enable export on the user's desktop:

  • Navigate to KeePass for Pleasant > Tools > Options > Policy tab
  • Check these options on:
    1. Export * (Allow exporting entries.)
    2. Export - No Key Repeat * (Do not require entering current master key before exporting.)
  • * Restart KeePass


If the first option is not enabled you may see:

  • KeePass: "This operation is not allowed by the application policy. Ask your administrator to allow this operation. The following policy flag is required: Export - Allow exporting entries."

If the second option is not enabled you may see the following prompt & popup:

  • KeePass: "Enter Current Master Key" (window prompt)
  • KeePass: "The composite key is invalid! Make sure the composite key is correct and try again." (popup)

Restricting Password Export

The ability to Export passwords / information can be restricted by administrators:

  1. By navigating to the KeePass options,
  2. Turning off KeePass Export and "Copy Whole Entries", and
  3. Assigning this Client Configuration file to be enforced for selected Users or Roles.

Better Alternatives than Exporting Passwords

These related methods are useful ways to manage the storage of your passwords, and are likely more secure/more convenient in many situations:

Export Options

  • Formats Available:
    • CSV, KDB, KDBX, XML, customizable HTML, Transform using XSL, or as Windows Favourites (bookmarks)
  • The export can be encrypted and password protected, or plain text, as you choose.
  • Not included in the Export/Import files:
    • Security Access
    • Roles
    • File Attachments
    • Plugin data

Password Export Steps

  1. Either:
    • Export All: Select Export from the File menu
    • Export a Folder: Right-Click on a folder
  2. Select a Format type and a filename
  3. Click Ok
  4. Enter a custom password (version 7.9.6)
  5. Click Ok

KeePass File Import Steps

To import this file back into either KeePass for Pleasant Password Server or the regular KeePass (

  1. Import the file into KeePass
  2. When prompted, enter the custom password (version 7.9.6), or the default password (previous versions):

How do I change the KDBX file password?

To store your exported passwords in a KDBX file with a password different than the default password mentioned in the section above, then follow these steps:

  1. Open KeePass for Pleasant Password Server.
  2. Export your entries to a KDBX file.
  3. Exit KeePass for Pleasant Password Server (make sure it's completely closed)
  4. Open up the regular version of KeePass (download from:
  5. Create a new database.
  6. Open File -> Change Master Key, and set a new password.
  7. Import your passwords from the KDBX file you exported earlier.

Scheduling Automatic Exports

We would recommend the methods in the "Better Alternatives than Exporting Passwords" section, as the export method can consume time and potentially even interfere with user actions.

Exporting can be scheduled automatically using KeePass Triggers. For example, see the export example here:


  • Be sure that this folder has been created ahead of time and ensure KeePass has access (try manually exporting first to that folder).
  • You could use an alternate Event such as "Time - Periodic" Event, instead of 'Saved database file' event (step 6).