# Classic ASP and Java migration worksheet
Guide: https://yenra.com/java-asp/
Work in an isolated environment with fictional accounts/data. Keep credentials out of this note.

## Scope and dependencies
- User action / URL / request methods:
- Classic ASP or ASP.NET evidence:
- ASP scripts and include files:
- Host OS, IIS/runtime and support owner:
- Session keys, timeout, authentication and authorization:
- COM/Java bridge, versions, bitness and native dependencies:
- Database queries, transaction owner and permissions:
- Encoding, redirects and visible error behavior:
- Existing jobs or other callers:

## Proposed boundary
- API boundary or page-and-logic rewrite; reason:
- Request/response schema and version:
- Trusted downstream identity mechanism:
- Timeout, error mapping and retry/idempotency contract:
- Correlation identifier and redacted diagnostic record:
- Schema compatibility for the rollback window:

## Parity cases (record expected, actual and database effects)
- Permitted order:
- Another user's order:
- Missing order:
- Expired authentication:
- Empty field and non-ASCII input:
- Dependency timeout:
- Decimal/rounding fixture (fictional 19.95 x 3 = 59.85):
- Agreed intentional behavior changes:

## Cutover and rollback
- Routing switch, owner and initial scope:
- Error/latency review thresholds:
- Rollback action and test result:
- Schema compatibility verified by:
- Observed comparison window:
- Remaining callers before bridge retirement:

Read-only comparisons may exercise both implementations against controlled fixtures. Do not replay writes against live records. A routing rollback cannot reverse incompatible schema changes or duplicate business effects.