> 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-publisher/manage/cloud-tab/application-migration.md).

# Application Migration section of Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

The **APPLICATION MIGRATION** section on the **Cloud** tab of Patch My PC (PMPC) Publisher helps you migrate applications from Microsoft Configuration Manager to Intune using the *Migration* feature of PMPC Cloud.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FpD22T2MahyDHMwFhJyYy%2Fimage.png?alt=media&amp;token=f787f576-5a81-41e9-a377-5c91b8e152be" alt="&#x27;APPLICATION MIGRATION&#x27; section" width="563"><figcaption></figcaption></figure>

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

You will be unable to enable the **Application Migration** feature until you have connected Publisher to your PMPC Cloud company as detailed in [Connect Publisher to Patch My PC Cloud](/patch-my-pc-publisher/manage/cloud-tab/cloud-connection.md#connect-publisher-to-patch-my-pc-cloud).
{% endhint %}

When the **Application Migration** option is enabled, Publisher inventories ConfigMgr applications and makes them available for migration to Intune through PMPC Cloud.

Discovery runs automatically every 60 minutes. Migration status and the number of discovered applications are shown for visibility and validation.

{% hint style="info" %}
**Note**

See [Setting Up ConfigMgr to Intune App Migration](/patch-my-pc-cloud/migration/setting-migration.md) for more details on setting up the Application Migration feature
{% endhint %}

## App Migration Database

When an app migration inventory runs, Publisher saves the inventoried ConfigMgr results in the Publishing Service's installation folder under the **Database** subfolder.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FxUtcDK8kVhmNOgCsaqiv%2Fimage.png?alt=media&amp;token=1862b87f-ea26-4d2d-a29b-56e34fcaa7f6" alt="Migration Database" width="563"><figcaption></figcaption></figure>

This folder contains two files:

* **AppMigration.db** stores the app migration inventory data and processing state.
* **existingApps.json** contains a JSON copy of the discovery data.

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

For reliability, consider excluding the **AppMigration.db** file from antivirus or endpoint protection scanning. This prevents the **AppMigration.db** file from being locked during scheduled scans, which can cause inventory or migration operations to fail.
{% endhint %}


---

# 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-publisher/manage/cloud-tab/application-migration.md?ask=<question>&goal=<user_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.