How to back up Syncro data
RMMBackup keeps a separate history of supported Syncro business records and managed asset details, including Windows patch status, installed applications, local administrators, BitLocker/TPM state, and referenced recovery passwords returned by Syncro. Use the guide below to compare backup options, connect Syncro, and verify your first snapshot.
Compare Syncro exports, API scripts, and recurring RMMBackup snapshots for customer, asset, Windows patch, security, documentation, settings, and alert data.
On this page
Choose a Syncro backup method
| Method | Useful for | Important limitation |
|---|---|---|
| Native Syncro exports | Separate CSV exports for organizations, end users, assets, inventory, and other report modules | Syncro's Export All Data guide documents separate export paths rather than one export-all action |
| API script or Database Exports | Repeatable reads or scheduled synchronization of selected documented objects | You must handle permissions, pagination, storage, failures, and field coverage |
| RMMBackup | Repeatable Syncro snapshots, original captured records, browsing, comparisons, and complete snapshot ZIPs | Coverage and history follow the supported data and plan details below |
A one-time CSV describes the selected live view at export time. A recurring independent backup creates separate dated captures and can retain earlier versions while those snapshots remain accessible.
See the Syncro integration for the Syncro data RMMBackup can back up.
What RMMBackup backs up from Syncro
| RMMBackup collection | Captured Syncro data | Boundary |
|---|---|---|
| Customers | Customer list and details, including disabled customers | Limited to fields returned by documented reads |
| Policy Folders | Paginated folder metadata for each customer | Complete policy definitions are not captured |
| Contacts | Contact list and details | Visibility follows the token and account |
| Assets | Asset list and details, chat metadata, and contact relationships | Only records returned while the asset exists can be captured |
| Windows Patches | Installed patches plus available, failed, and rejected patch status for each asset | Pagination is limited to the response returned by the documented operation |
| Installed Applications | Paginated installed-application inventory for each asset | Visibility follows the token and asset |
| Local Administrators | Local administrator accounts reported for each asset | Only accounts returned by Syncro can be captured |
| BitLocker & Recovery Keys | BitLocker volumes, TPM state, key identifiers, and referenced recovery passwords | Password reads require a separate permission and create Syncro audit events |
| Wiki Pages | Page lists and page details | Attachments are not separately promised |
| Settings | Account, tab, and printing responses | Not a complete account-configuration export; deletion inference is disabled |
| RMM Alerts | Paginated active and resolved alerts | The list operation is captured in full on each run |
RMMBackup preserves Syncro records in their original structure, keeping the details needed for browsing, comparison, and export.
The five asset-related sources are independently selectable. Device History uses Assets as the device identity and associates changes from the four related sources by Syncro asset ID.
Set up recurring Syncro backups
- Create and verify a RMMBackup account.
- Follow the Syncro API key guide to create a separate least-privilege key and identify the account subdomain.
- In Settings > Integrations, select Syncro, enter the subdomain and key, and choose the supported collections you need.
- Save, run connection validation, and enable the connection only after validation succeeds.
- Start Back Up Now, wait for the durable job to finish, and inspect every collection result and representative record.
- Download a snapshot ZIP and compare it with a native Syncro export before relying on the workflow.
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
Authorized users can browse captured records, search supported fields, compare versions, review meaningful changes, and download a complete Syncro snapshot ZIP. The ZIP includes a contents summary, captured records, and preserved source responses. See the Syncro native export guide and RMMBackup export overview.
BitLocker recovery passwords are retained in the BitLocker & Recovery Keys record and preserved source response. They are also included in authorized snapshot ZIPs. Store downloaded exports as securely as the credentials they contain.
A failed collection does not establish deletions or become the next comparison baseline. Successful collections in a partial snapshot remain available for review.
Preserve data before switching providers
Run and inspect a complete Syncro backup before removing access or beginning a cutover. Keep native Syncro exports beside the RMMBackup ZIP, record row counts and capture time, and verify customer and asset identifiers. The migration checklist explains how to keep a separate history through the move.
Review records from deleted devices
If an asset was captured before it disappeared from Syncro, an earlier accessible snapshot can retain its record. A later complete backup may record its absence without deleting the stored version. See deleted device history and retention boundaries for the conditions that determine what history is available.
Frequently asked questions
Can I back up all Syncro data in one export?
No single native workflow covers every Syncro data type. Use the relevant module export, Database Exports integration, official API read, or RMMBackup collection and document the gaps.
Can RMMBackup show a device deleted before the first backup?
No. Historical access requires a successful asset capture made while the device was still returned by Syncro.