Choose a migration question
Start with one decision: which dependency needs investigation, which workload should move first, or what performance behavior needs comparison. Name the workload owner and the security reviewer who will interpret the results.
Define the workload
Record the supported Linux target, deployment environment, important processes, and the traffic paths relevant to your question. Include the expected workload schedule so collection can cover representative activity.
Prepare access
Follow the installation guide for administrator access, organization API keys, and connectivity. Agree on the collection window with the workload owner before starting.
Agree on the review
Bring the migration concern, existing dependency information, and any performance constraints. Review captured evidence alongside coverage and missing observations. A completed scan is a starting point for interpretation.
Leave with a next step
Document what was observed, what remains uncertain, the next test or change, and its owner. See the migration review guide for a repeatable review structure.
Define acceptable alternatives
Bring security requirements, known dependencies, vendor constraints, and performance limits. Identify which native upgrades, connection-protection paths, or implementation changes your team could evaluate. Support and prerequisites must be confirmed for the specific operation, version, connection, and deployment.
Agree on the deliverable and validation
Scope an operator-assisted application migration evidence report with the Laviq team: evidence and coverage, requirements and dependencies, options evaluated, test conditions and costs, selected action and prerequisites, and before-and-after results where a change is evaluated. Decide who will own the next action and which observations would establish success. The report is prepared collaboratively through the agreed assessment.