Enterprise cloud migration often looks straightforward until the database estate comes into view: SQL Server workloads tied to old licensing decisions, finance teams questioning duplicate spend, auditors asking who controls encryption keys, and application owners refusing to risk downtime for a cleaner operating model. Public cloud services spending is forecast to rise from $595.7 billion in 2024 to $723.4 billion in 2025, but the hardest migrations still turn on narrower questions of license reuse, recovery, and operational control.
Minesh Chande, Senior WorldWide Specialist Solutions Architect at Amazon Web Services and a Senior IEEE Member, works in that exact space, helping enterprises modernize database platforms without forcing a false choice between cost discipline and managed-service reliability. To understand how teams are handling the hidden cost trap inside legacy SQL Server migration, we turned to Chande for his perspective on what the next stage of enterprise cloud modernization requires.
The Cost Problem Starts Before The First Workload Moves
“Migration can fail before the first workload moves if the economics do not survive review,” Chande says. “The hard part is not convincing teams that the cloud has value. The hard part is proving that the move will not make them pay twice for something they already own.” That concern is no abstraction. Managing cloud spend is cited by 84% of respondents as the top cloud challenge, while cloud spend is expected to rise by 28% in the coming year.
That is why Chande’s BYOM work on Amazon RDS Custom for SQL Server mattered. The design allowed enterprises to bring existing licensed SQL Server media into a managed database environment, avoiding the double licensing burden that can appear when valid software rights cannot be leveraged into the target service model. In one migration review, a finance lead reportedly circled the license line twice and asked why the company would pay again for rights it already owned. That question changed the room. Chande’s approach addressed the impasse by supporting estimated 30 to 60 percent savings for enterprise SQL Server workloads while keeping migration tied to managed cloud operations.
The Fix Had To Preserve Enterprise Control
Once the cost issue is visible, the next question is control. SQL Server estates in finance, healthcare, and retail rarely move as clean new deployments. They come with packaged applications, operating-system dependencies, audit requirements, and administrators who need enough access to keep business-critical behavior intact. In a 2024 SQL Server cloud study, users reported 85% satisfaction with Amazon EC2 due to migration ease, license mobility, and operating-system access, while 71% of Amazon RDS respondents reported overall lower cost benefits after moving from on premises.
Chande’s project sat between those needs. BYOM on RDS Custom for SQL Server gave customers a way to use pre-licensed SQL Server media while still operating inside a managed database model. The supported workflows included media onboarding and validation, instance provisioning using custom images, integration with AWS infrastructure services, and compatibility with managed service automation around backups, patching boundaries, and failover.
“The best migration design is boring in the right places,” Chande notes. “Teams should be able to see where the license enters, where automation takes over, and where their operational boundaries remain intact.”
Resilience Still Decides Whether A Migration Is Acceptable
Cost savings alone do not make a migration safe. Database owners still need confidence that a move to a managed environment will not weaken recovery, extend downtime, or leave teams without a dependable rollback posture. For the second consecutive year, 54% of respondents said their most recent significant outage cost more than $100,000, and one in five impactful outages cost more than $1 million from downtime to full recovery.
That is where the BYOM design carried practical weight. Chande’s solution preserved enterprise-grade high availability and point-in-time recovery while reducing the operational overhead of self-managed SQL Server environments. His recognition as an IETE Fellow reinforces the same kind of professional judgment required in these migrations, where database architecture, recovery planning, and operational control have to be evaluated together rather than treated as separate concerns. A migration that saves money but weakens recovery is not a modernization win.
Encryption Governance Has Become Part Of The Migration Decision
As database modernization moves deeper into regulated environments, encryption governance often decides whether a migration can proceed. In 2025 cloud security research, 42% of respondents identified encryption and key management as key enablers of digital sovereignty, while 33% pointed to data and workload portability as a leading driver for sovereignty efforts. Those numbers match the questions regulated customers ask before sensitive workloads move.
Chande’s BYOM approach required customer-managed KMS keys for data encryption, giving organizations a way to retain ownership and governance over encryption keys while moving SQL Server workloads into a managed AWS environment. That detail is especially important for finance and healthcare teams, where internal audit, data sovereignty, and compliance review can slow or stop cloud adoption.
“A migration plan has to satisfy the people who operate it and the people who audit it,” Chande says. “If key ownership is vague, the conversation gets harder. If the design is explicit, security teams can evaluate it without guessing.”
The Next Wave Will Reward Practical Migration Discipline
The next stage of enterprise migration will favor designs that make economics, recovery, and governance visible from the beginning. The global cloud migration services market was estimated at $16.90 billion in 2024 and is projected to reach $70.34 billion by 2030, growing at a 27.8% compound annual rate from 2025 to 2030. That growth points to a larger pattern: enterprises are still moving, but they expect migration designs that respect existing investments and regulated operating realities.
Chande’s work reflects that standard, fitting the same theme: this is not merely a database configuration issue but a professional discipline problem, one that examines how organizations move critical data systems into modern platforms while preserving accountability. “Cloud migration should not ask enterprises to abandon investments that still have value,” Chande says. “The better path is to carry those investments forward carefully, reduce the waste around them, and give the business a safer way to modernize.”
