Know what the Snowflake estate contains before you pick a date

What we look at on Snowflake

• Tables, views and dynamic tables, profiled against the live workload where we can reach it
• Tasks and Streams, and the downstream jobs that fire when a stream advances
• Secure views, row-access policies and the role hierarchy as it stands today
• Shares going out and coming in, and who consumes them outside this account
• Snowpipe, stages and external tables that have to move in step with the data
• Stored procedures in Snowflake Scripting, JavaScript or Python, and which of them a person still has to rewrite

What a person still has to do

• 01Tasks and Streams have no one-for-one on Databricks. Those become Jobs or Lakeflow pipelines, designed rather than converted.
• 02The role hierarchy maps to Unity Catalog grants. It does not paste across.
• 03Outbound and inbound shares have to be re-homed. Delta Sharing is a different contract.
• 04Snowpipe and stages become Auto Loader, Lakeflow or a Jobs path. The plumbing is new even when the files are not.
• 05Procedures that hide business rules stay in the residue until someone reads them.

What the two weeks produce

• 01An inventory where every object is dispositioned as in scope, excluded, or owned by a person
• 02The exclusions written down and agreed, so the scope still holds when someone questions it in month four
• 03A dependency map and a wave plan that respects it
• 04A named owner against every workload surface
• 05Parity criteria per object type, agreed before any conversion runs
• 06A hard-object pilot, chosen as the thing most likely to break
• 07A go or no-go recommendation with the reasoning shown

The other sources