Sign in Request access

Firewall Validation Checklist Before Migration

Use this checklist to verify migration output quality before change windows and production deployment.

Pre-Cutover Validation Steps

  • Confirm source and target inventory counts are within expected bounds.
  • Validate all policy references resolve to defined objects.
  • Review zone/interface mapping consistency.
  • Check NAT behavior alignment against original intent.
  • Flag and review potentially shadowed policies.
  • Run vendor-specific structural checks for target platform readiness.
  • Export findings and remediation notes for change approvals.
  • Execute pilot deployment before full rollout.
Run Validation Tool Read Framework

What the checks are, and what they are not

A migration result is not a cutover approval. On firewall paths, status comes from deterministic checkpoints (CP0–CP4) and behavior checks (BC1–BC4). AI can explain a finding. AI never sets status. A blocker is not something an assistant can clear by rewriting the summary.

Read the result as partial evidence. It can show unresolved references, zone and interface questions, NAT that did not line up, and policy that looks shadowed. It cannot show live traffic, device acceptance, or that every feature in the source was translated. Router and switch jobs stay in NEEDS REVIEW even when the emitted text has been checked.

Before a change window, keep the source and target versions, the scope you actually uploaded, and the findings you have not answered. Import or paste only after an engineer has accepted the candidate. A pilot on the target platform is still required. The hosted service does not log in to a customer firewall or manager to perform that pilot.

Keep the unanswered findings with the change record. A pilot on the target still has to pass before the window. Related reading: the migration hub for the path you are on, and supported platforms for what is source-only, target-only, or on request. Strata Cloud Manager conversion is supported on request. It is not a self-service target, and NetConverter does not read SCM configurations.