Migration to Cloud

That is a fairly simple task but could require a redeployment.
To be honest, I have not tested whether installing the Package Manager would take over and ensure the EPM Client is upgraded, the Console Adapter is installed, and the adapter is switched to the PM Cloud. It would be worth testing to save time.
Some things to think about:

• Create your computer groups: Test, Pilot, Production.
• Upload your old policy, or consider upgrading to a new QS and adding your current rules and configuration; the QS policy has evolved.
• Ensure auditing goes to PM Cloud Analytics for the items we need to audit.
• Manage versions using Package Manager or the deployed Client and Adapter from SCCM or similar (controlled by your computer groups if using the Package Manager, with Password Safe integration).
• When switching from on‑prem to cloud, does that also include migrating users from AD to Entra ID?
• If so, adjust Workstyles filters. If a user SID is S-1-5, it indicates on‑prem AD; if a user SID starts with S-1-12, it will need Entra ID filters.
• Deploy the Package Manager and use computer groups for Production so new clients receive the Production policy.

You can export your current policy and import it to the PM Cloud. When adding the policy to PM Cloud, set the options for what information you want in PM Cloud Analytics. Your old on‑prem setup relies on Raise an Event, which PM Cloud still uses, but you will have to enable additional reporting events to ensure they are visible in Analytics.
I strongly recommend creating a new QS policy to take advantage of new rules and features, then migrate your current settings into that policy.
The MMC snap‑in can be useful for that part.

Good luck

Jens