Tenant Migration Skill

Audit and execute the full migration checklist when cloning an existing Movemental tenant platform (the source, e.g. alan-hirsch) to create a new tenant deployment (the target, e.g. brad-brisco).

Context

This is a multi-tenant thought leader platform. Each tenant is:

• A separate Git repo/deployment sharing the same codebase structure
• Scoped to one organizations row in a shared Supabase database via TENANT_ORG_ID
• Visually differentiated via globals.css CSS variables and tenant.config.ts

The source repo (alan-hirsch) is the reference implementation. New tenants clone the repo, then must change every tenant-specific surface. This skill audits what's been done and what remains.

Execution Steps

Phase 1: Database & Org Identity (Supabase MCP)

Use the Supabase MCP (project vhaiiiykcukrlyvwlgip, public schema) to verify: