Exporting from NinjaOne

To export devices from NinjaOne, open the Devices search page, choose Export to CSV, and pick all device details, which includes every column and each device's organisation. Tickets export to CSV from any ticket board. Whether you are leaving NinjaOne or just want a copy of your estate, here is what it hands over, which option to pick, and what no export will ever carry.

We have used these products ourselves, and we respect them. Most migration guides are published by the product you are moving to; we make an RMM too, so we have kept this one to the facts: what each product hands over, and what it does not.

Devices: take the full export

Open the Devices search page and use the export in its toolbar. NinjaOne offers three versions of the same list, and the choice matters more than it looks.

• Export visible columns gives you exactly what the table shows. Fine for a report, thin for a migration.
• Export with all device details includes every column, whether it is showing or not. This is the one to keep.
• Export with custom fields gives device ID, name, role, type, organisation, location, tags and every custom field. Take this as well if you rely on custom fields.

Filter to one organisation first if you want to move clients in batches. The export follows the filter.

Tickets

Any ticket board exports to CSV from its export icon. The file matches the board, so set the filters and columns with Edit Board before you export.

A single ticket exports on its own from the menu inside it. That file carries every field and the full comment trail, public and private. It is the better format for an archive, and the slower one for a big estate.

One detail to note before you archive: the export writes times in your own time zone, not the time zone the console shows.

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 conditions. 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, the device export is all you need to bring your clients across.

1. In NinjaOne, export the device list with all device details.
2. In Helios, open Clients and choose Import from another RMM, then drop the file in.
3. Helios reads the file and shows you what it found: how many companies, how many machines, and anything it could not read. Nothing is written until you press Import.
4. Each organisation becomes a client, with its machines listed under it.

Imported machines are listed, not managed. NinjaOne's agent is NinjaOne'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 NinjaOne comparison is the page for that.

The sequence that works

1. Export everything read-only first, while you still have full access: devices, custom fields and your ticket archive.
2. Rebuild scripts and alert conditions 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

• A bulk export of organisations or end users. We found imports for both in NinjaOne's documentation, not exports.
• The exact column names in the all-details export. NinjaOne lists over 60 device fields and does not publish the file layout.
• Whether a NinjaOne contract can end mid-term. Ask before you plan the date.

Common questions

How do I export a device list from NinjaOne?

Open the Devices search page and use the export in the toolbar. Choose export with all device details, which includes every column whatever the table is showing. Filter first if you only want one organisation.

Can I export tickets from NinjaOne?

Yes. Any ticket board exports to CSV, matching its filters and columns. A single ticket also exports on its own with every field and all public and private comments. Exported times use your own time zone.

Can I export organisations from NinjaOne?

We could not find a bulk organisation export in NinjaOne's documentation, only an import. The device export names each device's organisation, which is usually enough to rebuild your client list elsewhere.

Can I import a NinjaOne export into Helios?

Yes. Export devices with all device details, then drop the file into Import from another RMM in Helios. It previews the companies 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.