|
<< Click to Display Table of Contents >> Migrating Packages to PDQ Connect |
You can move your custom packages to PDQ Connect from inside PDQ Deploy. Select one or more packages in the tree or in a folder's contents, right click, then click Migrate Package(s) to Connect.
PDQ Deploy exports the selected packages and opens them in the PDQ Migrate tool, where you sign in to PDQ Connect and choose what to upload. Your packages stay in PDQ Deploy; migrating copies them, it does not remove or change them.
PDQ Migrate is a separate tool that PDQ Deploy downloads the first time you migrate something. You are asked before anything is downloaded, and again whenever a newer version is available. If you decline an update, the version you already have is used.
The tool is installed to C:\Program Files (x86)\Admin Arsenal\Migrate Tool. The download is around 68 MB, so it may take a few moments on a slow connection. If the download cannot be reached, check this computer's internet connection and any proxy settings in Options > Preferences.
Package type |
Description |
|---|---|
Custom packages |
Packages you built yourself can be migrated, either one at a time or several at once. |
Package Library packages |
Auto Download packages from the Package Library cannot be migrated, and the menu item is unavailable when one is selected. PDQ Connect maintains its own copies of these packages, so there is nothing to move. |
Nested packages |
If a selected package uses a nested package step, the packages it depends on are included automatically so that the steps can be resolved in PDQ Connect. |
The exported file is written to your own temporary folder and is cleaned up automatically, so it is never left where other users of this computer could read it.
© 2026 PDQ.com Corporation. All rights reserved.
PDQ.com is a trademark of PDQ.com Corporation. All other product and company names are the property of their respective owners.
Help Version: 20.1.28.0