How to export and back up Domotz data

At a glance

Use Domotz's available export options for targeted needs, or use RMMBackup to keep repeatable snapshots of supported collectors, devices, inventory, network configuration, alerts, audits, and history. This guide explains the coverage and how to verify each captured collection.

Compare Domotz Excel device exports, reusable settings templates and RMMBackup snapshots of supported network records and history.

Published Updated

On this page

Export device details or reusable settings

The Domotz tools comparison distinguishes Excel device-detail transfers, JSON settings templates and unresolved desktop-app availability from monitoring history.

Domotz documents Excel device-detail export and import through its Pro Desktop App. Export a device list, preserve an original, and edit a copy for the documented round trip; confirm the current app's availability.

For configuration, its Device Management Overview describes JSON settings/property exports and selection of parameters to override on import. Review target identities and selected settings before applying a template. Neither workflow establishes transfer of historical monitoring data.

Define the account and collector scope

One RMMBackup Domotz connection belongs to one MSP and uses the collectors and organizations visible to its configured Public API key. Record the account-specific API Key Endpoint, intended organizations, expected collectors, plan, and feature set before capture.

Use native collector and device identifiers when checking results. Device names and IP addresses can change or be reused.

Export documented resource groups

Start with account scope and collectors, then traverse collector-scoped devices. Add inventory, applications, topology, policies, sensors, variables, alert configuration, audit data, and history needed by the recovery plan. Existing configuration-management history can include running or startup configuration bytes for supported devices; the backup does not trigger a new configuration capture.

The API uses more than one response pattern. Collector and some device-child lists use array pagination, while alerts and audit logs use count-bearing envelopes. Device lists are unpaged. A reliable exporter must preserve those distinctions instead of forcing every response into one guessed schema.

Respect usage limits and partial results

Domotz exposes account usage and concurrency information through its API. RMMBackup paces requests per MSP/provider connection, honors throttling responses, and uses bounded retry for transient network and server failures.

Plan-, permission-, and capability-dependent endpoints may fail for one collector or device while other scopes succeed. RMMBackup retains successful records and marks the collection partial. A partial result is not evidence that an absent resource is empty or deleted.

Verify the exported result

Confirm the expected collector count, inspect representative device and organization IDs, check every selected collection status, and compare important configuration or history records with Domotz. Open the downloaded ZIP and verify its manifest, records, response archive, and any selected configuration artifacts.

Keep the artifact encrypted and access-controlled because network inventory and configuration can be sensitive. See the Domotz integration, credential guide, and general export guide.

Keep restore expectations separate

RMMBackup is read-only. It does not activate collectors, initiate scans, run device commands, capture camera images, or write captured records back to Domotz. Treat the export as independently retained reference data, not an automated restore package.

Plan the next step

For a move, review destination import options, then use the RMM migration checklist. Check the selected native tool before transforming files; an export is not automatically a destination import package. The migration use case explains how successfully captured records remain useful as a separate reference within your plan's accessible history.

Frequently asked questions

Is there one Domotz Public API endpoint that exports the whole account?

The documented API exposes separate resources. A complete workflow must traverse the required account-, collector-, and device-scoped endpoints and record failures.

Does a RMMBackup ZIP import into Domotz?

No. The ZIP preserves captured JSON, a manifest, original API responses, and supported configuration artifacts for reference and independent retention.

Official source

Domotz Public API developer portal

Official Domotz reference for API authentication, resources, pagination, response shapes, and usage reporting.

Related Domotz integration

Review current Domotz backup coverage and availability.