> ## 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 from Vercel

> Pull a Vercel project's environment variables into a .env file then upload them with the Enkryptify CLI.

Use the Vercel CLI to pull a project's environment variables into a `.env` file, then upload that file to Enkryptify with `ek import`.

## Prerequisites

* The [Enkryptify CLI](/cli/install) installed and signed in with `ek login`
* A Vercel account with access to the target project
* [Node.js](https://nodejs.org) so you can install the Vercel CLI

<Steps>
  <Step title="Install the Vercel CLI">
    ```bash theme={"dark"}
    npm i -g vercel
    ```

    Check it installed with `vercel --version`.
  </Step>

  <Step title="Sign in to Vercel">
    ```bash theme={"dark"}
    vercel login
    ```
  </Step>

  <Step title="Link the directory to your Vercel project">
    Run this from your project directory then pick the scope and project at the prompts:

    ```bash theme={"dark"}
    vercel link
    ```

    This writes a `.vercel/` folder so the next command knows which project to read.
  </Step>

  <Step title="Pull the environment into a .env file">
    Pull the environment you want into a file named `.env`:

    ```bash theme={"dark"}
    vercel env pull .env --environment=production --yes
    ```

    <Note>
      Pass the filename and the environment explicitly. A bare `vercel env pull` writes to `.env.local` and pulls the `development` environment. Use `--environment=preview --git-branch=<branch>` for a preview branch, or pass a custom environment name such as `--environment=staging`.
    </Note>
  </Step>

  <Step title="Import into Enkryptify">
    ```bash theme={"dark"}
    ek import .env
    ```

    `ek import` parses the file, lets you choose the target workspace, project and environment then uploads the secrets. Accept the prompt to delete the `.env` afterward so no plaintext copy is left on disk.
  </Step>
</Steps>

## Notes

* The pulled file holds real secret values, including Vercel's sensitive variables. Keep it out of git and delete it after importing.
* `vercel env pull` writes standard `KEY="value"` lines that `ek import` reads as is, so no extra conversion step is needed.

## Next steps

* [Import from 1Password](/import/1password)
* [Import from AWS Secrets Manager](/import/aws-secrets-manager)
* [CLI Quickstart](/cli/quickstart)