Skip to main content

NinjaOne Backup — Decommissioning MSP360 at a Migrated Site

Audience: T2 Use when: NinjaOne Backup is verified working at a site and it's time to cleanly remove MSP360.

Do not decommission MSP360 until the migration verification checklist has been completed and the site tracker is updated. Removing MSP360 before NinjaOne is confirmed working leaves the site unprotected.

Pre-Decommission Checklist

Before removing anything:

  • Migration verification checklist completed for this site
  • At least 2 consecutive successful NinjaOne backups (local + cloud) confirmed
  • Test file restore from NinjaOne verified
  • Nate or Josh notified if the client has any data retention obligations for old MSP360 cloud data

Step 1 — Stop and Disable MSP360 Backup Jobs

Before uninstalling the agent, stop any active MSP360 jobs to avoid conflicts:

  1. Log into the MSP360 management portal
  2. Navigate to the client → find all active backup plans
  3. Disable or delete each backup plan for this site's devices
  4. Confirm no active jobs are running

Step 2 — Uninstall the MSP360 Agent From All Devices

Run this on each device at the site via NinjaOne terminal:

# Find MSP360 / CloudBerry / MBS agent
$agents = Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
    "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object {
    $_.DisplayName -like "*MSP360*" -or
    $_.DisplayName -like "*Cloudberry*" -or
    $_.DisplayName -like "*Managed Backup*" -or
    $_.DisplayName -like "*MBS*"
} | Select DisplayName, UninstallString

$agents | Format-Table -AutoSize

If found, uninstall via Programs and Features or using the UninstallString silently:

# Silent uninstall (modify the string based on output above)
# Example format:
Start-Process -FilePath "msiexec.exe" -ArgumentList "/x {PRODUCT-GUID} /quiet /norestart" -Wait

# Alternatively — use Add/Remove Programs if the GUID approach fails

After uninstalling: reboot the device, then confirm MSP360 is gone:

Get-Service | Where-Object {$_.DisplayName -like "*MSP360*" -or $_.DisplayName -like "*Cloudberry*" -or $_.DisplayName -like "*MBS*"}
# Should return nothing

Step 3 — Remove MSP360 VSS Provider (If Present)

MSP360 registers a VSS provider that can conflict with NinjaOne Backup even after the agent is uninstalled:

# Check for lingering VSS providers
vssadmin list providers

# Look for any provider with "CloudBerry", "MSP360", or "MBS" in the name
# If found — this needs to be removed. Contact NinjaOne support or escalate to T3 for registry-level removal.

Most cases: the MSP360 uninstaller removes the VSS provider automatically. Check anyway.

Step 4 — Confirm No MSP360 Scheduled Tasks Remain

Get-ScheduledTask | Where-Object {
    $_.TaskName -like "*MSP360*" -or
    $_.TaskName -like "*Cloudberry*" -or
    $_.TaskName -like "*MBS*"
} | Select TaskName, State

# Remove any found
# Unregister-ScheduledTask -TaskName "TaskNameHere" -Confirm:$false

Step 5 — Old Cloud Data Retention Decision

MSP360 backup data in Backblaze S3 is not automatically deleted when the agent is removed. Discuss with Nate:

  • Active Veeam BDR site: Old MSP360 data can be expired after 30 days — covered by Veeam
  • NinjaOne-only site: Old MSP360 cloud data can be expired once 2+ weeks of NinjaOne cloud backups are confirmed
  • Archive requirement: Some clients may have a contractual or compliance reason to retain old backup data longer — confirm before expiring

Update the Backblaze or S3 bucket lifecycle policy for this site's bucket to expire data after the agreed retention period.

Step 6 — Update the Migration Tracker and Remove from MSP360 Portal

  1. SharePoint migration tracker: update status to Decommissioned
  2. MSP360 portal: remove the site/devices from MSP360 management (don't leave ghost devices)
  3. NinjaOne: confirm devices are cleanly enrolled and showing healthy backup status

Post-Decommission Verification

Run a final backup in NinjaOne after the MSP360 removal and reboot:

  • Confirm Lockhart is still running and healthy
  • Confirm the backup job completes successfully
  • Confirm no new VSS errors appeared (old MSP360 VSS provider conflict can surface post-uninstall)
Back to top