Exporting from Datto RMM

Whether you are leaving Datto RMM or just want a copy of your estate, this is what it actually hands over, where to find each export, and what no export will ever carry.

Written with respect. We ran an MSP on several of the products we compare, we rate them, and without them Helios would not exist. These pages are here because buyers deserve the facts, not because we want a fight.

Devices: set the columns first

The device export is a copy of the table on screen, so the table is where the work happens. Open the Column Chooser and add what you will want at the other end: site, hostname, operating system, manufacturer, model and serial.

Then select rows. Export Selected Rows to CSV takes up to 500 and greys out above that. Past 500, select all rows across all pages and the Export All Rows to CSV action appears instead.

Filters and sort carry into the file too. Filter to one site if you want to move clients in batches.

Sites

The All Sites page exports to SitesTable.csv: site names, descriptions, device count, site type and PSA company name. It leaves out Site IDs.

If you need the IDs, Datto's own workaround is the Site Variables import template. In Setup, Global Settings, download the Import Site Variables template, and the file lists every site with its ID.

Tickets

Most Datto RMM estates keep tickets in a PSA rather than in the RMM, so the ticket export is usually a PSA job. Check where yours live before you plan the order.

What never transfers, whatever anyone tells you

• Scripts and automation. Every platform models these differently. They are rewritten, not imported, and this is usually the biggest job.
• Policies and alert thresholds. The thresholds you tuned over years will not match the defaults at the other end.
• Device history. Performance trends and patch history start again at zero. Export the reports clients will ask for before you switch off.
• Ticket history, in practice. Decide early whether you need old tickets live in the new system or archived and searchable. The second is far cheaper.

Loading the export into Helios

If Helios is where you are going, this is all you need to bring your clients across.

1. In Datto RMM, add the Site column with the Column Chooser, select all rows across all pages, then use Export All Rows to CSV.
2. In Helios, open Clients and choose Import from another RMM, then drop the file in.
3. Helios shows you what it found before anything is written: how many companies, how many machines, and anything it could not read. Nothing changes until you press Import.
4. Each site becomes a client, with its machines listed under it. Run it again with a fuller file and it updates rather than duplicates.

Helios needs one column that names each machine's client. It reads Company, Customer, Client, Organization or Site. If your file calls it something else, rename that heading before you import, and the preview will tell you if it still cannot find one.

Imported machines are listed, not managed. Datto RMM's agent is Datto RMM's software, so each machine starts reporting to Helios when our agent is installed on it. The dashboard counts your progress, for example 12 of 40 imported machines now reporting, so the rollout has a finish line.

Where you are going is your call. If you want the honest comparison first, the Helios and Datto RMM comparison is the page for that.

The sequence that works

1. Export everything read-only first, while you still have full access.
2. Rebuild scripts and alert thresholds on the new platform against a handful of your own machines. This sets your real timeline.
3. Run both platforms side by side across one complete patch cycle. A patch cycle is when an RMM tells you the truth about itself.
4. Move clients in batches, quietest first. Keep the old agent until the new one has reported healthy for that batch.
5. Only then cancel, and check your notice period before you pick the date.

And if you ever leave Helios

The same courtesy runs the other way. Any admin can export devices or clients to CSV from the report builder, with the columns they choose. No API key, no support ticket, no exit fee.

What we could not verify

• The exact column headings in the device export. They follow your Column Chooser choices, and Datto does not publish a fixed layout.
• Whether a Datto RMM contract can end mid-term. Ask before you plan the date.

Common questions

How do I export all devices from Datto RMM?

Open the Devices page, add the columns you need with the Column Chooser, then select all rows across all pages and use Export All Rows to CSV. Export Selected Rows stops at 500 rows.

How do I export a list of sites from Datto RMM?

The All Sites page exports to SitesTable.csv with names, descriptions, device count, site type and PSA company. For site IDs, download the Import Site Variables template from Global Settings, which lists every site with its ID.

Why is Export Selected Rows greyed out in Datto RMM?

It allows up to 500 rows. Above that, select all rows across all pages and use Export All Rows to CSV instead.

Can I import a Datto RMM export into Helios?

Yes. Include the Site column, export all rows, then drop the file into Import from another RMM in Helios. It previews the clients and machines before anything is written. Machines start reporting when the Helios agent is installed.

Details of other products on this page were checked on 28 September 2026 against their public documentation, and may have changed since. All trademarks belong to their respective owners. Spotted something out of date? Email hello@heliosmsp.io and we will fix it.