---
title: pulumi env clone | CLI commands
url: /docs/iac/cli/commands/pulumi_env_clone/
---

Clone an existing environment into a new environment.

## Synopsis

Clone an existing environment into a new environment.

This command clones an existing environment with the given identifier into a new environment.
If a project is omitted from the new environment identifier the new environment will be created
within the same project as the environment being cloned.

```
pulumi env clone [<org-name>/]<src-project-name>/<src-environment-name> [<dest-project-name>/]<dest-environment-name> [flags]
```

## Options

```
  -h, --help                help for clone
      --preserve-access     preserve the same team access on the environment being cloned
      --preserve-env-tags   preserve any tags on the environment being cloned
      --preserve-history    preserve history of the environment being cloned
      --preserve-rev-tags   preserve any tags on the environment revisions being cloned
```

## Options inherited from parent commands

```
      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
  -C, --cwd string                   Run pulumi as if it had been started in another directory
      --disable-integrity-checking   Disable integrity checking of checkpoint files
  -e, --emoji                        Enable emojis in the output
      --env string                   The name of the environment to operate on.
  -Q, --fully-qualify-stack-names    Show fully-qualified stack names
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
      --non-interactive              Disable interactive mode for all commands
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose
```

## SEE ALSO

* [pulumi env](/docs/iac/cli/commands/pulumi_env/)	 - Manage environments