> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/scenarios/migrate-to-saas/migrate-express.md). # Express migration to SaaS Follow these steps to create a new cloud tenant, recreate all appropriate settings from your on-premises server, and redeploy clients to report to your new OneSite Patch - SaaS deployment. We recommend you engage [Adaptiva Customer Support](https://support.adaptiva.com/) for any large or complex migrations. ## Step 1 (Optional): Upgrade your Adaptiva server If you want to continue to see historical data in your patching dashboards from your on-premises environment, you will need to upgrade your Adaptiva server and set some Client Settings Policies. a. Upgrade your server to the latest build (at least *9.3.969*), see [Server Upgrade](https://docs.adaptiva.com/platform-install/platform-upgrade/upgrade-platform#server-upgrade) in the Platform Installation Guide. * You are not required to update your clients b. Use this guide to configure the following settings on the Adaptiva Server - [How-To: Change the Default Number of Days Before the Adaptiva Server Removes an Inactive Client](https://support.adaptiva.com/hc/en-us/articles/360001702311-How-To-Change-the-Default-Number-of-Days-Before-the-Adaptiva-Server-Removes-an-Inactive-Client): | Configuration | Description | Value | Required | | ---------------------------------------------------------------------- | ---------------------------------------------------------------- | ------------------------------------------ | -------- | | client\_data\_manager.inactive\_client\_duration | Number of days before the client becomes inactive. | 315,360,000,000 (10 years in milliseconds) | Required | | client\_data\_manager.inactive\_client\_detector\_recurrence\_interval | Number of hours (in milliseconds) before the client is detected. | 31,536,000,000 (1 year in milliseconds) | Optional | | client\_data\_manager.ignore\_client\_uninstall\_msg | Set to ignore client uninstall messages. | true | Required | ## Step 2. Create your new OneSite Patch SaaS instance You can create a new OneSite Patch instance in our [Cloud Portal](https://console.adaptiva.cloud). a. Navigate to `https://console.adaptiva.cloud` to register for a [new account](https://docs.adaptiva.com/cloud/signup). b. Create a [new Company](https://docs.adaptiva.com/cloud/create-company) - ensure that your contact info and company details are accurate before proceeding. c. Create a [new Tenant](https://docs.adaptiva.com/cloud/create-tenant) - you may need to create multiple Tenants depending on your environment. d. Add your [license](https://docs.adaptiva.com/platform-guide/license-solution) - your current license and key will work for OneSite Patch SaaS. ## Step 3. Record your on-premises Auto Remediation settings In your **on-premises** Adaptiva server, record your Auto Remediation settings. a. Navigate the Admin Portal at `https://:`. b. In the left pane, click **Auto Remediation**. c. Record the auto remediation settings for the **Critical**, **High**, **Medium**, and **Low** risk categories. d. Take note of any custom **Schedules**, **Roles** (notification and approval roles), vulnerability management integrations, and **Business Units**. ## Step 4. Manually replicate your Auto Remediation settings In your OneSite Patch - SaaS deployment, recreate all relevant settings from your on-premises environment: **Note**: You can identify custom items using the search filters: **Built Ins = False**. * Create [Business units](/patch/patching-fundamentals/business-units.md) * Create [Maintenance windows](/patch/advanced-settings/maintenance-windows.md) * Set [User interaction](/patch/advanced-settings/user-interaction-settings.md) settings * Create [Custom products](/patch/advanced-settings/customized-products.md) * Configure optional integrations: * [Integrate Falcon Spotlight](/patch/integrations/integrate-crowdstrike.md) * [Integrate Defender](/patch/integrations/integrate-defender.md) * [Integrate SentinelOne with OneSite Patch](/patch/integrations/integrate-sentinelone.md) ## Step 5. Migrate your clients to SaaS You will need to perform a clean installation of the Adaptiva client on all clients. You may want to roll out client deployments in phases, especially in production environments. Testing in a pilot group before a full rollout can reduce disruption. Ensure you maintain a rollback plan in case SaaS onboarding uncovers blocking issues. Navigate to the [Cloud Portal](https://console.adaptiva.cloud/) and perform the following steps: a. Install the Adaptiva client as a clean install * Install the Adaptiva client for OneSite Patch SaaS by following the steps in the [SaaS Client Installation](https://docs.adaptiva.com/platform-install/client-install-and-uninstall/client-install/client-install-saas). * Ensure you are using the `CLEANINSTALL=1` installer option (Refer to the [Unattended Installation MSI Command Line Parameters](https://docs.adaptiva.com/platform-install/client-install-and-uninstall/client-install/client-install-windows#unattended-installation-msi-command-line-parameters)). This will uninstall the existing client and reinstall the client configured for your SaaS tenant. b. Audit the client migration in the migration dashboard 1. Import the [Migration Dashboard](https://support.adaptiva.com/hc/en-us/articles/39338088765453-Import-Migration-Dashboard) and use this to confirm your on-premises clients migration to your OneSite Patch SaaS tenant. 2. Check that each client reports into the new SaaS instance. 3. Confirm patch compliance reporting and policy assignments match expectations. ## Post‑migration checks * Confirm all devices are actively reporting in the OneSite Patch dashboard. * Validate patching cycles are triggered and completed successfully. * Ensure alerting and reporting functions are operational. * Decommission on‑premises infrastructure once SaaS functionality is confirmed stable.