How to back up Hudu data
RMMBackup keeps a separate history of supported Hudu companies, assets, articles, procedures, users, networks, and relationships. You can also choose whether to include sensitive password and file collections.
Compare Hudu CSV, PDF, and weekly S3 exports with API scripts and recurring RMMBackup snapshots, including opt-in passwords and files.
On this page
Choose a Hudu backup method
| Method | Useful for | Important limitation |
|---|---|---|
| Native Hudu exports | Manual per-client or all-client CSV, selected PDF handoffs, and weekly global CSV exports to S3-compatible storage | Integration-card data is not exported; formats and included record types differ, and generated manual exports are temporary |
| REST API script | Retrieve documented JSON resources with a scoped API key | You must manage company scope, pagination, archives, rate limits, sensitive fields, binaries, storage, and completeness |
| RMMBackup (recommended) | Recurring dated backups, history you can browse and compare, deletion tracking, and complete backups you can download | Passwords and files are optional and must be explicitly enabled |
For ongoing protection, RMMBackup is the recommended option because it creates recurring, independently stored history instead of relying on one-time exports or a custom script. Hudu's Exporting Data guide documents the native formats and weekly S3-compatible export. Keep a native export workflow for offboarding, independent verification, and contingency planning.
See the Hudu integration for the Hudu data RMMBackup can back up, including optional password and file data.
What RMMBackup backs up from Hudu
| Collection group | Captured data | Boundary |
|---|---|---|
| Companies and assets | Companies, asset layouts and fields, active and archived assets | Company scope follows the API key; integration-card data is not promised |
| Knowledge and process | Articles, folders, procedures, procedure tasks, lists, flags, labels, expirations | Archived behavior varies by endpoint; archived articles lack a documented filter |
| People and organization | Groups and embedded members, users, roles represented in native responses | User activity fields can be volatile |
| Network and physical records | Websites, networks, IP addresses, VLAN zones, VLANs, rack storage and items, relations | Preserves documented native relationships, not a normalized replacement model |
| Integration metadata | Magic Dash and integration matchers | Limited to documented GET responses and discovered integration IDs |
| Opt-in sensitive and files | Passwords, password folders, photos, public photos, uploads, activity logs, existing export metadata | Off by default; file bytes are bounded and failures make the collection partial |
Password and OTP fields are preserved for backup fidelity only when the collection is selected and the key permits access. File manifests include byte count and checksum.
After each successful, complete Hudu backup, RMMBackup compares the captured records with the previous complete backup. New, changed, and missing records are shown as added, changed, or deleted. A failed or partial collection never creates deletion events or replaces the last complete comparison point.
Set up recurring Hudu backups
- Create and verify a RMMBackup account.
- Follow Hudu's official REST API key instructions.
- Create a least-privilege key for one Hudu instance, restrict companies and IPs as appropriate, and leave password access disabled unless it is explicitly required.
- In Settings > Integrations, choose Hudu, enter the HTTPS instance origin and key, then select core and any approved opt-in collections.
- Save and validate, run a manual backup, and inspect collection and file-download results.
- Compare representative companies and assets with a native Hudu CSV, then download and inspect the RMMBackup ZIP.
Free allows one accepted manual backup attempt per rolling 24 hours across the MSP account, keeps the latest fully successful snapshot accessible, and does not schedule automatic backups. Full Access allows two accepted manual attempts per rolling 24 hours for this vendor, keeps ongoing accessible history, and adds a daily automatic schedule after the first fully successful backup. Full Access is free during open beta; contact support to activate it. See pricing.
Browse history and export captured data
RMMBackup lets you browse earlier copies of Hudu records, compare changes, and download a complete copy of a backup. If you chose to include approved files, those successfully backed-up files are included too. See the Hudu export guide to compare RMMBackup history with Hudu CSV, PDF, and scheduled exports.
Passwords and files are included only when you choose them, keeping those sensitive backup sources under your control.
Preserve Hudu data before a migration
Run Hudu's native all-client CSV or relevant client export and a complete RMMBackup capture before removing access. Confirm whether passwords, files, archived records, and integration cards are needed, because each has a different path or gap. The migration checklist applies to preserved reference data; RMMBackup does not move it into another documentation platform.
Review historical Hudu records
If a record captured in an earlier complete backup is missing from a later complete Hudu backup, RMMBackup marks it as deleted while retaining the earlier version in backup history. Use the deleted-record overview and the retention guide to understand when earlier records remain available.
Frequently asked questions
Does Hudu have native automatic exports?
Yes. Hudu documents weekly global CSV exports to S3-compatible storage, along with manual CSV and PDF options for super admins.
Are passwords and files included in RMMBackup by default?
No. Passwords, password folders, photos, public photos, uploads, activity logs, and existing export metadata are opt-in collections.