migrate-a-dashboard

# migrate-a-dashboard Preserve decision meaning, not merely chart appearance. ## When to use - Use for business intelligence replacement, workspace moves, metric-layer adoption, or report redesign. - Do not expose broader data in the target through weaker row, column, or export controls. ## Procedure 1. Inventory pages, visuals, metrics, filters, parameters, drill paths, alerts, subscriptions, exports, links, users, roles, and usage. 2. Freeze metric definitions, source versions, timezones, currencies, nulls, and known limitations. 3. Map old queries and semantic definitions to target models with explicit transformation differences. 4. Recreate effective row, column, tenant, share, embed, download, and administrator access. 5. Match visual encodings, sorting, totals, labels, accessibility, interaction, and responsive behavior. 6. Compare representative filter combinations, edge periods, cohorts, alerts, exports, and scheduled delivery. 7. Dual-run with identical cutoffs and reconcile values, membership, latency, freshness, and user actions. 8. Migrate users in cohorts, preserve legacy references, monitor decisions and defects, and retire only after dependencies drain. ## Done - A dashboard migration register records metrics, queries, visuals, filters, access, alerts, users, dependencies, mappings, and owners - Value, membership, filter, access, export, alert, freshness, accessibility, performance, and dual-run checks verify parity