How to export and back up Hudu data
Use Hudu's native exports for targeted or scheduled copies, or use RMMBackup to keep repeatable snapshots of supported companies, assets, documentation, relationships, and explicitly selected password or file data.
Back up Hudu companies, assets, articles, procedures, network documentation, relationships, and approved sensitive or file sources.
On this page
Choose a native documentation export
Compare Hudu exports, CSV imports and its IT Glue migration tool before choosing a documentation handoff method; export and import scopes differ.
Hudu's Exporting Data guide documents Super Admin CSV and PDF exports, plus weekly global CSV delivery to S3-compatible storage. Choose client scope and included information, download temporary files promptly, and protect exports containing readable passwords. Verify a sample of articles, assets and relationships before relying on a handoff.
Define the Hudu scope first
One RMMBackup Hudu connection represents one Hudu instance and every company visible to its API key. Use a least-privilege key and document whether company access is intentionally restricted. Reduced visibility is not proof that a record was deleted.
The connection URL should be the HTTPS instance origin, such as https://your-company.huducloud.com; /api/v1 is optional. Keep the API key separate from backed-up Hudu payloads and exports.
Select documented collections
Core sources include companies, asset layouts and assets, articles and folders, procedures and tasks, groups and users, websites, networks, IP addresses, VLANs, rack storage, relations, lists, flags, labels, expirations, and integration matchers.
Hudu does not expose every collection with the same pagination, archive, or detail behavior. RMMBackup handles those contracts per endpoint and preserves list and detail responses. After a complete collection backup, it compares the result with the previous complete capture and tracks added, changed, and deleted records. Failed or partial collections do not create deletions or replace the comparison baseline.
Approve sensitive and file data separately
Passwords and password folders are opt-in and require the corresponding Hudu key permission. Password and OTP fields are preserved for backup fidelity when selected, so production object encryption, access controls, and encryption-key recovery must be approved first.
Photos, public photos, and uploads are also opt-in. RMMBackup stores bounded opaque bytes with byte counts, SHA-256 checksums, and a file manifest. A failed selected download makes that collection partial rather than silently complete.
Verify the snapshot export
After a staged backup, confirm the expected companies and collections, inspect representative native records, and download the RMMBackup snapshot ZIP. Check its manifest, collection statuses, original API responses, and any selected binary manifests.
Keep RMMBackup ZIPs distinct from Hudu-native exports. RMMBackup does not initiate native exports or write records back to Hudu. See the Hudu integration page, data export overview, and backup retention guide.
Plan the next step
For a move, review Hudu import options and IT Glue-to-Hudu planning, 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
Does RMMBackup create a native Hudu export?
No. It captures documented GET data into RMMBackup snapshots and never initiates a Hudu-native export.
Are Hudu passwords and files backed up automatically?
No. Passwords, password folders, photos, public photos, uploads, activity logs, and existing export metadata are off by default and require explicit selection and suitable API-key permissions.
Official source
Official Hudu documentation for API-key authentication, scope, pagination defaults, and rate limits.