Express migration to SaaS

This guide is intended to help customers using OneSite Patch Express on-premises to move to a OneSite Patch - SaaS deployment.

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 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 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:

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.

a. Navigate to https://console.adaptiva.cloud to register for a new account.

b. Create a new Company - ensure that your contact info and company details are accurate before proceeding.

c. Create a new Tenant - you may need to create multiple Tenants depending on your environment.

d. Add your license - 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://<AdaptivaServerName>:<port>.

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

• Create Maintenance windows

• Set User interaction settings

• Create Custom products

• Configure optional integrations:

  • Integrate Falcon Spotlight

  • Integrate Defender

  • Integrate SentinelOne with OneSite Patch

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 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.

• Ensure you are using the CLEANINSTALL=1 installer option (Refer to the 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 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.