How to export and back up OptiTune data
Use OptiTune's available export options for targeted needs, or use RMMBackup to keep repeatable snapshots of supported inventory, configuration, tasks, files, alerts, and history. This guide explains the coverage and how to verify each captured collection.
Export documented OptiTune computer inventory, groups, metadata, tasks, deployments, files, alerting configuration, alerts, and audit history.
On this page
Separate API exports from task imports
The OptiTune tools comparison covers API exports and reusable tasks so you can choose the right method for your move.
OptiTune's REST API guide documents inventory retrieval and other operations governed by the account's role. The existence of creation operations does not establish a ready-made migration tool. Its prepackaged-task workflow imports selected library tasks after reviewing their details and storage needs.
For a move to OptiTune, ask the destination vendor which records it can accept and which templates or tools to use. Keep an independent copy of source history while planning the import.
Define the OptiTune export scope
One OptiTune connection belongs to one RMMBackup MSP and keeps a separate provider history. Record the OptiTune account type, expected computer and group counts, selected collections, and whether the credentials are intended to see one organization or master-administrator organization resources.
OptiTune documents Basic authentication and says available methods depend on account type. Use dedicated credentials generated from My Account, then grant only the access needed for the selected read resources. See the OptiTune API credential guide.
Export documented resources
| Area | RMMBackup capture | Relationship preserved |
|---|---|---|
| Inventory | Computers, computer detail and hardware, installed applications, Windows update catalog/state/history, malware, endpoint protection, and retired computers | Native computer, organization, update, and threat IDs |
| Organization | Accounts, optional master-administrator organizations, business entities, group hierarchy and membership, local users, computer metadata, and metadata prototype | Organization, parent-entity, parent-group, group, account, and computer IDs |
| Automation configuration | Script, install, repair, uninstall, system, and favorite tasks; deployments and results | Task, group, deployment, and computer IDs; schedules remain embedded |
| Files | File metadata/details and opt-in bytes from the documented DownloadUrl field |
File IDs and related task, installer, settings, and brand IDs |
| Alerting and history | Alert subscriptions, event categories/descriptors/sources, notification groups and members, mail templates, webhooks, paginated alerts, group settings, optional organization/billing/CloudBerry settings, and bounded history | Native group, template, event, account, plan, and target IDs |
| Branding and definitions | Brands, brand domains, Windows Event Log names, Windows Update categories, and optional product keys | Native brand, file, domain, event-log, update-category, and parent-category IDs |
The Files collection is opt-in because it can transfer substantial data. Downloads require HTTPS, use bounded sizes and redirects, sanitize archive filenames, and never send OptiTune Basic credentials to a different host.
Verify collection completeness
OptiTune's Swagger documents explicit page parameters only for alert instances. RMMBackup walks those pages until a short page is returned, rejects repeated alert IDs, and marks the collection partial if pagination or detail retrieval fails. Other documented list operations return arrays without page parameters; RMMBackup stores those arrays exactly as returned instead of inventing pagination.
OptiTune does not publish a fixed numeric request allowance in its public API documentation. RMMBackup therefore uses conservative pacing and bounded retries instead of assuming an account-wide limit.
For computer-, group-, and deployment-scoped resources, a failure after completed scopes retains the successful records but marks the collection partial. Partial and failed captures cannot become deletion baselines. Deleted-computer navigation is based only on complete successful Computer captures for the same OptiTune provider connection; retired computers remain a separate native resource.
Download and review the snapshot
After a backup, inspect collection statuses and compare expected computer, group, task, and file counts. Sample hardware details and relationship IDs, then request the full snapshot ZIP. The archive includes a manifest, record JSON, original OptiTune response files, and selected stored-file bytes with checksum metadata.
The ZIP is not an OptiTune import package. RMMBackup does not create or execute tasks, run scripts, open remote sessions, install software or updates, modify configuration, or restore records. Review the OptiTune integration and backup setup guide before relying on the capture.
Understand historical boundaries
Audit capture defaults to the previous 30 days to avoid collecting unbounded operational history on every backup. Windows event logs, agent state, connection state, benchmarks, and performance data are not collected because they are high-volume or continuously changing telemetry. Vendor retention and credential visibility still determine how much historical data the API returns.
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 OptiTune endpoint that exports the entire account?
No. The documented REST API exposes separate inventory, configuration, task, file, alert, and history resources with account-type-dependent access.
Does an RMMBackup OptiTune ZIP restore into OptiTune?
No. The ZIP is an independently retained, read-only snapshot artifact for browsing, comparison, and download.
Does RMMBackup execute OptiTune tasks or scripts?
No. The integration uses documented GET operations only and does not invoke any remote or write action.
Official source
OptiTune REST API V1 Swagger definition
Official downloadable Swagger contract for OptiTune's documented API resources, authentication scheme, request parameters, and response models.