Exporting from Level

To export devices from Level, use Export to CSV at the top right of the device list, or run lvl device export from the command line; the file includes every matching device, all columns and custom field values. Scripts, automations and device history do not transfer anywhere. Whether you are leaving Level or just want a copy of your estate, here is what it hands over.

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

Level's export is the simple kind: every column, every device that matches your filters. Filter to one group or tag first if you want to move clients in batches.

If you script your migrations, the Level CLI writes the same export to standard output, so it drops straight into a file.

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 Level, clear or set your filters, then use Export to CSV at the top right of the device list.
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 client 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. Level's agent is Level'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 Level 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

• Which column in Level's export names the client. If it is Group, rename that heading to Company before you import.
• A bulk export of alerts history or automation runs beyond their own CSVs.

Common questions

How do I export devices from Level?

Use Export to CSV at the top right of the device list. It includes every column for every device matching your filters. The CLI does the same with lvl device export.

Does the Level export include custom fields?

Yes. Device CSV exports include custom field values for each device.

Can I import a Level export into Helios?

Yes. Make sure one column names each device's client, renaming it to Company if needed, then drop the file into Import from another RMM in Helios.

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.