Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 CLI Documentation | 2026.1

# p4 renameclient

Rename a client workspace.

## Syntax

    p4 [g-opts] renameclient --from=old --to=new

Syntax and naming conventions

## Description

This command renames a client workspace and modifies any relevant database records. This is convenient because the user only executes one command. The result is the automatic creation of a new client, the migration of work-in-progress to that new client, and the deletion of the old client. In addition, this command adds an entry to the spec depot for the new client, and adds a deletion entry for the old client.

The migration of work-in-progress includes:

- pending and shelved changes created by the client workspace

- any fixes that the user made to jobs associated with pending changes

- any files that the user has opened or shelved

- the files on the client's have list The list of file revisions most recently synced from the depot into the workspace. In other words, the list of files that the client workspace has.

- the client record itself

The run.renameclient.allow configurable determines which sort of user can run the command.

### Limitations

- The client cannot be renamed to a client that already exists.

- Does not modify submitted changes or fixes that are associated with submitted changelists.

- The client name is not changed in descriptive text fields, such as job descriptions, change descriptions, and client workspace descriptions.

- Does not process unloaded clients, so any unloaded client to be renamed should be reloaded first.

- Is not supported for use with partitioned or readonly clients, clients with opened streams, or clients with promoted shelves.

## Usage notes

Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required
--- | --- | ---
N/A | N/A | `admin` or owner of client workspace

Your search for returned results