> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enkryptify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Import secrets

> Bring secrets from a .env file, Vercel, 1Password or AWS Secrets Manager into Enkryptify.

Already keeping secrets somewhere else? Move them into Enkryptify in two steps. Pull your environment into a local dotenv file, then upload it with the CLI.

```bash theme={"dark"}
ek import                  # imports ./.env by default
ek import .env.production  # or pass any dotenv file
```

The file path is optional. With no argument `ek import` reads `.env` in the current directory, or you can pass any path such as `.env.production`. It then parses the file and uploads the secrets into the workspace, project and environment you choose. See the [command reference](/cli/commands#import) for all options.

## Choose your source

<CardGroup cols={2}>
  <Card title=".env file" icon="file" href="/import/env-file">
    Upload an existing local `.env` file from the CLI or the dashboard.
  </Card>

  <Card title="Vercel" icon="triangle" href="/import/vercel">
    Pull project environment variables with the Vercel CLI.
  </Card>

  <Card title="1Password" icon="key-round" href="/import/1password">
    Resolve secret references into a `.env` with the 1Password CLI.
  </Card>

  <Card title="AWS Secrets Manager" icon="cloud" href="/import/aws-secrets-manager">
    Export a secret into a `.env` with the AWS CLI.
  </Card>
</CardGroup>

## Before you start

* Install the [Enkryptify CLI](/cli/install) and run `ek login`.
* Keep the generated `.env` file local and do not commit it to git.
* After a successful import the CLI offers to delete the source file, so no plaintext copy is left behind.

<Note>
  Whatever the source, the goal is a plain `.env` file with `KEY=value` lines. Once you have that, `ek import` handles the rest.
</Note>