Projects and migrations
Azure Database Migration
Moving databases off ageing on-premises servers into Azure — sized against what you actually use rather than what the old server happened to have.
What the work involves
- An inventory of what databases exist, which is often longer than expected.
- A compatibility assessment against the target, including deprecated features still in use.
- Choosing the target: a managed instance, a single database, or a VM. They differ in cost, effort and what they take off your hands.
- A test migration and a validation pass with the people who actually use the application.
- Agreeing a cutover window and a rollback point before the real move.
What it depends on
Size and downtime tolerance, mostly. A database that can be offline overnight is a straightforward move; one that cannot is a different piece of work involving replication and a much shorter cutover.
Version matters too. Migrating from something long out of support usually means fixing compatibility problems that have been quietly accumulating.
Commonly underestimated
Applications with a server name hardcoded somewhere nobody remembers. These surface at cutover, which is the worst time to find them.
Scheduled jobs, agents and integrations attached to the old server. The database moves cleanly and the things around it do not follow by themselves.
Backups. Your existing backup approach may not apply to the target, and discovering that after cutover is not the moment to design a new one.
How we scope this
We do not quote this work before seeing your environment. How long it takes and what it costs depend on what you already have, how much of it there is, and how quickly your side can make decisions — and a number produced without knowing those is a guess you would end up budgeting against.
What we will commit to is a start: work begins within five business days of signature. If a particular engagement cannot start inside that window, we say so before you sign.
More on this in what it costs. Ongoing support for this sits under our services.
Other projects
-
Azure Virtual Desktop
A full Windows desktop delivered from Azure, so staff get the same environment from any device, anywhere, and it stays under your control rather than living on a laptop. Access is built on identity and conditional access rather than a VPN nobody wants to use.
-
On-Premises to Microsoft 365
Email, files and identity moved off your own servers into Microsoft 365, including the part most migrations underestimate — deciding what does not come with you.
-
Microsoft 365 Commercial to GCC High
The migration a defense contractor makes when CUI enters the picture. It is a tenant-to-tenant move, not an upgrade, and the CUI boundary has to be designed before anything is copied.
Talk it through
Tell us what you're moving and what you're moving it from. Twenty minutes, no obligation.
Schedule a call