cf-switch-backendlisted

# Switch Tracking Backend Switch ContentForge's tracking and delivery backend between **Google Sheets + Drive**, **Airtable**, or **Local filesystem**. Optionally migrate existing tracking data and output files to the new backend. ## When to Use - Switching from local (default) to a cloud backend for collaboration - Migrating from Google to Airtable (or vice versa) for simpler auth - Downgrading to local when cloud access isn't needed - Checking current backend status before switching ## How to Use ``` /contentforge:switch-backend airtable /contentforge:switch-backend google /contentforge:switch-backend local /contentforge:switch-backend --status ``` ## What This Command Does ### Step 1: Identify Current Backend Read the active brand profile's `tracking.backend` field. Report current state: ``` Current backend: local Records: 47 tracking records Output files: 42 files in ~/.claude-marketing/{brand}/tracking/outputs/ ``` ### Step 2: Validate Target Backend **If switching to Airtable:** 1. Check `AIRTABLE_TOKEN` environment variable exists 2. If missing, guide through setup: - Go to [airtable.com/create/tokens](https://airtable.com/create/tokens) - Create a Personal Access Token with `data.records:read` and `data.records:write` scopes - Select the base that will hold tracking data - Set the environment variable: `export AIRTABLE_TOKEN=patXXXXXXXX` 3. Ask for the Airtable Base ID (from the base URL: `airtable.com/appXXXXXXXXX/...`) 4. Verify access by runn