RMM data import: formats, field mapping, and validation

At a glance

Start with the destination RMM's current import documentation and template. Confirm supported record types, required parent records, field names, file encoding, duplicate behavior, and validation results before importing the full data set.

Check what an RMM can import, prepare vendor templates, map fields, test a small batch, and validate the destination without assuming a full migration.

Published Updated

On this page

Start with what the destination accepts

Compare native import tools and their accepted records before choosing a template or migration tool. Follow the linked instructions for your destination.

Check for a dedicated official importer before preparing a generic CSV. A native tool may already preserve the relationships you would otherwise have to map. For example, Syncro's migration hub lists distinct source-specific tools; check which records each tool transfers.

An export file is not automatically importable. The destination decides which resources, fields, formats, and relationships it accepts. Download its current template instead of renaming columns by guesswork, and check whether the feature depends on an account plan, administrator role, or pre-existing record.

Before editing the export, list the import requirements:

Question What to record
Which records can be imported? The destination's official import page and current template
Which fields are required? Required template columns and account-level required fields
Which parent records must exist first? Customer, organization, site, asset type, or other dependency
How are duplicates handled? Documented identifiers, update rules, and rejection behavior
How is success checked? Import-results screen, counts, errors, and sampled destination records

Ask the vendor about any required field, duplicate rule or import result that is unclear before uploading a large file.

Prepare and map the data

  1. Keep the original source export unchanged.
  2. Download a fresh destination template and preserve its headers.
  3. Map source fields to destination fields in a separate worksheet or document.
  4. Normalize dates, phone numbers, booleans, and identifiers only where the destination requires it.
  5. Flag source fields with no destination instead of discarding them silently.
  6. Scan spreadsheet cells for formulas before opening or uploading CSV files.

Map parent records before child records. Organizations or customers commonly precede contacts, users, and assets. A device agent deployment may create a new managed-device record rather than import an old device record and its history.

Test and validate an import

Use a small representative batch that includes ordinary records, custom fields, and edge cases. Save the destination's import results, correct rejected rows, then compare counts and sample fields in the destination. Check relationships as well as row creation: a contact under the wrong customer is not a successful migration.

Before the full import, decide how you will prevent duplicates and whether rerunning a file creates, updates, or rejects records. Afterward, reconcile totals for every supported resource and retain the error report with the transformation notes.

Match narrower imports to the right task

Native tools may organize existing endpoints, import scanner findings or transfer configuration. Use the vendor tools comparison to choose a method, then follow the destination guide below for its templates and setup steps.

For narrow configuration tasks, N-sight documents script uploads and community SNMP checks; OptiTune documents prepackaged task imports. Use these tools for their specific script, check or task imports. Keep earlier device history separately when moving between platforms.

Keep native imports separate from RMMBackup

RMMBackup preserves supported source records as read-only history and provides snapshot ZIP downloads. It does not upload those records into an RMM, map fields for a destination, or run native vendor import tools. Use the destination vendor's official workflow for writes, and use RMMBackup history to review supported records that were captured before source access ended.

Continue with the RMM migration checklist, plan the source export, and preserve deleted device history when it may not transfer.

Provider guides

Choose your destination below for templates, prerequisites and import checks. If it is not listed, ask the vendor which import tools fit the records you need to move.