# Migrate an Application from ConfigMgr to Intune using Patch My PC Cloud App Migration

*Applies to: Patch My PC Cloud*

There are three different types of application migrations we currently support in Patch My PC (PMPC) Cloud, depending on the results of the Migration scan: 

* [Publish the App in Intune as a Suggested PMPC Catalog App](https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-suggested-app) 
* [Publish the App in Intune as a PMPC Catalog App](https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-catalog-app)
* [Publish the App in Intune as a PMPC Custom App](https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-catalog-app-1)

{% hint style="danger" %}
**Important**

As detailed in [Migration Requirements](https://docs.patchmypc.com/patch-my-pc-cloud/migration/requirements), to use the **Migrate** button to perform the migration, your PMPC Cloud Company must be using an Enterprise Premium license.
{% endhint %}

The process for starting a migration is the same regardless of the type of target app that will be created in PMPC Cloud/Intune. 

To perform a Migration: 

1. Sign in to your PMPC Cloud Company.
2. Navigate to **Migration**.<br>

   <div data-full-width="true"><figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FoIeOpg3GQkwVmddxa15Q%2Fimage.png?alt=media&#x26;token=9c575b99-b843-4301-97a2-5a01c3188e9f" alt="Begin an application Migration from the Migration tab" width="563"><figcaption></figcaption></figure></div>
3. Find the application you want to migrate.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FUodU4L7snI99IQrZiYPE%2Fimage.png?alt=media&#x26;token=88dc95f1-3daa-495c-b3c8-140cfc1fcd9a" alt="Select the application to migrate" width="563"><figcaption></figcaption></figure>

{% hint style="success" %}
**Tip**

You can use the **Search** box and start typing the name of the application to help you find it.

Alternatively, click the filter button and select the checkbox next to the **Match Type** of the application you wish to migrate (**PMPC App** or **Custom App**). Then, click **Apply All Filters** to view only the matching applications.
{% endhint %}

4. If a warning triangle is not present in the **Info** column for the application, go to step 11.
5. If a warning triangle is shown in the **Info** column, click it to open the application's properties.<br>

   <figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FuxtDkBVcpMs8oA17oLdE%2Fimage.png?alt=media&#x26;token=fc94f680-e830-4bf3-84ed-be9092d42150" alt="Understand if the migration will not include some properties"><figcaption></figcaption></figure>
6. In the application's properties, locate the tab(s) with a warning triangle beside them.<br>

   <figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FpGWmOFzeLq0TuyI3nH7W%2Fimage.png?alt=media&#x26;token=9e6e1ff3-8455-4171-916f-86be53ae1782" alt="Read and understand any warnings about the application to be migrated" width="563"><figcaption></figcaption></figure>
7. Click the relevant tab and look for the items with the warning triangle beside them.
8. Review the warning and determine your course of action.
9. If you are happy to proceed with the migration, go to step 11.
10. If you cannot proceed with the migration, close the application's properties and click **Cancel** to close the **Migration Wizard**. You now need to assess how to address the warnings to determine your next course of action for this application.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F3VTGgd7SywhezfoMEVIz%2Fimage.png?alt=media&#x26;token=0fe0de5e-eaf1-40de-b2ab-80d94877a576" alt="Click the Migrate button"><figcaption></figcaption></figure>

11. The behavior of the **Migrate** button depends on both the application **Match Type** and the **Migrate button** state shown in the UI. The image below highlights two possible Migrate button states:

    * **Button State 1 – Single Migrate button**\
      Clicking **Migrate** immediately starts the migration wizard.
    * **Button State 2 – Migrate button with dropdown**\
      Clicking **Migrate** displays additional options, allowing you to choose how the application should be migrated.

    <figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FlMOhWcGYc6WdAQqINWrN%2Fimage.png?alt=media&#x26;token=1585f325-b279-453e-9c68-8a9773ffee08" alt="Migrate Button State" width="184"><figcaption><p>Migrate Button State</p></figcaption></figure>

    Use the following sections to determine which action to take based on the application’s **Match Type** and the **Migrate** button state shown:

* [Match Type: Catalog App, Button State = 1](#match-type-catalog-app-button-state-1)
* [Match Type: Custom App, Button State = 1](#match-type-custom-app-button-state-1)
* [Match Type: Custom App, Button State = 2](#match-type-custom-app-button-state-2)

### **Match Type: Catalog App, Button State = 1**

If the application is identified as a **Catalog App**, click **Migrate** and follow the  [Publish the App in Intune as a PMPC Catalog App](https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-catalog-app) process.

### **Match Type: Custom App, Button State = 1**

If the application is identified as a PMPC Custom App and no alternative catalog match is available, the migration will proceed directly as a custom app. Click **Migrate** and follow the [Publish the App in Intune as a PMPC Custom App](https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-catalog-app-1) process.

### **Match Type: Custom App, Button State = 2**

If the application is identified as a **Custom App**, but a potential catalog match was identified based on application metadata instead of the file hash, the drop-down menu will present two options:

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FCA7Gu61H1Vi2LSg67zS5%2Fimage.png?alt=media&#x26;token=ef42563a-d6ce-48e8-a66d-9beeccfabf84" alt="two options in the dropdown if a potential catalog match was identified based on application metadata instead of the file hash, the drop-down menu" width="170"><figcaption></figcaption></figure>

* **Match to Catalog App -** Select this to migrate the application using the suggested catalog match and follow the [Publish the App in Intune as a Suggested PMPC Catalog App](https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-suggested-app) process.
* **Create a Custom App -** Select this to migrate the application as a PMPC Custom App and follow the [Publish the App in Intune as a PMPC Custom App](https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-catalog-app-1) process.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.