cf-switch-backend

# 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 **Running in Cowork?** The "local" backend writes to the ephemeral sandbox filesystem — files vanish at session end. For Cowork team setups, use the Google (Drive) route and run `/contentforge:cf-cowork-setup` first to wire the Drive folder layout. ## How to Use ``` /contentforge:cf-switch-backend airtable /contentforge:cf-switch-backend google /contentforge:cf-switch-backend local /contentforge:cf-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` ...