> For the complete documentation index, see [llms.txt](https://docs.winga.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.winga.me/import-guides/importing-from-vercel.md).

# Importing from Vercel

Winga can read a Vercel project's environment variables and turn them into feature flags. This guide covers connecting Vercel to your workspace and running the import.

***

### 1. Connect Vercel

Open your workspace and go to **Connections** from the workspace navigation. On the Connections page, find the **Vercel** card under *Available integrations* and press **Connect**.

Vercel connects with a **personal access token** rather than an OAuth redirect. A dialog opens asking you to paste a token with read access to your account:

1. Press **Create a token in Vercel** to open [vercel.com/account/tokens](https://vercel.com/account/tokens) in a new tab.
2. Create a token there and copy it.
3. Paste it into the dialog and press **Connect**.

Winga validates the token against the Vercel API before saving the connection. You need the **owner** or **admin** role in the workspace to add or remove a connection.

***

### 2. Start the import

The import wizard lives on a project's **Flags** page, not on the Connections page. Open the project you want to import into, go to its **Flags** page, and start an import. Choose **Import from Vercel**, then pick the Vercel project to import from.

***

### 3. How variables are partitioned

Winga reads your project's environment variables from the Vercel API and splits them into two groups based on each variable's type:

* **Plain and system variables** import **with their values**. Their parsed value can be seeded as the flag's default if you choose to import values.
* **Sensitive (encrypted) variables** import as **name only**. Vercel never returns the plaintext of an encrypted environment variable through its API, so Winga imports the key with an empty value. You set the real value yourself after the flag is created.

Because of this split, the **Import values too** option in the configure step is only available when at least one plain (non-encrypted) variable is present in the import. If every variable in the project is encrypted, the import brings in the names so you can recreate the flags, and you fill in values manually.

***

### 4. Review and configure

After the variables are fetched, the review step lists every key. Deselect any you don't want, then move to the configure step to:

* choose which environments the imported flags are enabled in, and
* optionally import the parsed values as flag defaults (off by default — only enable this for test or example values, never production secrets).

Press **Import** to create the flags.