> 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/setting-migration.md).

# Setting Up ConfigMgr to Intune App Migration for Patch My PC Cloud

*Applies to: Patch My PC Cloud*

Before you can perform a migration using the Patch My PC (PMPC) Cloud *Migration* feature, you need to ensure that Publisher is connected to the same PMPC Cloud Company that you plan to migrate the objects to.

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

See [Add a Connection](/patch-my-pc-cloud/manage/settings/connections/add-connection.md) for further details.
{% endhint %}

You also need to ensure that the **Enable application migration** checkbox on the **Cloud** tab is checked.

{% hint style="info" %}
**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](/patch-my-pc-cloud/migration/requirements.md).

Also, if the [Publisher was connected to the Cloud](https://docs.patchmypc.com/patch-my-pc-publisher/administration/cloud) more than 90 days ago, you may be prompted to sign in again using an account that has access to the Cloud Portal.

This is expected behavior as we do not control the authentication token, and once it expires, it must be renewed by re-authenticating.
{% endhint %}

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FcqiK6gL1gCpWApWzP5kO%2Fimage.png?alt=media&amp;token=ed4f0a37-6ed3-47de-8dd4-76c7c675f2f0" alt="&#x27;Enable Application Migration&#x27; checkbox is checked on the &#x27;Cloud&#x27; tab" width="563"><figcaption></figcaption></figure>

By default, Publisher polls the ConfigMgr Site Database every 60 minutes for application changes.

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

If you click **Disconnect** on the Publisher's **Cloud** tab, all of the Migration features data will be deleted from your PMPC Cloud company. You should therefore avoid doing this until you have completed the migration of all required items from ConfigMgr to PMPC Cloud.
{% endhint %}

Next, sign in to your PMPC Cloud company and verify that the **Migration** node is visible in the Cloud Portal.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F92h9XNcKhZ0zVsXBd92X%2Fimage.png?alt=media&amp;token=0a61944a-cb9c-4cf5-8edb-57c9409f67fe" alt="&#x27;Migration&#x27; node" width="563"><figcaption></figcaption></figure>

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

The following log files can be used for more information and for troubleshooting the migration feature:

`"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs\PatchMyPC-AppMigrationService.log”`

`"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs\PatchMyPC-CloudFileUploadBackgroundService.log”`

`"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\PatchMyPC.log”`
{% endhint %}

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

For new installations of Patch My PC Publisher, the **PatchMyPC.log** file will exist in the following folder:

`"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs"`
{% 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-cloud/migration/setting-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.