Snowflake Begins Phased Removal of Legacy Worksheets and Dashboards from Snowsight Effective June 22, 2026 (BCR-2260)

Snowflake has started the phased removal of the Legacy Worksheets standalone UI and Legacy Dashboards from Snowsight. The rollout for both changes begins today, June 22, 2026, and will complete over the following weeks.

The change is tracked under identifier BCR-2260. New dashboard creation was already disabled across all accounts as of April 20, 2026. Legacy Worksheets remain viewable via a sidebar section in the new Workspaces experience after the standalone UI is removed, but Legacy Dashboards will no longer be accessible once removed.

Official source: Snowflake documentation for BCR-2260.

Key Timeline and Facts

• April 20, 2026: Workspaces became the universal default SQL editor (can no longer be disabled by accounts). New Legacy Dashboard creation was disabled for all accounts. Self-service worksheet migration tooling became available. Account administrators could still temporarily revert to Legacy Worksheets using the USE_WORKSPACES_FOR_SQL parameter until June 22.

• June 22, 2026: Rollout begins to remove the Legacy Worksheets standalone UI from Snowsight (phased over several weeks). Rollout also begins to remove Legacy Dashboards from Snowsight (phased over several weeks). After removal, dashboards are no longer accessible.

• Post-June 22, 2026: The USE_WORKSPACES_FOR_SQL = 'never' setting is no longer supported. Existing Legacy Worksheets remain accessible from the Legacy Worksheets section in the Workspaces sidebar.

• Python worksheets: Must be migrated to remain executable after the Legacy Worksheets UI removal. The migration tool converts them to Workspaces files (named worksheet_name.py.sql) containing stored procedure logic.

• Shared worksheets: Remain accessible to shared users after UI removal, but the bulk migration tool creates copies without preserving the original shared status.

• Reader accounts: Exempt from this specific change but will follow a separate deprecation timeline for Workspaces once fully rolled out.
• Legacy notebooks: Not affected by this change.

What This Means

This is a forced transition away from older Snowsight interfaces. Data teams, analysts, and administrators who still rely on Legacy Worksheets for SQL editing or Legacy Dashboards for visualization face a phased loss of the classic standalone experience.

The new Workspaces model emphasizes file-and-folder organization, sharing, and Git integration. Legacy Dashboards have no direct in-product successor within Snowsight and must move to Streamlit apps (via Snowflake’s built-in conversion tool) or external BI/visualization platforms.

Failure to migrate dashboards before or during the rollout window results in permanent inaccessibility. Shared content and automation referencing old URLs or entry points require updates. The change reduces long-term maintenance of legacy UI paths while pushing users toward modern Snowflake-native or third-party alternatives.

Actions to Take

Immediate (starting today, June 22, 2026):

• Review the Workspaces sidebar in Snowsight for the new Legacy Worksheets section to confirm continued access to existing content.

• Identify all Legacy Dashboards still in active use and prioritize them for migration, as they will become inaccessible during the phased rollout.

• Check account-level settings and remove any reliance on USE_WORKSPACES_FOR_SQL = 'never' before it stops working.

Short-term (within the next 1–2 weeks):

• Use the self-service bulk migration tool (available via banner in the Legacy Worksheets section of the Workspaces sidebar) to convert worksheets to Workspaces files where desired. Test the tool on non-critical worksheets first.

• For Python worksheets, run the migration immediately — these will stop being executable without conversion.

• Open each Legacy Dashboard and use the built-in “Generate Streamlit app” option to create a native Snowflake Streamlit replacement before the UI is removed.

• Update any internal bookmarks, documentation, automation scripts, or shared links that point to Legacy Worksheets or Dashboard URLs.

Before the rollout completes:

• Decide on target platforms for dashboards (Streamlit in Snowflake or third-party BI tools) and complete migrations. Test published Streamlit apps and connected data sources.

• For collaboration needs, migrate to shared Workspaces rather than relying on legacy sharing mechanics.

• Account administrators should verify that all users have access to Workspaces and communicate the timeline internally.

Post-rollout monitoring:

• Confirm that all critical Legacy Dashboards have been successfully converted or replaced and are no longer needed in the old format.

• Update any external processes, ETL jobs, or reporting that referenced the deprecated interfaces.

• Monitor Snowflake release notes and the BCR-2260 page for any adjustments to the phased timeline.

Teams should treat this as a standard deprecation with a clear migration window. Prioritize dashboards first due to the hard inaccessibility outcome, then address worksheet organization and Python content. The transition aligns with Snowflake’s push toward Workspaces as the primary modern interface for SQL and development work.

All details above are taken directly from the official Snowflake documentation page for BCR-2260.