# Source: https://docs.zapier.com/platform/manage/export-cli.md

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

# Export integration to Platform CLI

> The Zapier Platform CLI (Command Line Interface) is a toolset you install and run in your local development environment. It allows you to build, test, and manage your Zapier integration through JavaScript code and terminal commands.

Platform UI is the way for users with API experience that are more comfortable with a visual form editor to build integrations on Zapier.

The CLI is, on the other hand, the most powerful tool for professional developers and teams. Some of the advantages:

* Access to all [features](/platform/quickstart/ui-vs-cli) of the Zapier Platform
* Ability to better optimize your code. Move shared logic into modules. Leverage middleware to centralize request & response processing.
* Easier team collaboration. You'll be able to check all the code for your Zapier integration into your team's source control repo.
* Set up automated regression tests, to catch errors each time you push a change.

To export your existing Platform UI integration to Platform CLI:

## 1. Install and configure the Zapier CLI on your development environment

Follow the steps in the setup section in our [quickstart guide](/platform/reference/cli-docs#quick-setup-guide)

## 2. Run the `convert` command to create a CLI version of your project locally

Create a new directory for your Zapier project and from the command line `cd` into it. Then run:

`zapier convert {your integration id} . --version={integration version you want to convert}`

Your integration ID can be found in the browser location bar in the Platform UI:

<Frame>
  <img src="https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/c5e0c7f17a5ab52d9661e134394e9cc7.webp?fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=93dce6bc0fabc8c2f550ed39ac979173" data-og-width="1389" width="1389" data-og-height="359" height="359" data-path="images/c5e0c7f17a5ab52d9661e134394e9cc7.webp" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/c5e0c7f17a5ab52d9661e134394e9cc7.webp?w=280&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=c9b9f88301a497d05a9de06e5fd36be7 280w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/c5e0c7f17a5ab52d9661e134394e9cc7.webp?w=560&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=9969cba093b39efc92dee7ebc2c4c4fd 560w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/c5e0c7f17a5ab52d9661e134394e9cc7.webp?w=840&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=dffdc1759884577ea97bcd0ea596c1ad 840w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/c5e0c7f17a5ab52d9661e134394e9cc7.webp?w=1100&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=ea5f74b3565c71a199d444d61aeb9337 1100w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/c5e0c7f17a5ab52d9661e134394e9cc7.webp?w=1650&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=c801ae890f0fe590cee07072d2bc2fc1 1650w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/c5e0c7f17a5ab52d9661e134394e9cc7.webp?w=2500&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=b4602c22b977bf00abd3d1ddc29a5085 2500w" />
</Frame>

Similarly, your version can be found there, and elsewhere throughout the Platform UI:

<Frame>
  <img src="https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/e31dd202b5e64bbcb13fc8b200518d17.webp?fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=695e85cc93afd1c9973425c3fdf278b7" data-og-width="1390" width="1390" data-og-height="334" height="334" data-path="images/e31dd202b5e64bbcb13fc8b200518d17.webp" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/e31dd202b5e64bbcb13fc8b200518d17.webp?w=280&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=d642a6883593065e00e9c71c129f6303 280w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/e31dd202b5e64bbcb13fc8b200518d17.webp?w=560&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=991f3c81a9a2c7e1a934f56779d3b905 560w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/e31dd202b5e64bbcb13fc8b200518d17.webp?w=840&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=569134916b105d8b048e24fd24f208f2 840w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/e31dd202b5e64bbcb13fc8b200518d17.webp?w=1100&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=c6f5d904567cc6b1a831ffadb850e9de 1100w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/e31dd202b5e64bbcb13fc8b200518d17.webp?w=1650&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=0ac5ecbb8077d2dc5cc75f9b09cbf073 1650w, https://mintcdn.com/zapier-82f0e938/2ebL4bG5uJP5JVc0/images/e31dd202b5e64bbcb13fc8b200518d17.webp?w=2500&fit=max&auto=format&n=2ebL4bG5uJP5JVc0&q=85&s=b61bd5d961e51520a665b35f347041ea 2500w" />
</Frame>

Using this example, to create our project in the current directory our command would be:

`zapier convert 1234 . --version=1.0.0`

## 3. Explore your new CLI project and get familiar with the tool

Check out the resources available in the [CLI section](/platform/reference/cli-docs) of the docs to learn all about the Zapier CLI.

If you need a refresher on JavaScript, it's well worth the time to check out some of the many great resources available [online](https://javascript.info/). The Zapier Platform uses promises pretty heavily, so this is a good JavaScript topic to get familiar with.

## 4. Deploy

When you ran convert and created your new local CLI project, it was automatically associated with your Zapier integration (using the `.zapierapprc` file).

A couple of important notes before deploying:

* When you push the CLI project to the server it will create a *new version* of your integration. If you haven't gotten familiar with how versions work you might take a moment and learn about those [here](/platform/manage/versions).
* Take a look at the version number in your `package.json` file. When you created your project with the `convert` tool we automatically incremented the version you converted. You can change this to a different version number depending on your needs, but make sure a version with that number doesn't already exist in your integration. Run `zapier versions` from your project directory to see what's already been created.
* Integrations converted with the `zapier convert` command will include `convertedByCLIVersion` in the `package.json` for informational purposes.

When you're ready to deploy your CLI version run:

`zapier-platform push`

When that completes you'll be able to see the new version in the Platform UI in the Manage > Versions section, and will be able to make Zaps with your new CLI-built version.

You will not be able to edit your new CLI-built version from the *Build* section of the Platform UI, the attributes of this version will all [show a lock icon](https://cdn.zappy.app/f048ffc4c905bcbb332e344ce0ce52ba.png).

You can still use all the other functions of the Platform UI, though, including version management, embed management and your Partner Dashboard. Your earlier versions, created within the Platform UI, are also still available and can still be edited and used.

If you decide that the Platform CLI is not for you, you can delete your new version from Manage > Versions and continue where you left off in the Platform UI.

***

*Need help? [Tell us about your problem](https://developer.zapier.com/contact) and we'll connect you with the right resource or contact support.*