uipath-cli
latest
false
- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip docsai
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- create-project
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-workflow-examples
- pack
- restore
- run-file
- search-templates
- start-studio
- stop-execution
- uia
- uip traces
- Migration
- Reference & support
UiPath CLI user guide
Last updated May 7, 2026
The Migration section is for teams moving from the legacy .NET CLI (uipcli.exe / dotnet uipcli.dll, calendar-versioned 2025.10 and earlier) to UiPath CLI 1.x (uip, TypeScript on npm). The two CLIs are different binaries with different command shapes, auth models, and output formats — this section gives you the mapping.
If you are starting fresh on 1.x and have no legacy pipelines to migrate, skip this section and go straight to Get started and How-to guides.
The four pages
| Page | What it covers | Read it when |
|---|---|---|
| Migrating from the legacy .NET CLI | The narrative overview: what changed and why. Headline differences in runtime, distribution, scope, and output. | Read first — sets context for the other three. |
| Command map | Per-verb mapping (uipcli package pack → uip rpa pack, etc.) with classification (1:1, 2 steps, removed). Before/after snippets. | When you are porting a specific uipcli invocation. |
| Flag renames | Per-flag mapping inside each verb (--governanceFilePath → --governance-file-path, -A/--accountForApp → --organization, etc.). | When you have a verb mapped but a flag is missing or renamed. |
| Breaking changes | Semantic shifts that affect every command: auth modes removed, implicit env-var reading removed, exit-code contract, stdout format. | Before any porting — these apply across the board. |
Recommended migration order
For a typical CI pipeline migration:
- Migrating from the legacy .NET CLI → understand the runtime and distribution change (
.NET→ Node/Bun, MyGet → npm). - Breaking changes → before you change a single line, know what the cross-cutting differences are. Auth alone may break your pipeline.
- Command map → walk your existing
uipclicalls one by one. Note the rows marked 2 steps or N steps — they need new shell logic, not a simple rename. - Flag renames → fill in per-flag detail.
- Then a CI/CD recipe for your platform — copy and adapt.
Quick-start for the impatient
The minimum viable port:
# Legacy
uipcli package pack <project> -o <out>
uipcli package deploy <pkg> <url> <tenant> -A <org> -I <id> -S <secret> --processName <name>
# New (uip)
uip login --client-id env.UIPATH_CLIENT_ID --client-secret env.UIPATH_CLIENT_SECRET --tenant <tenant>
uip rpa pack <project>
uip or packages upload <pkg>
uip or processes create --name <name> --package-key <key> --package-version <v> --folder-path Shared
# Legacy
uipcli package pack <project> -o <out>
uipcli package deploy <pkg> <url> <tenant> -A <org> -I <id> -S <secret> --processName <name>
# New (uip)
uip login --client-id env.UIPATH_CLIENT_ID --client-secret env.UIPATH_CLIENT_SECRET --tenant <tenant>
uip rpa pack <project>
uip or packages upload <pkg>
uip or processes create --name <name> --package-key <key> --package-version <v> --folder-path Shared
Full per-flag detail is in Flag renames.
What's not in Migration
- New features in 1.x that have no legacy equivalent (skills, MCP, sessions, JMESPath filtering). Those live in What's new.
- The legacy CLI's documentation. It still lives at the CI/CD integrations docs, which remain canonical for
2025.10and earlier.
See also
- What's new — headline summary, target audience: anyone deciding whether to migrate.
- Versioning and stability — the contract you can rely on after migrating.
- Authentication — the auth flow your pipeline will use post-migration.