Sign in Request access

Home · Migrations · SmartMove alternative

Comparison / Check Point direction

SmartMove
and NetConverter

Check Point documents SmartMove as a tool that converts a third-party firewall policy and NAT into a Check Point management database. NetConverter does not do that. Check Point in NetConverter is source-only, toward Palo Alto SET, XML or Panorama.

Discuss this migration →Compare migration paths →

Account approval and feature support apply. A listed migration path does not certify every model, version or configuration.

The short answer

Are these the same direction?

No. Check Point's public SmartMove description, including the CheckPointSW/SmartMove repository, says the tool parses other vendors and produces Check Point policy. NetConverter does not generate Check Point configuration. If the destination is Check Point, SmartMove is Check Point's tool, and this page will not pretend otherwise. If the destination is Palo Alto, the Handoff Bundle path is the one NetConverter publishes.

Define the handoff

What goes in.
What you review.

Source inputs

For NetConverter, a Check Point R80+ Handoff Bundle. R75 and R77 are not in scope. The hosted service does not log in to SmartConsole.

Target output

Palo Alto SET, XML or Panorama for review. Not a Check Point database.

Path-specific boundaries

NetConverter does not generate Check Point configuration. On the Check Point source path, VPN is not translated and zones remain any.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Destination

SmartMove's destination is Check Point. NetConverter's Check Point role is a source.

REVIEW 02

Version

NetConverter's published Check Point source is R80+. Do not send R75 or R77 and expect a translation.

REVIEW 03

VPN

Check Point VPN is missing on the NetConverter path. Do not claim it moved.

REVIEW 04

Review

NEEDS REVIEW and BLOCKED findings need an engineer. AI does not set status.

Each result's status comes from deterministic checkpoints (CP0–CP4) and, on firewall paths, behavior checks (BC1–BC4); AI can explain findings but never sets status. These are review areas, not a guarantee that every construct in them is automated. Unsupported features, missing captures and conditional behavior remain part of the engineering review.

Questions

Common questions

Can NetConverter import a policy into SmartConsole?

No. It does not generate Check Point output and it does not log in to Check Point.

Where is the Palo Alto guide?

Use Check Point to Palo Alto for SET and XML, and Check Point to Panorama when the management target is Panorama.

Is SmartMove endorsed or opposed here?

Neither. The pages describe the direction each tool publishes. Pick the tool whose destination you actually need.

Plan the next step

Bring the details
that make your migration different.

Say whether the destination is Check Point or Palo Alto. That choice decides which tool's own documentation applies.

Discuss your scope →Check Point to Palo Alto →