# Enterprise migration to SaaS Follow these steps to create a new cloud tenant, migrate any settings from your on-premises server, and redirect clients to your new cloud tenant. 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. (Optional) Migrate custom workflows used for patching a. Identify any custom workflows that you are using in your patching implementation. * Under **Workflows**, search both the **Workflow Designer** page and the **Workflow** **Activities** page by using the search filter **Built Ins = False**. ![](/files/pthHMfzLwld9Dcg7jqDU) b. Export custom workflows. * For each workflow, click the ellipsis **(...)** and click **Export**. c. Submit a ticket to [Adaptiva Support](https://adaptiva.com/support) to review and sign each custom workflow. d. Import Workflows into your tenant Once you have received your signed workflows from Adaptiva, follow these steps to import your workflows into your Patch tenant - [Import a Workflow](https://docs.adaptiva.com/platform-guide/how-to-import-workflow). ## Step 4. Manually Replicate Configuration Settings In the [OneSite Cloud Portal](https://console.adaptiva.cloud), recreate all relevant settings from your on-premises environment: {% hint style="info" %} Identify custom actions and sensors to be recreated using the following search filters: * Under **Actions**, create a search filter for **Built Ins = False**. * Under **Sensors**, create a search filter for **Built Ins = False**. {% endhint %} * Set [User interaction settings](/patch/advanced-settings/user-interaction-settings.md) * Customize [Schedules](https://docs.adaptiva.com/platform-guide/platform-features/schedules) * Create [Maintenance windows](/patch/advanced-settings/maintenance-windows.md) * Define [Custom actions](https://support.adaptiva.com/hc/en-us/articles/4895992813709-Actions-and-Action-Factories) and [Custom sensors](https://support.adaptiva.com/hc/en-us/articles/4868465121293-Sensors-and-Sensor-Factories) * Create notification and approval [Chains](/patch/advanced-settings/chains.md) * Create deployment and notification [Bots](/patch/advanced-settings/bots.md) * Create [Custom products](/patch/advanced-settings/customized-products.md) * Create custom [Patch deployment](/patch/advanced-settings/bots.md#deployment-bots) or [Rollout process](/patch/advanced-settings/rollout-processes.md) for your imported workflows * 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) * Create [Business units](/patch/patching-fundamentals/business-units.md) * Configure [Deployment waves](/patch/advanced-settings/deployment-waves.md) * Create your [Patch strategy](/patch/patching-fundamentals/patch-strategies.md) ## Step 5. Migrate your clients to SaaS You will need to perform a clean installation of the OneSite Patch SaaS client on all devices. 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. Log in to the [Cloud Portal](https://console.adaptiva.cloud) and perform the following steps: a. Install the SaaS 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. c. Audit the client migration in 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.adaptiva.com/patch/scenarios/migrate-to-saas/migrate-enterprise.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.