Migration discovery · step 1 of 2

Azure Migration Intake

Answer what you know. This builds a draft high-level user specification and technical specification you can hand to your migration team as a starting point — not a substitute for full Azure Migrate discovery.

← Services

0 / 12 answered

Core details

required for a draft

Company name

Application name

Scale of use

Business purpose

What does it do, and who relies on it? One to three sentences.

Current hosting environment

Business criticality

Operating system

OS version (if known)

Application stack

Database engine

Primary migration driver

Additional details

recommended — sharpens the draft

Dependencies

Other systems, APIs, or shared databases this application talks to.

Data sensitivity / compliance

Preferred migration strategy

Hard constraints

Budget ceiling, deadline, systems that must stay on-premises, anything non-negotiable.

Draft saved in this browser