RMM configuration backup and coverage
A useful RMM configuration backup records which settings were captured, how they were collected, and what remains missing. A device inventory alone does not preserve policy definitions, assignments, or every account setting.
Preserve RMM settings and configuration with available exports, repeatable snapshots, and a clear record of what each copy contains.
On this page
Inventory the configuration you depend on
Check the native configuration import and export methods for supported packages and omissions before treating a saved file as a portable configuration.
List policy definitions, assignments, overrides, schedules, and account settings separately. For each item, record its native identifier, customer or site scope, capture time, and the documented collection method. Keep application credentials in a separate secret store rather than configuration notes.
Choose an available collection method
| Method | What it can establish | Limitation |
|---|---|---|
| Vendor configuration export | The fields included by that export | Importability and omitted settings require separate checks |
| Official API read | The documented response for a resource | A list entry may not include a complete definition |
| Dated manual record | Settings an administrator inspected | Must be maintained and cannot promise automated restoration |
Use the vendor guides below to find the scripts, settings and configuration files you can save.
Compare historical settings
Preserve originals before and after an approved change. Compare the same native resource within the same provider account. Record assignment changes separately from definition changes: a policy can remain identical while applying to different devices.
RMMBackup coverage differs by provider: Syncro settings are limited to account, tab, and printing responses; Atera automation profiles and thresholds need separate copies; other available integrations have their own documented configuration collections and gaps. See current collections. No current integration promises complete policy backup or write-back support.
Plan for gaps and retention
Document missing fields and the person responsible for keeping manual records current. Verify access to stored copies before offboarding a platform. Link configuration evidence to data exports, and choose a retention period based on how far back you need to investigate changes. Historical records can assist review; recreating settings requires a separate vendor-specific process.
Before migration, pair this inventory with the comprehensive guides for Syncro, Action1, N-able N-sight, Hudu, Atera, SuperOps, Domotz, Level, or OptiTune. They distinguish native export coverage from RMMBackup collections and link the matching credential and deleted-record guidance.
Provider guides
Find your platform below for configuration files and the assignments or dependencies to keep beside them. Save the source version and capture date with each copy.
-
Atera
Atera configuration backup: preserving settings and policy evidence
Preserve Atera configuration history with dated policy records, assignments, and change evidence.
-
NinjaOne (formerly NinjaRMM)
NinjaOne configuration backup: custom fields and policy context
Preserve the supported NinjaOne custom fields and policy context you may need when reviewing earlier settings.
-
Datto RMM
Datto RMM configuration backup: monitoring policy exports
Preserve Datto RMM monitoring policies and keep a clear record of the settings included in each copy.
-
Domotz
Back up Domotz network and monitoring configuration
Preserve supported Domotz network, monitoring, alert, and device configuration in a separate history.
-
SuperOps
Preserve SuperOps configuration: scripts, policies and custom fields
Build a SuperOps configuration record from maintained source files and explicitly documented assignments.
-
ConnectWise Automate (formerly LabTech)
Back up Automate configuration: scripts, groups and dependencies
Build an Automate configuration package around verified script and group export tools.
-
N-able N-sight
Back up N-sight scripts and document monitoring configuration
Preserve script files while documenting the monitoring context needed to use them again.
-
Kaseya VSA
Back up Kaseya VSA policies, profiles and automation
Capture native VSA configuration files with version and dependency notes before making changes.
-
ConnectWise RMM
ConnectWise RMM configuration backup: policies and scripts
Preserve the settings, scripts and assignments your team would need to rebuild a ConnectWise RMM setup.