Migrating a Panorama-managed estate to Strata Cloud Manager

Moving firewalls from Panorama to Strata Cloud Manager (SCM) comes down to five steps: prepare and export from Panorama, run the migration workflow in SCM, check the snippets, repoint the firewalls, then push and validate. I ran it end to end on a pair of VM-Series firewalls in an Azure transit VNet, and one small prerequisite tripped up the first push.

I’m seeing more people who want to move their management to SCM, and many of them are Panorama-managed today. SCM has a migration workflow built for exactly this. Here is what it looks like in practice, including the part that went wrong.

Prefer to watch? The full walkthrough is seven minutes: Migrate Panorama managed estate to Strata Cloud Manager.

Before you start

Most of the work is in the preparation. These are the things I would have in place first. The official migration guide has the full list.

Tenant and access

  • Get the feature enabled. The migration workflow sits behind a feature flag. If you do not see it in your tenant, contact your account team and they can request that it is enabled.
  • Licence. The tenant needs a Strata Cloud Manager Essentials or Pro licence.
  • Superuser on both sides. You need the Superuser role in Panorama and in SCM.
  • Prisma Access in the same tenant. If the tenant has a Panorama-managed Prisma Access instance, the firewall migration option is not available until that has been migrated.

Firewalls

  • PAN-OS version. Firewalls need PAN-OS 10.2.3 or later.
  • Routing engine. If your firewalls are still using the legacy routing engine, migrate them to the Advanced Routing Engine (ARE) before you migrate them to SCM. Do it as its own change and confirm routing is healthy, so you are not changing the routing engine and the management plane at the same time.
  • Content. Update content on every firewall. This is the one that caught me out, and the story is in Step 5.

Planning

  • Decide what goes first. You can migrate in phases. Start with non-critical devices or device groups, or go site by site.
  • Know your templates. Note which templates and template stacks each firewall uses, so you know which snippets belong on which folders.
  • Pick the date. Check the SCM upgrade schedule for the tenant and avoid that window.

Step 1: Prepare Panorama and export the configuration

This part is done on Panorama.

  1. Back up Panorama and the firewalls.
  2. Check your default rules. If intrazone-default or interzone-default have been overridden at device group level, the migration tool cannot process the configuration. Remove the overrides.
  3. Commit and push every pending change, so the running configuration matches what is on the firewalls.
  4. Export running-config.xml. SCM wants that XML file, not a tech support file.
  5. If Panorama uses a custom master key, make a note of it. You need it when you upload the configuration.
  6. Pull a tech support file from each firewall you want to validate. The diff review in Step 2 uses it.

Step 2: Run the migration workflow in SCM

In SCM, go to the onboarding section and start the migration.

  1. Upload the Panorama running-config.xml file, and enter the master key if you use a custom one. SCM runs a sequence of checks on it.
  2. Review the compatibility screen. It flags anything that is unsupported or only partially supported in SCM today. Custom reports are a typical example. Unsupported items are trimmed from the configuration that lands in SCM; Panorama itself is not touched. You can export the summary, and you can stop here if all you want is an assessment. Otherwise acknowledge the items you can live without and proceed.
  3. Select the devices or device groups to migrate.
  4. Map templates to folders. You see the Panorama device group tree on one side and how it lands in SCM folders on the other. Auto template mapping associates the snippets with folders for you; manual mapping lets you assign each template or template stack yourself. If two or more device groups share a template, put it on a higher folder. A global baseline can sit on the All Firewalls folder. Where a folder has more than one snippet, set the order, because the order decides which one wins. Leave nothing unassigned.
  5. Click prepare migration, let the second round of checks run, then load the configuration into SCM. Read the load and validation results. They call out name collisions, missing references and names that break the 31-character limit.
  6. Review the configuration diffs. Pick a firewall, upload its tech support file, and SCM shows what was added, trimmed or renamed for that device. Passwords and keys show as modified. That is expected, because SCM encrypts them with a different master key. Long names may also have been shortened. Check at least one firewall of each type or site pattern.
  7. Confirm and finish.

When it finishes, the configuration is staged in SCM. The firewalls are still managed by Panorama at this point: the migration tool does not onboard them. That happens in Step 4.

Step 3: Check the snippets on each folder

This is the step people miss. Device groups map to folders, but the Device and Network tab configuration from your Panorama templates and template stacks comes across as snippets. A snippet does nothing until it is associated with a folder.

Whichever mapping option you chose in Step 2, go into each folder and check that the relevant snippets are associated, and associate any that are missing. That is what gives the firewalls their interface, zone and logical router settings. In my lab I also had a baseline template on Panorama carrying shared settings, so that snippet needed associating too.

Step 4: Repoint the firewalls at SCM

This part is done from Panorama.

  1. Push an update from Panorama telling the firewalls to connect to the cloud service.
  2. Clear the option that reverts the change if the firewall cannot reach Panorama. You are deliberately moving away from Panorama, so you do not want an automatic rollback.
  3. Select force template values on the push. If anything has been overridden locally on a device, this gives you a clean start.
  4. Back in SCM, move the firewalls from available devices to cloud managed devices.

The devices then show as connected in SCM and you can push configuration to them.

Step 5: Push from SCM and validate

With the firewalls connected, check each one sits in the folder you intended, then push the staged configuration from SCM.

The gotcha: update content before you migrate

My first push from SCM failed. The cause was a content version mismatch.

SCM stays current with content releases. Firewalls that have been sitting behind Panorama may not. In my case the configuration referenced a newer URL category, browser runtime attack, that the VMs did not know about because they were on older content. There is a knowledge base article covering it.

The fix was simple: check for new content, download and install it on both firewalls, confirm the category was present, then commit again from SCM. The second push went straight through and everything showed in sync.

What to check after the push

A successful commit is only the start. After the first push, check:

  • Every device shows as connected and in sync
  • Sessions and traffic flow look normal
  • Interface, routing and HA status are healthy
  • Logs are arriving in Strata Logging Service

Screenshot the connected state and the successful push. It is useful evidence for the change record.

If you need to back out

During the workflow you can cancel the migration, and after it loads you can revert. SCM takes a snapshot before it loads the migrated configuration, and you can load that from the config version snapshots. Reverting only changes what is staged in SCM. It does not push anything to the firewalls.

Pre-migration checklist

  • Ask your account team to have the migration feature enabled on the tenant
  • Confirm an Essentials or Pro licence and Superuser access in Panorama and SCM
  • Confirm PAN-OS 10.2.3 or later on every firewall
  • Migrate any firewall still on the legacy routing engine to the Advanced Routing Engine (ARE)
  • Update content on every firewall
  • Decide which devices or device groups go first, and avoid the SCM upgrade window
  • Note which templates each firewall uses, so you know which snippets belong on which folders
  • Back up Panorama and the firewalls
  • Remove any device group overrides of the intrazone-default and interzone-default rules
  • Commit and push pending changes, then export the Panorama running-config.xml
  • Have the Panorama master key to hand if it is not the default
  • Collect a tech support file from each firewall you will validate
  • Review the unsupported and partially supported items and decide what you can leave behind
  • Plan the Panorama push: auto-revert cleared, force template values selected
  • After the first SCM push, confirm every device shows in sync, then check traffic, HA and logging

This is a high-level run through a small lab estate, and I shortened some of the sequence in the video. A production migration deserves a proper plan and a maintenance window.

Watch the full walkthrough on The Packet Shed YouTube channel.

Built for the community, by an engineer. The Packet Shed is a personal project aimed at helping others untangle complex tech. The thoughts and opinions shared here are entirely my own, completely independent of my employer, and 100% pitch-free.