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

# Migrate from the community voiceflow-cli to the vf CLI

> Command-by-command mapping from the retired community voiceflow-cli to the official vf CLI, with explicit rows where no equivalent exists yet.

The community `voiceflow-cli` (installed as `voiceflow` from a personal
Homebrew tap) has been retired from this documentation. The official CLI is
`vf`, developed at [github.com/voiceflow/cli](https://github.com/voiceflow/cli).
They are different binaries with different commands, flags, and defaults, so
scripts need the mapping below rather than a rename.

## Install the replacement

Follow [Install](/cli/install), then [authenticate](/cli/authentication). The
old tap install (`brew install xavidop/tap/voiceflow`) has no supported
upgrade path to `vf`.

## Command mapping

| Community `voiceflow` command    | Official `vf` equivalent                                                                                                            |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| `voiceflow kb query`             | [`vf knowledge-base query`](/cli/commands/knowledge-base/query)                                                                     |
| `voiceflow document upload-file` | [`vf document`](/cli/commands/document) create commands                                                                             |
| `voiceflow document upload-url`  | [`vf document`](/cli/commands/document) create commands                                                                             |
| `voiceflow transcript fetch`     | [`vf transcript`](/cli/commands/transcript)                                                                                         |
| `voiceflow transcript fetch-all` | [`vf transcript`](/cli/commands/transcript) list and get                                                                            |
| `voiceflow analytics fetch`      | [`vf analytics query`](/cli/commands/analytics) per-metric commands                                                                 |
| `voiceflow agent export`         | [`vf environment export-json`](/cli/commands/environment)                                                                           |
| `voiceflow dialog start`         | [`vf conversation send`](/cli/commands/conversation)                                                                                |
| `voiceflow dialog replay`        | No direct equivalent. Script [`vf conversation send`](/cli/commands/conversation) over a saved transcript                           |
| `voiceflow test execute`         | No equivalent yet. Use [Tests](/documentation/measure/tests) in the product, or the [evaluation commands](/cli/commands/evaluation) |
| `voiceflow test suites`          | No equivalent yet. See [Tests](/documentation/measure/tests)                                                                        |
| `voiceflow server` (api-serve)   | No equivalent. The hosted [APIs](/api-reference/api-overview) cover the same surface                                                |
| `voiceflow completion`           | No equivalent yet                                                                                                                   |
| `voiceflow jsonschema`           | No equivalent. `vf --usage` prints the CLI usage schema in KDL format                                                               |

Rows marked "no equivalent" are the truth, not a placeholder: those community
features have no counterpart in `vf` today. If one of them blocks you, say so
on the [CLI issue tracker](https://github.com/voiceflow/cli/issues).

## What the official CLI adds

Beyond the mapped commands, `vf` covers surface the community CLI never had:
[projects](/cli/commands/project), [environments](/cli/commands/environment),
[functions](/cli/commands/function), [API tools](/cli/commands/api-tool),
[MCP servers](/cli/commands/mcp-server), [playbooks](/cli/commands/playbook),
[variables](/cli/commands/variable), [evaluations](/cli/commands/evaluation),
and [workspaces](/cli/commands/workspace), plus structured output
(`--output-format`), inline [jq](/cli/commands/overview) filtering, and
`--dry-run` on every command.

## The retired test platform

The community Test Platform web app was built on the community CLI's server
mode and is retired with it. For testing agents, use
[Tests](/documentation/measure/tests) and
[evaluations](/documentation/measure/evaluations) in the product.