RMM Import and Export Tools Compared

At a glance

Compare vendor tools for moving RMM records and settings. Download earlier records you still need before deleting them or ending access.

Compare RMM import, export and migration tools by supported records, formats and permissions. Check which earlier records to save before switching.

Published Updated

On this page

Choose a tool for the data you need to move

Check the source Data Export guide, destination Data Import requirements, and RMM migration checklist. Linked vendor guides contain the procedures.

Inventory spreadsheets, configuration packages and agent installers serve different tasks. Check separately whether they transfer monitoring history or deleted records. Check the specific source and destination, and use the Deleted Device History guide.

Native tools by vendor

Choose by supported records and settings. Keep earlier history separately if the transfer excludes it.

Scroll horizontally on smaller screens to compare all four columns.

Native RMM and IT documentation import, migration and export methods
Vendor Native import/migration tools Native export tools Important limits and history gaps
Action1 Export guide; automation run evidence. CSV: endpoint group import assigns existing endpoints by name; agents must already be installed and the first column must be Endpoint Name. reports: Tools export saves endpoint report results as CSV or HTML. Group imports assign existing endpoints; agent installation is separate. Choose report scope and filters for the device details you need, and preserve earlier history before ending access.
Atera Import guide; export guide. CSV: import customers/sites, contacts/users and assets. Requires an administrator, eligible plan, current templates and parent records/asset types. reports/API: export FAQ describes operational CSV, analytical PDF/Excel and entity-specific JSON API exports. Asset import creates new records; duplicate serial numbers reject the entire file. No single all-data export; report limits and API scope differ. Use the API reference for entity-specific fields and pagination, and plan device history separately from customer and asset imports.
Automox Export guide; Worklet versions in Git. specialized CSV: Vulnerability Sync maps scanner findings for remediation; select the scanner's expected format and review unmatched findings and unknown devices. reports: reporting options include activity logs, patch-history/API-activity extracts and policy results. Vulnerability uploads allow up to one million rows. They are remediation inputs, not account/history imports. Choose the report and date range for the activity or patch history you need.
Datto RMM Import guide; configuration guide; export guide; patch statuses; job output. configuration packages: Monitoring policies use .pcy; components use .cpt. Check policy/component permissions. packages/reports: the same package tools export eligible items; Reports provides PDF reports and CSV exports, including device activity and change logs. Monitoring-policy targets are limited to Default Device Filters; custom Response settings and Antivirus Status, Component and Datto Continuity monitors are omitted. Imports default to Global scope. Copy eligible ComStore components to the library before export; licensing applies. Keep earlier monitoring history separately from these configuration packages.
Domotz Export guide; configuration guide. spreadsheet/configuration: Excel round trip edits device details. JSON settings import applies selected properties to target devices. Excel/JSON: the same instructions cover device-list/detail spreadsheets and device settings/properties such as names, locations, sensors and triggers. Excel transfers require the Domotz Pro Desktop App; ask Domotz about access if it is absent from your portal. Check the exported columns before a handover. JSON imports let you choose settings to override. Keep monitoring history separately from these device-detail and settings transfers.
Gorelo Export planning guide. CRM CSV/API overview: CRM overview describes bulk client/contact portability. Ask Gorelo for the template, required permissions and matching rules for your records. CRM CSV/API overview: the same overview describes bulk exports. Choose the RMM export guide for device and asset backups. The CRM overview covers client/contact transfers. For device, configuration or monitoring history, agree the transfer details with Gorelo and retain a source copy before cutover.
Hudu Import guide; export guide; IT Glue-to-Hudu guide. CSV: admin templates cover companies, articles, passwords and layout-based assets. Vendor-maintained migration tool: IT Glue-to-Hudu instructions link the Hudu-owned repository. CSV/PDF: Super Admin exports support selected/all clients, PDF handoffs and weekly global CSV to S3-compatible storage. CSV creates records rather than updating; use exact UTF-8 templates under 1 GB. Integration-card data is excluded from native exports; protect readable passwords. The migration tool requires source API access and compatible versions; permissions/share links do not migrate. Ask Hudu about checklist transfers if needed. Plan RMM monitoring history separately from documentation.
Level Export guide. library/CLI configuration: Resource Library imports supply automations, monitors and scripts. The Level CLI creates/applies automation specifications using an authenticated profile. CSV/CLI: Device Listing export includes filtered devices and all available columns. CLI exports device/alert/run CSV, JSON lists and YAML/JSON automation specifications. Group permissions and filters constrain device visibility. Keep earlier execution history separately from reusable library items and automation definitions. CLI apply can delete omitted triggers/actions and is not transactional: review its dry-run plan. CLI capabilities do not expand RMMBackup's public v2 API coverage.
N-able N-sight Export guide; offboarding guidance. Use the N-sight configuration guide for script and configuration files. Ask N-able which import method fits other records you need to move. XML/SQL: Asset Tracking data dumps export hardware/software inventory for all clients or one client, online or in the background. Asset Tracking inventory is not all RMM data. The offline link lasts 24 hours and requires the requesting account. Download before access ends. These are N-sight instructions; N-central is a separate product.
NinjaOne Import/deployment guide; export guide; script activity. CSV/deployment: organization CSV creation uses an organization template before separate agent deployment. Apps & Services imports documents using a selected template and required names. list CSV: Devices search has visible-column, all-details and custom-field modes. The dashboard catalog documents filtered Activities CSV export. All-details device CSV omits custom fields; a separate custom-field export exists. Check technician visibility, templates and licensing. Organization/document imports, agent installation and earlier monitoring history are separate tasks. Export Activities CSV separately for the event history you need.
OptiTune Export/API planning guide. technical API workflow: REST API offers selected group/account creation, metadata updates, file uploads and task creation. Generated API credentials and the account's role determine access. API retrieval: the same reference describes computer inventory, applications, updates, hardware, metadata, performance and stored-file downloads. Output handling requires technical work. API exports need a script or integration to save the returned data. For CSV imports or a platform move, ask OptiTune which files and records it can accept. RMMBackup saves supported data for browsing and download.
SuperOps Import guide; export guide. spreadsheet import: clients, requesters and sites accepts CSV, TSV, XLS, XLSX and XML, with header, column/value matching and review. report CSV: Data Reports selects assets, alerts, patches or client-related fields and filters; Export CSV emails a download link. Check required fields and duplicate handling in the import wizard before a large upload. Report columns and date/client filters determine output. Keep earlier device history and configuration copies separately.
Syncro Import guide; export guide; Atera-to-Syncro guide. CSV/native importer: organization templates and end-user CSV. The migration hub includes an Atera importer for selected client/contact records; agent deployment is a separate step. module CSV: Assets & RMM distinguishes all-assets Export from Export Displayed Columns; organization/end-user instructions cover their CSV tools. Organizations must precede end users; review identity/custom fields and update behavior. The Atera tool needs a source API key/rate limit; preserve history outside its listed records separately. Legacy “Export All Data” guidance remains vendor-marked unverified; use current module instructions first.

Keep transfer methods and preservation separate

Native CSV/spreadsheet tools move the listed objects and fields. Check required parents, encoding, duplicate behavior and current templates. Exporting a CSV does not prove a destination accepts it.

Native migration tools have a named source and destination, such as IT Glue to Hudu or Atera to Syncro. Follow the tool's own scope and linked maintained repository. An agent deployment script establishes destination management; verify historical transfer independently.

API/CLI workflows need a script or integration, suitable permissions and a place to save results. Support-assisted transfers need an agreed list of records, formats and delivery dates. For third-party services and community tools, check who maintains the tool and whether it supports your source, destination and product versions.

For configuration preservation, save package files, assignments, dependencies and omitted settings together. List the earlier device records, script runs, documentation links and deleted records you still need, then choose how to retain each one.

Preserve the records you may need later

RMMBackup saves successfully captured records for browsing, comparison and snapshot ZIP download. Examples include device inventory, alerts, available activity, Hudu documentation, and Automox policies, Worklets and available execution data. Coverage differs: Syncro policy-folder metadata is not a full policy definition; NinjaOne script metadata is not script source. Check supported backup data and the vendor guides.

Check each data type's result; a partial backup contains only successful captures. Back up before deletion or loss of access. Vendor APIs may limit available history. Snapshot ZIPs provide a reference, not a vendor restore/import package or endpoint-image backup. RMMBackup does not write to the destination.

Keep original native exports alongside any needed snapshot ZIPs before cutover. Product retention and plan rules determine accessible RMMBackup history; they do not extend the upstream vendor's history window. See available integrations for current connection availability and Beta qualifications, separately from the existence of native tools.

Related Action1 integration

Review current Action1 backup coverage and availability.

Related Atera integration

Review current Atera backup coverage and availability.

Related Automox integration

Review current Automox backup coverage and availability.

Related Datto RMM integration

Review current Datto RMM backup coverage and availability.

Related Domotz integration

Review current Domotz backup coverage and availability.

Related Gorelo integration

Review current Gorelo backup coverage and availability.

Related Hudu integration

Review current Hudu backup coverage and availability.

Related Level integration

Review current Level backup coverage and availability.

Related N-able N-sight integration

Review current N-able N-sight backup coverage and availability.

Related NinjaOne (formerly NinjaRMM) integration

Review current NinjaOne (formerly NinjaRMM) backup coverage and availability.

Related OptiTune integration

Review current OptiTune backup coverage and availability.

Related SuperOps integration

Review current SuperOps backup coverage and availability.

Related Syncro integration

Review current Syncro backup coverage and availability.