Import Datto RMM components and monitoring policies

At a glance

Datto RMM supports component packages and monitoring-policy imports. These transfer specific configuration, with important policy exclusions and target checks. They are separate from device history and from Autotask PSA imports.

Transfer Datto RMM component and monitoring-policy packages, inspect documented exclusions, and validate scope before applying configuration.

Published Updated

On this page

Import component packages

The Datto RMM portability comparison separates configuration package imports from report/history exports and highlights package exclusions.

The Component Library imports .cpt files. Export a component from its row action, then import and review it in the destination library. ComStore components must first be copied into the library to be exportable; an unavailable Export action means that entry cannot be exported through that action.

Inspect script parameters, dependencies and intended targets before using an imported component. Keep its source package with your migration notes.

Review monitoring-policy exclusions

Datto's Policies documentation describes .pcy monitoring-policy packages. Imported policies default to Global scope. Exported targets are limited to Default Device Filters; custom Response configuration is omitted. Antivirus Status, Component and Datto Continuity monitors cannot be exported.

Review scope, targets, alerts and omitted responses before enabling the destination policy. A successful file import does not prove equivalent monitoring behavior.

Distinguish a platform migration

For a move from VSA 9, start with Datto's migration page and confirm the transfer scope and prerequisites with Kaseya. Plan device history separately from the component and policy packages described above.

Autotask is a separate PSA product. Its record importers are not evidence of Datto RMM historical-data import.

Validate and preserve your reference

Use the Datto RMM export guide for reports and identity records, and the migration checklist for a pilot and cutover. Compare intended targets with actual policy application and review alert routing and component behavior.

The Datto RMM Beta integration preserves supported records and component metadata. Native .cpt packages serve a different purpose from that metadata. RMMBackup does not execute configuration imports. Check plans for history access and the migration use case for keeping captured records useful later.

Official source

Datto RMM Component Library

Related Datto RMM integration

Review current Datto RMM backup coverage and availability.