Situation and why it mattered
The existing SQL Server environment needed a more scalable foundation and a closer look at underlying query and pipeline design. New development had to move forward while current reporting remained available because operating teams still depended on it every day.
The real constraint
Modernization could not be treated as a back-end swap. Data completeness, report behavior, access, scheduled jobs, archives, stakeholder readiness, and a path back all had to be accounted for.
Role and team context
I led a mixed internal and vendor team, helped architect the new environment, coordinated the migration, and remained technically involved. I used Snowflake and helped shape the design, but did not serve as its administrator or personally build every component.
Approach
We kept the existing environment live while developing a medallion-style architecture, migrating data, validating completeness and report behavior, and planning the cutover. Selected high-value reports were rebuilt, scheduled jobs and access were transitioned, and rollback readiness remained explicit.
Result and what changed
The cutover completed without user downtime, and users did not need to change how they accessed reporting at the point of transition. Data became available early in the morning rather than late in the evening, giving reporting teams a more useful start to the day.
Evidence boundary
The organization is anonymous because the story includes constraints in the prior environment. A recalled cost reduction is not published because comparable cost records and scope have not been validated.
What was learned
Continuity is an outcome to design for. Architecture, validation, ownership, communication, and rollback planning belong in the same conversation.