Import & export
Plan import and export let you move plans between Alteryx One workspaces — for example, promoting from development to production. The exported format is portable and can be committed to version control.
Mutating commands are dry-run by default — add --apply to commit.
Quick reference
Section titled “Quick reference”| Command | What it does |
|---|---|
ayx one plans export |
Export a plan to a portable file |
ayx one plans import |
Import a plan into the workspace |
Export
Section titled “Export”# Dry-run — shows export metadata, writes nothingayx one plans export <plan-id>
# Commit — write the exportayx one plans export <plan-id> --applyUnlike flow export, plans export does not take an --output path flag — the server controls the output location or returns the content inline. Use --output json to capture the full response including any returned artifact data.
Import
Section titled “Import”# Dry-runayx one plans import
# Commitayx one plans import --apply
# Non-interactive (CI / scripts)ayx one plans import --apply --yes
# Target a specific profileayx one plans import --profile <name> --applyIn this version, ayx one plans import --help shows only the standard flags (--profile, --apply, --yes, and the diagnostic flags) — there is no --body or --input. If you need to automate plan imports, confirm the expected input mechanism for your Alteryx One version before scripting it.
Promote a plan between environments
Section titled “Promote a plan between environments”# 1. Export from devayx --output json --profile dev one plans export <plan-id> --apply \ > plan-export.json
# 2. Import to prodayx one plans import --profile prod --apply --yes