> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-suggested-app.md). # Publish the Migrated App in Intune as a Suggested Patch My PC Catalog App *Applies to: Patch My PC Cloud* When migrating a Configuration Manager (ConfigMgr) application as a suggested Patch My PC (PMPC) Catalog App, the migration flow depends on how many catalog matches are found. If multiple PMPC Catalog Apps match the ConfigMgr application, you are first presented with the **Matched App** step, which allows you to review the available matches and select the PMPC Catalog App to migrate to.
Multiple suggested apps identified
After you select the appropriate match, the migration continues into the deployment flow with the selected application pre-selected.
Migration deployment flow
If only a single unique PMPC Catalog App match is identified, the **Matched App** step is skipped entirely and the migration moves straight into the deployment flow with that application automatically pre-selected.
Single suggested app is matched
{% hint style="info" %} **Note** Where possible, details such as architecture and installer type are inferred from the original ConfigMgr application and populated automatically to reduce manual configuration. {% endhint %} From this point, continue following [Publish the App in Intune as a PMPC Catalog App](/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-catalog-app.md), where the remaining steps of the deployment flow are completed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.patchmypc.com/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-suggested-app.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.