Exporting from Action1

To export your estate from Action1, build a custom report with the columns you need, then use Tools, top right, to download it as CSV or HTML; the PSAction1 PowerShell module can do the same from a script. Automations, policies and patch history do not transfer anywhere. Whether you are leaving Action1 or just want a copy of your estate, here is what it hands over and where to find each export.

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.

Endpoints: build a custom report

Create a custom report with the endpoint fields you want at the other end, including the organisation, name, OS and serial. Then Tools, top right, and export as CSV.

The built-in reports export too, but only custom reports let you choose the columns.

From PowerShell

Action1 publishes PSAction1. Get the endpoints and pipe them to Export-Csv, choosing the properties you want.

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 Action1, build a custom report with the organisation and endpoint fields, then use Tools and export it as 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 organisation 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. Action1's agent is Action1'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 Action1 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 fields a custom report offers for the organisation each endpoint belongs to. If it is missing, add a Company column to the file before you import.
• Whether Action1 exports patch and deployment history in bulk.

Common questions

How do I export a list of endpoints from Action1?

Build a custom report with the fields you want, then click Tools in the top right and choose CSV. The export option is on custom reports only. PSAction1 can do the same from PowerShell.

Can I import an Action1 export into Helios?

Yes. Make sure a column names each endpoint's organisation, then drop the CSV into Import from another RMM in Helios. It previews everything before anything is written.

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.