App Migration Readiness Questionnaire

Where and how the application runs today.

Primary languages, frameworks, or platforms in use.

Operating system, middleware, or runtime versions.

Highest number of users active at the same time.

Transactions per second during the busiest hour.

Average data volume received per day, in gigabytes.

Average data volume sent per day, in gigabytes.

Approximate total stored data size in terabytes.

Expected annual growth rate of stored data.

Whether load is relatively steady or has sharp spikes.

Whether traffic is mostly reads, writes, or mixed.

How sensitive users or processes are to response time.

Known batch, nightly, or maintenance processing windows.

Dominant shape of the application’s data.

Regulatory categories that apply. Selecting None clears the others.

Countries or regions where data must remain.

Typical inbound network bandwidth in megabits per second.

Typical outbound network bandwidth in megabits per second.

Key upstream or downstream systems this app depends on.

Identity provider used for authentication.

Federation or auth protocol in use (SAML, OIDC, etc.).

Approximate number of distinct roles or entitlements.

Committed or target uptime percentage.

Recovery point objective — maximum acceptable data loss.

Recovery time objective — maximum acceptable downtime.

Approved times when maintenance can run.

How often backups are taken (e.g. daily, hourly).

How the software is licensed.

Number of seats, cores, or instances under license.

Current vendor support or maintenance status.

Overall migration complexity; 1 is simplest, 5 is hardest.

How confident you are in the answers above.

How well this app fits the intended target platform.

Person to follow up with for clarifications.

Markdown supported (bold, italic, lists, links, code, headings). Each note is stamped with the current date and time.

**bold** · *italic* · `code` · - list · [link](url)