Great structured playbook — the 10-step framing makes this approachable for teams that are intimidated by "migration" as a project.

One thing worth calling out for larger migrations: the serverless compute Genie Code spins up during /importBI runs is billed under your workspace's serverless budget, not tied to a specific project or cost center by default. If you're migrating 30+ dashboards in parallel across multiple teams, that attribution gap adds up fast and can surprise finance at month-end.

A practical guardrail before starting: set a serverless budget policy scoped by tag or user group, so you get early signals on spend per migration workstream rather than discovering it after the fact.

On the Unity Catalog promotion step (step 7) — for teams in regulated industries (banking, healthcare), this is also where a PII scan of migrated metric views pays off. Genie Code faithfully migrates computed columns and filters, but it won't flag if a measure accidentally surfaces personal data that was previously hidden by row-level security in the original BI layer. Worth a data governance review pass before broad publication, especially if your Unity Catalog has mixed sensitivity tiers.