> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeperpam/commander-cli/command-reference/import-and-export-commands/proton-pass-import.md).
# Proton Pass Import
Automatic Migration of your Proton Pass Vault
## **Overview**
This document outlines the steps required to seamlessly migrate your Proton Pass Vault data into Keeper.
### Export your Proton Pass Data as a JSON File
By default, Proton Pass exports your data as a JSON File. Exporting on Proton Pass is only supported on the Proton Pass Browser Extension.
To export on Proton Pass:
1. Navigate to settings on your Proton Pass Browser Extension
2. Click on the Export tab and select Export.
This will export a zip file that contains the JSON file. Keeper commander gives you the option of providing either the zip file or the JSON file as input.
### Import your Proton Pass Data into Keeper
On Keeper Commander and with the exported zip file, executing the following command will import your Proton Pass Data:
```
import --format=proton ProtonPass.zip
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.keeper.io/keeperpam/commander-cli/command-reference/import-and-export-commands/proton-pass-import.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
