<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Move my Panorama vm from VSphere to Hyper-V in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/move-my-panorama-vm-from-vsphere-to-hyper-v/m-p/1262369#M126898</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1495067427"&gt;@J.Dore&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Rather than converting or live-migrating the existing VMware VM to Hyper-V, the supported approach is to deploy a new Panorama virtual appliance on Hyper-V and migrate the Panorama configuration to it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;There is a techdoc on &lt;A href="https://docs.paloaltonetworks.com/panorama/administration/transition-to-a-different-panorama-model/migrate-a-panorama-virtual-appliance-to-a-different-hypervisor" target="_self"&gt;Migrating a Panorama Virtual Appliance to a Different Hypervisor&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="PDq2pG_selectionAnchorContainer" data-end="3077" data-start="2798"&gt;At a high level, you'll deploy the Panorama VHDX on Hyper-V, bring the new appliance to the appropriate PAN-OS/content versions, export the configuration from the existing Panorama, migrate the serial/license as applicable, and then import the configuration on the new appliance.&lt;/P&gt;
&lt;P class="PDq2pG_selectionAnchorContainer" data-end="3077" data-start="2798"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="3355" data-start="3082"&gt;One thing to plan for is locally stored logs. The Panorama configuration can be migrated, but existing logs on the VMware Panorama are not transferred to the new VM. If retaining those logs is important, the old Panorama can temporarily remain available as a Log Collector.&lt;/P&gt;
&lt;P data-end="3355" data-start="3082"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="3485" data-start="3360"&gt;I would also verify your current PAN-OS version against the Panorama Hypervisor Support matrix before starting the migration.&lt;/P&gt;
&lt;P data-end="3485" data-start="3360"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="3485" data-start="3360"&gt;Hope this helps!&lt;/P&gt;</description>
    <pubDate>Thu, 20 Aug 2026 02:56:09 GMT</pubDate>
    <dc:creator>JayGolf</dc:creator>
    <dc:date>2026-08-20T02:56:09Z</dc:date>
    <item>
      <title>Move my Panorama vm from VSphere to Hyper-V</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/move-my-panorama-vm-from-vsphere-to-hyper-v/m-p/1262139#M126890</link>
      <description>&lt;P&gt;We are changing our hypervisor platform from VMware to Hyper-V. Our normal migrate process (Shutdown, Backup with Veeam, Live Migrate to Hyper-V) failed with #Panorama, perhaps not unexpectedly&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How can I migrate my current setup?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2026 08:30:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/move-my-panorama-vm-from-vsphere-to-hyper-v/m-p/1262139#M126890</guid>
      <dc:creator>J.Dore</dc:creator>
      <dc:date>2026-08-18T08:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: Move my Panorama vm from VSphere to Hyper-V</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/move-my-panorama-vm-from-vsphere-to-hyper-v/m-p/1262369#M126898</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1495067427"&gt;@J.Dore&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Rather than converting or live-migrating the existing VMware VM to Hyper-V, the supported approach is to deploy a new Panorama virtual appliance on Hyper-V and migrate the Panorama configuration to it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;There is a techdoc on &lt;A href="https://docs.paloaltonetworks.com/panorama/administration/transition-to-a-different-panorama-model/migrate-a-panorama-virtual-appliance-to-a-different-hypervisor" target="_self"&gt;Migrating a Panorama Virtual Appliance to a Different Hypervisor&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="PDq2pG_selectionAnchorContainer" data-end="3077" data-start="2798"&gt;At a high level, you'll deploy the Panorama VHDX on Hyper-V, bring the new appliance to the appropriate PAN-OS/content versions, export the configuration from the existing Panorama, migrate the serial/license as applicable, and then import the configuration on the new appliance.&lt;/P&gt;
&lt;P class="PDq2pG_selectionAnchorContainer" data-end="3077" data-start="2798"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="3355" data-start="3082"&gt;One thing to plan for is locally stored logs. The Panorama configuration can be migrated, but existing logs on the VMware Panorama are not transferred to the new VM. If retaining those logs is important, the old Panorama can temporarily remain available as a Log Collector.&lt;/P&gt;
&lt;P data-end="3355" data-start="3082"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="3485" data-start="3360"&gt;I would also verify your current PAN-OS version against the Panorama Hypervisor Support matrix before starting the migration.&lt;/P&gt;
&lt;P data-end="3485" data-start="3360"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="3485" data-start="3360"&gt;Hope this helps!&lt;/P&gt;</description>
      <pubDate>Thu, 20 Aug 2026 02:56:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/move-my-panorama-vm-from-vsphere-to-hyper-v/m-p/1262369#M126898</guid>
      <dc:creator>JayGolf</dc:creator>
      <dc:date>2026-08-20T02:56:09Z</dc:date>
    </item>
  </channel>
</rss>

