CHANGE THE PLATFORM. KEEP THE CONTROL.

THE PROBLEM.

Moving patching between platforms needs more than copying schedules. Both tools must agree on device scope, and only one should own patching for a given device.

MY ROLE.

I supported a pilot migrating Windows workstation patching from Automate to ConnectWise RMM, working through scope, policy packages, reporting and rollback.

HOW IT WORKED.

1. Understand existing behaviour

   Review policies, company and site scope, workstation separation and exceptions.

2. Move ownership deliberately

   Prepare reusable OS and third-party patching policies and prevent both RMM tools from patching the same endpoints.

3. Validate the pilot

   Review results and reporting, then preserve a route back to the previous patching ownership.

MAKE IT TRUSTWORTHY.

This work was a pilot. Device membership, ownership and reporting were central validation points. Expanding a migration means verifying those controls on the pilot before bringing more sites into scope.

Controls that matter

• Explicit company and site scope
• Workstation / server separation
• Single patching owner
• OS and third-party validation
• Reporting and rollback procedures

WHY IT MATTERS.

Policy targeting, ownership, exceptions and validation are architectural skills that transfer across RMM products. That includes platforms such as Datto RMM and NinjaOne; this project is not a claim of direct Datto experience.