Source inputs
A scoped Panorama export with the selected devices, inherited policy context and intended SCM folder requirements.
Management migration / Scope first
Panorama
to Strata Cloud Manager
Prepare the source, review the translated configuration and validate the behavior that matters to your network. Start with the device, software version and features in scope.
Account approval and feature support apply. A listed migration path does not certify every model, version or configuration.
Define the handoff
What goes in.
What you review.
Target output
SCM JSON output for supported objects and policies, for review and on-site import.
Path-specific boundaries
This is a file-output migration workflow. Hosted conversion does not log in to SCM or push to firewalls. Confirm supported management features and use the applicable on-site importer.
Scope the review
Check the behavior,
not just the syntax.
Device-group and inherited-policy scope
Confirm the intended behavior, supported scope and target-platform requirements.
Object dependencies and naming
Confirm the intended behavior, supported scope and target-platform requirements.
Target folders and policy placement
Confirm the intended behavior, supported scope and target-platform requirements.
Import validation and firewall deployment
Confirm the intended behavior, supported scope and target-platform requirements.
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.
See the current product
Explore the workflow.
View dated product captures and a clearly labeled synthetic verification example. A screenshot of an interface does not establish acceptance of this migration path.
See the product tour →Understand your result
Read the findings and their limits alongside the output. Address blockers, validate device acceptance and test affected traffic before seeking deployment approval.
Read the result guide →Plan the next step
Bring the details
that make your migration different.
Source and target models, software versions, critical features and the change window help establish a realistic scope.