**Important**
This feature is currently only available through an invitation-only Private Preview, as both it and the documentation are under development, incomplete, and subject to change.
Please do not share links to these docs with others outside of the Private Preview.
Once this feature is released, it will be announced and this banner removed.
Before you can perform a migration using the Patch My PC (PMPC) Cloud Migration feature, you need to ensure that your On-Premises Publisher (Publisher) is connected to the same PMPC Cloud Company that you plan to migrate the objects to.
**Note**
See [Add a Connection](../cloud-administration/manage-cloud-connections/add-a-connection.md) for further details.
You also need to ensure that the Enable Application Migration checkbox on the Cloud tab is checked.
**Note**
If you do not see the **Enable Application Migration** checkbox on the **Cloud** tab, ensure you are running the required version of Publisher as detailed in [Migration Requirements](migration-requirements.md).
**Important**
If you click **Disconnect** on the **Cloud** tab of the **Publisher**, all of the data for the Migration feature will be deleted from your PMPC Cloud company. You should avoid doing this until you have completed the migration of everything you need to migrate from ConfigMgr to PMPC Cloud.
Next, sign in to your PMPC Cloud company and verify that the Migration node is visible.
When you navigate to Migration, the Migration page is displayed, showing a list of the ConfigMgr applications that have been detected with the following information.
| Field | Description |
|---|---|
| Match Type |
The result of our attempt to match the ConfigMgr application to an app in our App Catalog, which will be one of the following: PMPC App – We have successfully matched the ConfigMgr application to a version in our catalog. These apps can be deployed into Intune as a PMPC App and kept up to date by us for you. Custom App – We have been unable to successfully match the ConfigMgr application to a version in our catalog, but we can still help you migrate it to Intune. Not Supported – We cannot currently migrate the ConfigMgr application, such as PSADT, or an app we’ve published from our Publisher to ConfigMgr, where it doesn’t make sense to migrate it, as you can just deploy it straight from our catalog to Intune using PMPC Cloud. TIP: |
| Matched App | The name of the app we have matched the ConfigMgr application to in our catalog. |
| Status |
The migration status of the ConfigMgr application, which will be one of the following: Not Started – The migration process has not been started. Pending – The migration process has been initiated. In Progress – The migration is in progress. Migrated – The application has been successfully migrated to PMPC Cloud. |
| Info | If there is further information/warnings about this application that we want you to review (such as we’ve detected a setting in the ConfigMgr application we cannot migrate), a warning triangle is displayed in the Info column.
The triangle includes a number, which is the number of warnings. If you hover your mouse over the triangle, you will see a summary, and if you click the triangle, it will open the properties of the application and display the triangle beside the items we are warning you about. Clicking the triangle will show you more details that you should review before continuing to migrate the application. |
**Note**
The last column displays the **Migrate** button, which is what you actually click to migrate the application. The **Migrate** button will be unavailable if:
* The application cannot be migrated or has already been migrated to PMPC Cloud.
* You do not have the correct license for your PMPC Cloud Company.
By default the Publisher polls the ConfigMgr Site Database every 60 minutes for changes.
**Tip**
The following log files can be used for more information and for troubleshooting the migration feature:
`”%ProgramFiles%Patch My PCPatch My PC Publishing ServiceLogsPatchMyPC-AppMigrationService.log”`
`”%ProgramFiles%Patch My PCPatch My PC Publishing ServiceLogsPatchMyPC-CloudFileUploadBackgroundService.log”`
`”%ProgramFiles%Patch My PCPatch My PC Publishing ServicePatchMyPC.log”`
**Note:**
For new installations of Patch My PC Publisher, the **PatchMyPC.log** file will exist in the following folder:
`”%ProgramFiles%Patch My PCPatch My PC Publishing ServiceLogs”`