AS DataWorksBook an assessment call
Menu

Azure & Microsoft Migration

The assessment: what you get before you decide anything.

A fixed-scope, fixed-price review of what you run, what it depends on, what it will cost in Azure, and what will hurt. Read-only — we change nothing. You get a costed plan and a risk register, and you decide what happens next: with us, with your own team, or with somebody else.

access during the assessmentread-only — we change nothing

Assessment scope map During a migration readiness assessment we read five parts of the environment — servers and applications, SQL Server and databases, network paths, identity and licensing, and backups — and change nothing. Configuration changes are explicitly out of scope until a separate, approved engagement begins. Your environment Servers SQL Server Network Identity Backups Read-only. We inventory each of these — we change none of them. Out of scope during the assessment Configuration changes. We make none — findings only.
Five parts of the environment are read during the assessment — servers and applications, SQL Server and databases, network paths, identity and licensing, and backups. Configuration changes are out of scope until a separate, approved engagement begins.

What's in scope

We inventory what you run and what it depends on — servers, databases, applications, network paths, identity, licensing, backups — using Azure Migrate for discovery and dependency mapping, plus direct review of the things automated tooling always misses. Nothing is reconfigured: the assessment inspects, it does not change.

What you get

The assessment is a standalone deliverable. If you take it to another firm to execute, it is still a complete and useful document. We write it that way deliberately — a plan that only works if we deliver it is a sales instrument, not a plan.

What it costs and how long it takes

What happens after

You decide whether to migrate at all — with us, with your own team, or with somebody else. The four real paths for a SQL Server estate specifically, including the ones that don't involve a migration at all, are onSQL Server to Azure SQL.

How the assessment runs

  1. Discovery. Azure Migrate maps servers, dependencies and utilisation; we review by hand the things automated tooling always misses.

  2. Analysis. Each workload gets a recommendation — rehost, re-platform, replace with SaaS, rebuild, or leave where it is — with a costed Azure run-rate and a one-time migration estimate.

  3. Report. A written risk register and a sequenced wave plan, handed to you as a standalone document you can act on with anyone, not only with us.

This is one part of Azure & Microsoft Migration.

Start with the assessment, not the migration.

Book an assessment call

30 minuteswith the engineer who would scope the work[PLACEHOLDER: written-summary turnaround, not yet committed]