rudder-import-and-evolve

Import and Evolve Workflow

This skill teaches how to import existing RudderStack resources into CLI management and safely evolve your tracking schema over time.

When to Use This Skill

• You have existing tracking plans, events, or properties in RudderStack
• You want to manage them via YAML files and git
• You need to make changes without breaking production SDKs
• You're migrating from UI-based management to CLI

Import Workflow

┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│   RudderStack   │────▶│   Import to     │────▶│   Local YAML    │
│    Workspace    │     │   Local Files   │     │     Files       │
└─────────────────┘     └─────────────────┘     └─────────────────┘
                                                        │
                                                        ▼
                                               ┌─────────────────┐
                                               │   Git Version   │
                                               │    Control      │
                                               └─────────────────┘

Step 1: Authenticate

rudder-cli auth login

This prompts for an access token; the token decides the workspace. An agent does not run it: it asks the user to export RUDDERSTACK_ACCESS_TOKEN in the shell that starts the agent, and never asks the user to paste a token into the chat. See rudder-cli-setup.

Step 2: Verify Connection

rudder-cli workspace info --json

Should show your workspace name and workspaceID.

Step 3: Import Resources

rudder-cli import workspace

This imports:

• Events
• Properties
• Categories
• Custom types
• Tracking plans
• Event stream sources (if applicable)
• Transformations and libraries

Step 4: Review Imported Files

imported/
├── data-catalog/
│   ├── events/
│   │   └── *.yaml
│   ├── properties/
│   │   └── *.yaml
│   ├── categories/
│   │   └── *.yaml
│   └── custom-types/
│       └── *.yaml
└── tracking-plans/
    └── *.yaml