Sign in Request access

Home · Migrations · Check Point to Panorama

Firewall migration / Scope first

Check Point
to Palo Alto Panorama

Translate a Check Point R80+ Handoff Bundle toward Palo Alto Panorama. Check Point is source-only. NetConverter does not generate Check Point output, and it does not log in to SmartConsole 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

Is Check Point to Panorama separate from Check Point to PAN-OS?

It is the Panorama target of the same source. The supported-vendors page lists Check Point to Palo Alto SET, XML or Panorama. The general guide covers that family. This page is the Panorama case: device groups, templates and shared objects need a placement review before anyone imports policy. Zones on Check Point migrations are still any. Check Point VPN is not a translated feature. R75 and R77 are out of scope.

Define the handoff

What goes in.
What you review.

Source inputs

A Check Point R80+ Handoff Bundle from a SmartConsole export. The hosted service does not log in to the Check Point management server.

Target output

Reviewable Palo Alto output aimed at Panorama. Confirm device-group, template and shared-object placement. SET or XML for a standalone firewall is the companion guide.

Path-specific boundaries

NetConverter does not generate Check Point configuration. Check Point SmartMove, as Check Point documents it, converts third-party policy into a Check Point database. That is the opposite direction.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Objects, security and NAT

The published comparison with Expedition marks Check Point R80+ objects, security, NAT, L3 and routes as live, with zones still any.

REVIEW 02

What is missing

Check Point VPN is missing. R75 and R77 are not supported.

REVIEW 03

Panorama hierarchy

Review where shared objects and rules should sit in device groups and templates. Do not treat hierarchy as already certified.

REVIEW 04

No live push

Nothing is pushed to Panorama. Engineers import and test the candidate.

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

Does NetConverter write a Check Point policy?

No. Check Point is source-only, via the Handoff Bundle. NetConverter does not generate Check Point configuration.

Which Check Point versions are in scope?

R80+ for objects, security, NAT, L3 and routes. R75 and R77 are not. VPN is not translated.

How is this different from SmartMove?

Check Point documents SmartMove as a tool that converts third-party policy and NAT into Check Point. NetConverter does not generate Check Point configuration.

Plan the next step

Bring the details
that make your migration different.

Bring the Check Point version, the package you can export, and the Panorama device-group layout you expect.

Discuss your scope →Check Point to PAN-OS →