How to import clients, requesters and sites into SuperOps

At a glance

SuperOps offers a guided import for clients, requesters and sites, with column and value mapping. Its separate asset migration scripts install agents. Plan and validate those workflows independently so a newly managed device is not mistaken for transferred history.

Prepare SuperOps client, requester and site imports, map columns and values, and separate agent deployment from historical data transfer.

Published Updated

On this page

Choose the record type and source file

Compare SuperOps supported imports and report exports before assuming an asset inventory file can recreate old managed-device history.

SuperOps documents the import under Modules > Clients > CSV import, with a choice of clients, requesters or sites. Despite the button name, its official guide accepts CSV, TSV, XLS, XLSX and XML, plus manual entry.

Save an original source export and work on a copy. Identify parent clients and sites before preparing dependent records. Do not substitute a device report for a requester list.

Map headers, columns and values

The wizard lets you choose headers, match columns and map values before reviewing the result. Check names, contact details and parent assignments against a representative source sample. The public article does not define every required field or duplicate rule; confirm the target wizard's validation before a large upload. Do not assume a repeated file updates existing records.

Handle managed assets separately

SuperOps' asset migration script guide starts at Profile > Product Onboarding > Migrate data > Import Asset. It provides Windows, macOS and Linux scripts using client/site context and account credentials. Review the current vendor script and pilot an endpoint before expanding deployment.

This is evidence for agent onboarding, not transfer of the former RMM's historical records. Track imported business records and newly enrolled endpoints as separate acceptance checks.

Validate the result before cutover

Compare record counts, client/site assignments and sampled field values. For endpoints, verify inventory, policies, monitoring and remote access. Keep rejected rows and unresolved mappings with the unchanged export. Follow the migration checklist before ending source access.

Retain information for later questions

The SuperOps export guide covers reports and supported captures. The SuperOps integration preserves supported records for browsing and export; RMMBackup does not run imports or installation scripts. Capture needed data successfully while it is available, and check plans for history and automatic scheduling. See the migration use case for the ongoing reference workflow.

Official source

Importing clients, requesters, and sites

Related SuperOps integration

Review current SuperOps backup coverage and availability.