Skip to content
ProVal Technologies
407-588-0101
Facebook Twitter Instagram Linkedin Youtube
  • Home
  • Company
    • ProVal’s Journey
    • Approach
    • Culture & Values
    • Our Team
  • NOC SERVICES FOR MSPS
    • ConnectWise
      • ConnectWise Automate
      • ConnectWise RMM
      • ConnectWise Manage PSA
    • Kaseya
      • Kaseya VSA
      • Datto RMM
    • Managed Backups
    • 24×7 Monitoring
  • Careers
  • Resources
    • MSP Blogs
    • Your Tools. Our Experts.
    • MSP Webinars
    • Testimonials
  • Contact Us
  • Client Portal
Menu
  • Home
  • Company
    • ProVal’s Journey
    • Approach
    • Culture & Values
    • Our Team
  • NOC SERVICES FOR MSPS
    • ConnectWise
      • ConnectWise Automate
      • ConnectWise RMM
      • ConnectWise Manage PSA
    • Kaseya
      • Kaseya VSA
      • Datto RMM
    • Managed Backups
    • 24×7 Monitoring
  • Careers
  • Resources
    • MSP Blogs
    • Your Tools. Our Experts.
    • MSP Webinars
    • Testimonials
  • Contact Us
  • Client Portal

What to Consider When Migrating RMMs

  • May 5, 2022
  • Chase Murphy
  • Business Continuity, Business Intelligence, Business Value

Over the last few quarters, we have seen a lot of MSP partners switching their RMM tools. This is not a decision to be made lightly, there are a lot of factors involved in a making a switch. To try and simplify this a bit, we’ve generated a list of items that should be considered when switching RMMs. ProVal believes there are a few core pillars of an RMM and what it is supposed to do. These items are: (in no particular order) Patching, Reporting/Auditing, Monitoring, Automation, and Remote Access.

Patching

Patching, specifically Windows/Microsoft patching, is a core element to most RMM software. Most systems have things broken into two parts. One is the schedule of when patches are installed and how reboots occur. The second system is which patches are approved for installation.

  • Ensure the same functionality exists between both systems
    • Patch install policies (Timing of when patches are installed)
    • Reboot policies (Timing of how reboots occur on endpoints)
  • Review current patch install and reboot policies, by client, for configuration in the new system
    • Note: This is a good time to work on overall patching strategy and get schedules standardized if possible.
  • Review and ensure machine exceptions are maintained
  • Review patch approval and denial status between the two systems and ensure they match
  • Verify Windows 10 build upgrades are managed in the new system
  • Verify Third Party Patching configuration if present in the current RMM and migrate to the new RMM where possible

Reporting/Auditing

Most, if not all, RMMs have some core functionality around gathering data from machines automatically and displaying that information for all to see. The MSP will need to review what is gathered in the current tool versus data in the new tool to ensure there is no loss of data or loss of visibility to the data required for the team.

  • Review current scheduled reports
    • Review the content of these reports and ensure the new system has something similar
    • Match the schedules for the reports so there is minimal interruption in reporting for partners. Notify partners of the change so they are not surprised when a different report arrives.
  •  Auditing
    • Work with the team to understand what tools they are using to audit various thing in environments. (Software lists, hardware lists, patching metrics, etc.)

Monitoring

There are certain critical functions of all RMMs that will carry over, things like Offline Server notifications. There are some that are very specific to the MSP or to their end clients that may need to be migrated to the new system. It’s important to find these items and setup a plan to verify similar monitoring happens between the old and new RMM.

  • Review how the RMMs monitor scenarios and create parity between the two systems
  • Develop methods to bridge gaps between the two systems. An example of this is some RMMs use Event Logs for most alerting, and some use information in the database.

Automation

Most RMM systems have Automation as a core function. Automation can mean many things. It can be an automated audit gathering data from endpoint. It may be a monitor that looks for an issue on a machine and remediates that issue. It could be a script performing a disk cleanup and ticketing based on the results from the cleanup.

  • Audit the current system for scripting and ensure those items make it into the new system.
  • Review the new system to bridge gaps that were present in the old system.
  • Review machine groups / other machine organizational methods in the RMMs and understand their function.
    • Migrate the “automation” provided by these groups to the new RMM where necessary/possible.
  • Overall System configuration
    • Branding
    •  Templates/Policies/Onboarding/Offboarding
    • Automatic application of monitoring, alerting, scripting, etc by configuring the new environment to do this for you

Remote Access

Another pillar of RMMs are their remote access functions. When automation does not suffice, a human will need to get involved. It should be easy and secure to connect to endpoints using the RMM. Many RMMs have their own proprietary tools, and some do not.

  • Review current remote access configuration and considerations depending on what the tool can do
    • Deploying the remote access software (where applicable)
    • Configuring the centralized portal (where applicable)
    • Audit and review exceptions for sensitive machines. Ensure these configurations are still required or make it into the new RMM/Remote Access tool.
    • End user remote access to machines
      • If the current system allows for users to connect to their own devices remotely, it will be important to ensure that after the migration those functions are still available
    • Security Policies
      • Connection timeouts
      • Endpoint screen lockouts on disconnect or timeouts
      • Securing administrative consoles

Other Considerations

There is obviously a lot more to consider when transitioning RMMs beyond these functions. Above are just some of the core pillars of what an RMM does. Below we’ll outline some of the other items to keep in mind during the transition.

  • Agent Migration

    • How to migrate the agents so they end up in a similarly structured way in the new system (Client/Location vs Machine groups vs sites, etc.)
    • How, technically, to do the deployment.
      • In many cases, using the current RMM to install the new RMM’s agents.
  • User Permissions

    • All RMMs are going to have a unique approach to permissions in the environment. It is paramount to understand the differences between the two systems and ensure that the Principal of Least Privilege is followed in the new RMM.
    • Restricting access to certain information or machines and how to do that. Reviewing the current settings to ensure those are mapped to the new system. Especially in regulated industries like finance or healthcare.
  • Integrations

    • Verify or assess what currently plugs into the RMM and if the new RMM has the same functionality
      • If an integration doesn’t exist in the new system, how does this item need to be handled moving forward?
    • PSA Sync
      • Does the RMM sync up with your PSA to sync tickets, configurations/assets, contacts, etc?
  • Training

    • The MSP staff will require training on the new product. Who will train the staff and what content will they learn? (Likely a training program will need to be generated for each product switch.)
  • Maintenance

    • Many RMMs require some form of maintenance each month. Ensuring someone (or the vendor) is responsible for maintenance is important.
  • Other MSP Considerations

    • Are there any specific processes that are central to the current RMM that needs to be transitioned to the new RMM?
    • Does the current RMM provide value to other teams like sales/finance/marketing that will impact their work?
    • Security
      • Does the RMM meet or exceed the MSP’s security policy?
    • Insurance
      • Insurance firms / underwriters have been more cautious with RMMs since the Kaseya breach. It’s likely worth confirming with the insurance provider that premiums will not increase.

If you’re looking to make a change on your RMM, or have recently made a change, we hope the list will help you through the process.

Chase Murphy

Chase Murphy

Chase Murphy is the RMM practice leader at ProVal tech. He started with ProVal in 2016 as the RMM Administration practice at ProVal was launching. Since then, Chase has worked with hundreds of Managed Service Providers to understand their needs and improve their systems with automation and training. Chase also helps develop and manage the ProVal consulting team to ensure we’re delivering best in class service to ProVal’s partners.
PrevPreviousCentralized Services for Managed Service Providers
NextShould my RMM be On-Prem or SaaS?Next

Categories

Labtech
  • Mac Agent Functionality Within ConnectWise Automate
  • ConnectWise RMM vs Automate: Should I be using CW RMM?
  • ConnectWise Automate on Linux – Best Practices
  • ConnectWise Automate Maintenance Mode Explained Best Practice
  • Uninstalling and Offboarding Automate Agents
  • How to Set Up Automate users to use ConnectWise SSO
  • Windows 10 Build Upgrades are Inevitable – Use Kaseya/ConnectWise Automate to Deploy
  • Best Practice Naming of Patching Groups
  • Automate 12 Patch 9 Now Available!
  • 5 Tips for using the Report Center
  • See All Labtech Posts
Business Continuity
  • See All Business Continuity Posts
Proactive Maintenance
  • See All Proactive Maintenance Posts
Kaseya
  • What Should I be Automating in Kaseya VSA 9.5?
  • Security Best Practices for Kaseya VSA
  • Kaseya VSA: Software Management vs. Patch Management
  • Software Management Enhancements
  • Two-Factor Authentication in Kaseya VSA
  • Windows 7 & Windows 10 Multiple Builds End of Life – Upgrade Using Kaseya or ConnectWise Automate
  • Kaseya Network Monitor: Benefits & Features
  • Kaseya Patch 9.5.0.22 and Future Updates
  • Kaseya’s New State-of-the-Art Contemporary User Interface
  • Kaseya Product Release – April ’19
  • See All Kaseya Posts
Datto
  • Creating & Implementing a Disaster Recovery Plan
  • Disaster Recovery – Minimizing Impact of Downtime
  • Updating a Datto Device
  • Datto Agent Communication Errors
  • Datto
  • See All Datto Posts
StorageCraft
  • See All StorageCraft Posts

Get in touch today for MSP NOC Services

Contact Us

ProVal Technologies, Inc

498 Palm Springs Drive, Ste. 130
Altamonte Springs, FL 32701
United States
Phone: 407-588-0101

Facebook Twitter Instagram Linkedin Youtube
SOC 2 Certified Logo
Form CTA

©2023 ProVal Technologies, Inc All Rights Reserved.

Privacy Policy – Disclaimer

What to Consider When Migrating RMMs

Migration Checklist Blog (Newsletter)

I truly view ProVal as a partner and extension of my team, not as one of my vendors

When our NOC Manager left last fall we wanted to replace the position with an outsourced NOC to reduce headcount, and bring in an expert to both Labtech and our backup solutions. Bringing in ProVal Technologies was one of the best decisions we made last year and has paid for itself.During our first few monthly recurring Labtech admin meetings the ProVal team discovered incorrect settings and policies that were not applying correctly in our Labtech server. Things that we thought were automated and working were not. For example, there were multiple scripts and policies running but set to do nothing such as disk cleanup scripts. Cisco Umbrella was not configured correctly. Server alerting was not set right and the list went on.The backup team sends daily and weekly reports and updates that reduce my technicians time that we used to spend on backup or antivirus tickets that took forever and were tedious.ProVal also brings in great insights to our business and really cares about our success. They will frequently mention to me in meetings what new scripts they can import to make us more efficient or will schedule upgrades to our backups, Labtech, etc so I don’t have to worry. I truly view ProVal as a partner and extension of my team not as one of my vendors.

Chris-Warnick-Headshot
Chris Warnick
Vision Computer Solutions
Northville, MI

They will quickly become an extension of your team and your ROI will reflect the results

We have been a long time user of Labtech and had tried for many years to manage the product internally with no real success at the level we needed to make our solutions more efficient for our customers. Once we hired Vikram and his team at ProVal, it solved all our pain points with the product and we really felt like we were leveraging the tool as it was designed. If this sounds like you and it’s keeping you up at night, then you need these guys. They will quickly become an extension of your team and your ROI will reflect the results.

Bryan-Wolff-Headshot
Bryan Wolff
CEO, Wolff Logics LT Managed & Admin Services
Cedar Park, Texas

They work well, fast and on budget

We met Vikram from ProVal Tech at Gary Pica’s Shnizzfest a year ago. Vikram explained the advantage of having trained, certified personnel take care of our recent Automate implementation. Even though we had taken an implementation package from ConnectWise to start up the program, we felt many custom configurations we needed for our business were lacking. We hired ProVal Tech after Automate was installed to help us with this task. From sales to technicians everyone was professional and knowledgeable. Onboarding was simple, and well documented. Tools on the web were supplied while we did the work, and they allowed us to track what was done, and see the improvements in the environment. It was easy to reach any of the team members, for any concern or question – all answered with courtesy and smile. Once the work was finished, we were given some training and explanations, add to that documentation, about the work and the scripts and features added to the program. We have been happily working with Automate since then. We can only recommend this efficient team of people for any work into Automate: they work well, fast and on budget.

Ben-Prevost-Headshot
Ben Prevost
FarWeb IT
Sherbrooke, Canada