Skip to main content
PD-Blog-How-to-transfer-Parallels-Header

How to Transfer Parallels to a New Mac

parallels-150x150
February 19, 2026

This article was originally written in October 2015 and has since been updated with new discoveries and research in January 2026.

If you’re updating your Mac and you use Parallels Desktop for virtual machines, you don’t have to start over on your new device. You can transfer Parallels Desktop to a new Mac while keeping your apps, files, and settings intact, as long as you move two things in the right order: your Parallels Desktop license, then your VM.

One important compatibility note: Intel-based virtual machines cannot run on Apple silicon Macs. That difference affects Windows options and shapes the cleanest migration path for many users upgrading hardware.

  • You can transfer Parallels to a new Mac in two parts: your license, then your virtual machine files.
  • The safest method for most users is an external drive transfer of the VM package, followed by activation on the new device.
  • An Intel Mac migration to another Intel Mac is usually straightforward, but an Apple silicon Mac transition changes what Windows VM types you can run.
  • Backups and a quick macOS compatibility check prevent most “it won’t start” surprises.

Before you start: Check your Macs, licenses, and backups

Before you start learning how to transfer Parallels Desktop to a new Mac, a smooth transfer starts with a quick pulse check on your setup:

  • Understand Intel vs Apple silicon differences: The type of Mac you’re moving to matters, and it directly affects Windows behavior and Windows virtual machine compatibility.
    • Intel to Intel: Your existing Windows VM typically moves over with minimal changes.
    • Intel-to-Apple silicon: Windows runs as Windows 11 on Arm. Most modern apps work well, but legacy drivers, kernel extensions, or specialized hardware may require extra validation.
    • Apple silicon to Apple silicon: This is often the simplest path, with the fewest compatibility changes.
  • Confirm your Parallels Desktop license and access: Before you install anything, verify your edition, subscription status, and account access so the license activation process is predictable.
  • Back up your virtual machines: Always back up your Windows virtual machines before transferring them. A VM is typically stored as a single .pvm file that contains the operating system, apps, and data.

If you do nothing else, do the backup. It can turn a stressful move into a reversible workflow.

Step 1: Prepare Parallels Desktop and your virtual machine on the old Mac

Before you copy anything to the new Mac, prep both Parallels Desktop and your VM so you are not moving an unstable state:

  • Open Parallels Desktop and shut down the VM completely; do not suspend it.
  • Once the VM is shut down, locate the virtual machine file on your Mac. By default, Parallels stores VMs in your user folder, which is often what people mean by the Parallels folder location. To locate it:
    • Right-click the Parallels Desktop application icon in the Dock, then select Control Center.
    • In the Control Center, right-click the VM you want, then select Show in Finder.
  • Optional: If you want an added safety layer before you start the Parallels VM transfer, keep a duplicate copy of the .pvm on external storage or in your usual backup system.

The goal here is simple: move a clean VM package, not a snapshot of a paused moment in time that can cause problems on first boot.

Step 2: Install and activate Parallels Desktop on your new Mac

With your VM prepared, get Parallels Desktop installed and activated on the new Mac. Even if you plan to move your existing virtual machine, installing fresh on the destination device reduces friction and makes Parallels Desktop installation more predictable.

Here’s what to do: 

  • Install the latest build by downloading it from the official Parallels Desktop download page on the new machine, then complete the Parallels Desktop step.
  • Deactivate the license on the old Mac (or sign out) so the same subscription or key can be used on the new device, using the steps in Parallels’ guide to deactivating Parallels Desktop on a computer.
  • Sign in with your Parallels account or enter your key to complete the license activation process, which typically prevents seat- and device-based activation from causing seat and device limit issues.
  • If you see what looks like a retail license activation error, confirm your installed edition matches your key and then try again.

Once Parallels is activated cleanly, you’re ready to move the VM.

Step 3: Transfer your virtual machine to the new Mac

After activation, you can handle the Parallels VM transfer itself. For most users, copying the .pvm file is the most reliable form of virtual machine migration.

Here are the steps to follow: 

  • Copy the .pvm from your old Mac to an external drive (external storage transfer), then copy it from the drive onto your new Mac (external drive transfer).
  • On the new Mac, double-click the .pvm file to register and launch the existing virtual machine in Parallels Desktop.
  • If prompted, choose whether you “copied” or “moved” the VM. Selecting Moved typically preserves VM parameters more closely, while Copied may generate new identifiers.
  • On first launch, update Parallels Tools if prompted, since Parallels Tools updates are a common prerequisite for stable performance after a host change.

If you’re comparing approaches, Parallels also documents two common paths: copying the VM package directly when transfering existing VM to new Mac and migrating the Parallels app plus license when transferring Parallels Desktop to a new Mac.

Once the VM boots, run a fast validation pass: open key apps, confirm shared folders, verify networking, and test any devices you rely on. That small checklist catches most issues early.

Moving from Intel to Apple silicon: What changes and what to expect

If you’re upgrading from an Intel based Mac to an Apple silicon Mac, the Apple silicon Mac transition is where expectations matter most.

Intel based Windows virtual machines cannot run directly on Apple silicon Macs. VMs created on Intel based Macs use x86_64 CPU architecture, which is different from the ARM architecture used in Apple silicon.

For most Intel to Apple silicon moves, the most reliable approach is:

  • Create a new Arm-based VM on the Apple silicon Mac (your new virtual machine setup).
  • Move your data and settings into the new VM instead of trying to move the entire Intel VM.
  • If you currently rely on a Windows 10 virtual machine, plan for Windows 11 on Arm on the new hardware, and validate any apps that depend on legacy drivers or specialized hardware, using Microsoft’s Windows Arm-based PCs FAQ as your compatibility reference point.

This can feel like extra work, but it typically creates a cleaner outcome. Once you validate what you actually use day to day, performance and stability are often better on modern M-series hardware.

Troubleshooting common transfer and activation issues

Most issues have a straightforward fix. Here are the most common failure points and what to do next.

“License already in use” errors

This often happens when you forget to deactivate first, or when you install one edition (Standard, Pro, Business) while your key belongs to another.

Fix: Install the correct edition, then complete the deactivation step on the old device so the license activation process can finish normally.

VMs that don’t open due to compatibility or incomplete transfers

If a VM doesn’t open on the new Mac, it may have been copied while suspended, or the transfer may have been interrupted. If you’re moving from Intel to Apple silicon, remember that Intel-based VMs won’t run and must be rebuilt as an ARM-based VM for Windows virtual machine compatibility.

Fix: Confirm the .pvm file size matches the original. If it’s incomplete, recopy the file from your backup or external drive, then try again.

Migration Assistant limitations

Migration Assistant limitations show up when you assume Apple’s transfer process will move VM packages and activation state cleanly across different Mac models. If you do use Apple’s tool for user files, follow Apple’s steps for transferring to a new Mac with Migration Assistant, then move Parallels VM packages directly so you can verify integrity end-to-end.

Fix: Use Migration Assistant for user files if you want, but handle Parallels VM transfer and VM packages directly so you can verify integrity end-to-end.

Once you’ve worked through these, most “can’t activate” and “VM won’t boot” reports disappear quickly.

When to contact Parallels Support

If you’ve done the basics and something still isn’t working, it’s usually faster to escalate than to keep repeating the same steps.

Contact Parallels Support if any of the following apply:

  • Activation fails after freeing all devices.
  • A VM won’t open despite a verified, complete backup.
  • You’re unsure how licensing applies in a Business or Enterprise environment, especially when you need to reconcile license activation across multiple Macs.

In those cases, starting at Parallels Support helps you route to the right team and avoid unnecessary back and forth.

Get up and running on your new Mac with Parallels Desktop

If you’ve been wondering how to transfer Parallels to a new Mac, the simplest mental model is that you’re moving two things: the app license and the VM.

By preparing your Macs and licenses, shutting down and backing up your Parallels virtual machine, completing activation on the new device, and validating everything after transfer, you can migrate confidently and quickly. 

If you end up needing to reinstall Parallels Desktop during troubleshooting, a clean reinstall, along with a verified VM copy, usually gets you back to a stable baseline without turning migration into an ongoing project.

Parallels Desktop for Mac