SQL Server Migration & Upgrades
On-premise or to Azure. Planned, rehearsed, and reversible, so that the weekend of the cutover is the least interesting part.
Migrations Rarely Fail on the Database
The restore usually works. What catches people out is everything attached to it.
Logins that exist on the old server and not the new one. A linked server nobody documented. Jobs that ran under an account that no longer has rights. A collation difference that surfaces three weeks later in one report. A query that was fine under the old compatibility level and picks a different plan under the new one, on the busiest morning of the month.
None of these are difficult problems. They are simply easy to miss, and they are found at the worst possible moment by whoever is on call. The value in doing this properly is not technical brilliance on the night; it is the unglamorous work beforehand that means nothing surprising happens.
What We Handle
Moving to Azure
Azure SQL Database, Managed Instance, or SQL Server on a virtual machine. Which one you want depends on what your application actually does, and the wrong choice is expensive in ways that only appear on the bill.
Version Upgrades
From an out-of-support version to something current, with compatibility level handled deliberately rather than by default, and query plan regressions found in testing instead of in production.
Edition Changes
Enterprise to Standard is one of the more effective ways to cut a licensing bill, provided the workload genuinely fits inside Standard's limits. Establishing whether it does is the job.
Server Moves & Consolidation
New hardware, a new data centre, or several underused instances brought together onto one. Consolidation saves real money, but only if the workloads can share without fighting each other.
Assessment & Planning
What breaks, what needs changing first, how long it takes, and what it will cost. Delivered as something you can put in front of a board, not a list of technical caveats.
Testing & Rollback
A rehearsed cutover with a rollback plan somebody has actually run. A rollback plan that exists only as a paragraph in a document is not a rollback plan.
Making the Case for It
An upgrade justified only by a support deadline is a grudge purchase, and it tends to get deferred until it becomes an emergency.
It is a much easier conversation when the same project also gives the business something it could not do before. Native vector support, for instance, arrived in SQL Server 2025 and is available in Azure SQL, which means an upgrade can be the thing that finally lets you build search that understands what your customers mean rather than just what they typed.
The other half of the case is what it saves. Migrations are one of the few moments when somebody looks properly at what the estate is actually doing, and that is usually where the savings are hiding: capacity bought to cover inefficiency, editions nobody needed, storage full of history that should have been archived years ago. We've written separately about what that costs on-premise and what it costs in Azure.
Where to Start
Usually with a look at what you've got. Our free health check covers one instance and will tell you a good deal about how straightforward or otherwise a move is going to be, before anyone commits to anything.
For a whole estate, the SQL Server Audit is the fuller version: everything assessed end to end, with a written, prioritised plan and a fixed fee agreed up front.
Got a Migration Coming?
Whether it's next month or next year, the earlier the assessment happens the more options you have.
Talk to UsOr call us directly on 01293 988004.