How to export Syncro assets, software inventory and contacts
Export assets from Assets & RMM, installed software from its report, and contacts from the End Users CSV menu. Each file answers a different question; a RMMBackup snapshot ZIP preserves supported records as a separate dated capture.
Export Syncro assets and contacts to CSV, choose a Software Inventory report, and check filters, columns, IDs and scan freshness.
On this page
Use current asset and report export controls
The Syncro tools comparison connects these module exports with current organization/end-user imports and the separate migration tools.
Choose an asset list for device details, Software Inventory for installed applications, or End Users for people and their organization relationships. The three workflows below have different row meanings; an application install count is not an asset count.
Retire a device with Archive Assets
Use native archiving when the goal is to retire a device while keeping its history in Syncro. Open the asset in Assets & RMM, choose Actions > Archive, then confirm Archive Assets. Syncro's Archive Assets guide explains agent deactivation/removal at next check-in and continued visibility from associated alerts, tickets and chats. Archived details show only System Info, with Merge/Delete actions; primary network-discovery nodes and assets with active SNMP configurations cannot be archived.
Before archiving, save and inspect the independent inventory/field copies you need below. Archiving preserves access inside Syncro; a dated export or successfully captured RMMBackup snapshot gives you a separate reference during an outage or after account access ends. Verify the required values in that copy rather than assuming every visible tab appears in a CSV.
Before you export
You need access to the relevant Syncro module or report. Export permissions and visible records follow your account access, so use an administrator or a role that can see the intended customers, assets, tickets, invoices, or inventory. Decide which datasets you need; Syncro does not provide one account-wide export.
Download the export-validation checklist and record the tenant, dataset, filters, expected count, export time, and person performing the export.
Export Syncro assets to CSV
- Open Assets & RMM and review the asset view.
- For a full asset CSV, choose Actions > Export. Syncro documents that this includes all assets regardless of row selection.
- For a tailored file, customize the table columns and choose Export Displayed Columns.
- Download the generated file from File Downloads; refresh after a few minutes if it is still being generated.
These controls are documented in About the Assets & RMM Tab/Page. Syncro's dynamic asset export release note describes the customized export as matching applied columns and filters.
Our suggested check is to compare a full export with the intended full asset population, and a customized export with the filtered view. Record active/archived scope and check identifiers and selected columns. Selecting a few rows is not a way to restrict Export to those devices.
Export an installed-software inventory report
- Open Reports > RMM > Software Inventory.
- Select a customer organization and choose Run Report.
- Use the report's CSV button when available; the file downloads directly or appears in File Downloads.
The Software Inventory report reference describes Windows-agent inventory, updated after the agent scans and reports back. It measures installed applications, not application usage. Its Installs Count links open the matching asset list. The report export guide explains CSV delivery; individual report controls still determine availability.
Our suggested check is to compare application names, versions and install counts with the generated report, then inspect a sample device's Installed Apps. Record scan freshness and the selected organization. Keep this report separate from Inventory products/services and from a per-device application list; summary rows do not establish a device-to-application mapping.
Export contacts and End Users
- Open Organizations, select the organization, then open End Users.
- Choose CSV > Export.
- On File Downloads, refresh and download the generated CSV.
The End User export guide also offers Reports > Customers > Contact Export. Syncro is renaming Contacts to End Users, so labels can differ. At least one organization is needed for this workflow.
Our suggested check is to inspect customer_id and contact_id, compare the intended organization's people with the file, and sample names, emails and custom fields. Preserve IDs as text in working spreadsheets. A contact file does not include ticket comments. Use the Syncro import guide if you later need to prepare a separate import copy.
Export the required datasets
Syncro marks its older Export All Data summary as imported and not yet verified by Syncro. Use the current asset and End User controls listed below, and contact Syncro Support if another listed option is absent.
| Data | Navigation or action |
|---|---|
| Customers | More > Admin > Reports > Customer Export |
| Contacts / End Users | Organizations > selected organization > End Users > CSV > Export |
| Ticket comments | Confirm the export with Syncro Support |
| Logistics line items | More > Admin > Reports > Logistics Export |
| Tickets | More > Admin > Reports > Ticket Export |
| Assets | Assets & RMM > Export or Export Displayed Columns |
| Invoices | More > Admin > Reports > Invoice Export |
| Inventory | Inventory > Inventory Modules > Export to CSV |
For each dataset:
- Clear or record filters that could narrow the source view.
- Start the documented export.
- If Syncro opens File Downloads, wait for the generated file and refresh if necessary; some report CSVs download directly.
- Download the file and keep the original unchanged.
The official article says it was imported from Syncro's former knowledge base and has not yet been verified by Syncro. If a named control is absent, confirm your role and current module navigation, then contact Syncro Support. Do not guess a private download URL.
Verify the result
Open every file before relying on it. Confirm that headers parse into separate columns, compare the exported row count with the source list or report, and spot-check stable customer or asset IDs from the beginning and end of the source view. Record active filters and known omissions. Check End User CSVs separately, and retain any ticket-comment files obtained through Support.
Use a filename such as syncro-example-msp-assets-YYYY-MM-DD.csv for your own copy. Keep the unedited file, the completed validation checklist, and any Support-provided files together. A CSV proves only what that export contained at that time; it does not prove that every Syncro module was included.
Export availability does not establish RMMBackup coverage. Review what RMMBackup backs up before expecting the same data in a snapshot.
Troubleshoot missing or incomplete exports
- If the file is not on the Downloads page, refresh after a few minutes and confirm that the export was started in the intended tenant.
- If the row count is low, return to the source view and record filters, archived-state choices, and role visibility before rerunning it.
- If expected columns are absent, confirm that you used the intended module export; separate Syncro exports have different schemas.
- For contacts, use the current End User CSV workflow; confirm ticket-comment exports with Support instead of treating another report as equivalent.
Keep historical captures separately
RMMBackup ZIPs contain captured JSON records, manifest.json, and original-api-responses/; they are not native Syncro CSV reports. Follow the snapshot export guide to download a historical capture.
If you need ongoing point-in-time history, set up Syncro backups. The Syncro integration page describes current availability. Exports do not automatically migrate or restore records.
Plan the next step
For a move, review Syncro 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.