RMM migration checklist: export, import, validate, and preserve history
Start an RMM migration by checking the destination's official tools, then plan records, agent deployment and configuration separately. Keep a source copy, test a small group, reconcile results, and retain old-platform access until the cutover checks pass.
Plan an RMM migration by inventorying records, exporting source data, checking destination imports, validating results, and preserving history that will not transfer.
On this page
Plan your migration
Use this RMM migration checklist to agree on the records, working features and historical evidence your MSP needs before choosing a cutover date:
- Inventory customers, contacts, sites, devices, tickets, documentation, policies, scripts, monitors and audit history.
- Assign an owner and a way to check each type of record. Record IDs and parent relationships, not just names.
- Check the destination's named native tools before choosing a manual CSV transformation.
- Preserve source exports and configuration notes while access is available.
- Pilot the documented import and agent deployment separately. If the tool cannot select a small batch, agree on a test or onboarding environment with the vendor.
- Reconcile results, review access and operational controls, and resolve failures before expanding the move.
- Confirm source-access deadlines, retained-history access, rollback contacts and contract dates before cutover.
Keep both platforms available during validation where contracts and security policy permit. A created destination record is not enough: check monitoring, patching, scripts, alerts and remote access with ordinary technician roles.
What transfers, and what stays behind?
Use the RMM import, export and migration tools comparison to identify a method for each resource before preparing your migration checklist.
List what each tool transfers, what it leaves out, and any questions to settle with the vendor before starting. Keep a separate copy of records you still need after the move.
| Task | What to check | What it does |
|---|---|---|
| Historical-record migration | Records, fields and relationships included in the tool | Which earlier records transfer, and which require separate preservation |
| Agent deployment | Installer, account mapping and deployment instructions | How endpoints become managed in the destination; keep earlier history separately |
| Configuration transfer | Supported policy, component or template package | Which settings transfer and which dependencies or assignments need review |
| Internal migration | Account, organization or region instructions | A move within the same vendor, with its own rules |
For each resource, record the source ID, destination matching field, required parent records, import method, rejection handling and validation result. Keep originals unchanged; transform working copies only when the destination requires it. Configuration definitions, assignments and historical executions are separate items to verify.
Export from your current platform
Start with the Data Export guide and its vendor instructions for native reports, files and supported API retrieval. A current inventory export may be useful without containing every previous device state.
For a documented Atera exit, the Atera-to-Syncro guide connects Atera exports to the destination's importer and deployment workflow. For N-sight offboarding, use the guide below to plan device removal, recovery-key access and download deadlines. Use the other vendor export guides to save the records and settings you need before ending access.
Keep configuration evidence, export filters, timestamps, record counts and unresolved gaps with the files. Download needed copies before changing source credentials or ending access.
-
N-able N-sight
N-sight data retention: deletion, reports and recovery keys
Plan N-sight offboarding around specific data lifecycles instead of one assumed retention period.
Import into your destination
Use the Data Import guide to choose published destination instructions for Atera, Syncro, Hudu, NinjaOne, SuperOps or Datto RMM. Their accepted resources differ: a configuration package, documentation import and customer CSV are not interchangeable.
Follow the destination guide for templates, permissions, account requirements and field mapping. Validate counts, relationships, rejected rows and duplicate behavior. Do not assume an RMMBackup ZIP or another vendor's CSV is directly importable.
The official Level deployment guide requires elevated execution and the correct install key. SuperOps asset scripts install agents using client/site information. These are agent deployment instructions, not evidence that old device history transfers.
Vendor-specific migration paths
Syncro's Atera importer documents selected customer, contact, ticket and comment fields plus a separate agent deployment step. It excludes invoices, requires an Atera API key and an appropriate rate limit, and calls for ticket-status review. The Atera-to-Syncro guide below links the source and destination instructions instead of treating all exports as equivalent imports.
For VSA 9 to Datto RMM, start with Datto's migration page and confirm the records, prerequisites and configuration work with Kaseya before choosing a cutover date.
Internal account, organization and region moves
Action1's regional migration moves accounts and agents between its regions. Plan the manual work for groups, users, automations, custom applications, scripts, data sources and reports. Automox's policy migration video demonstrates transfers between Automox organizations; its script omits payloads and group assignments, so save those separately and ask Automox which tool to use. These moves stay within each vendor rather than moving records to a competitor.
Choose the guide below that matches your source and destination.
-
Atera
Atera to Syncro migration: export, import, and validate the move
Coordinate Syncro's documented Atera importer, asset deployment, cutover checks, and separate historical records.
Documentation migrations
Documentation needs separate checks for articles, assets, passwords, attachments, relationships and permissions. Moving these records does not enroll managed endpoints in a new RMM.
Hudu's IT Glue migration instructions link its maintained migration repository. Check current tool versions, source API access and destination permissions there. The guide below connects official source-export instructions to Hudu import guidance, and explains which records and permissions need separate handling.
-
IT Glue
IT Glue to Hudu migration: choose the tool and validate documentation
Choose Hudu's migration tool or selected CSV imports, then check transferred records, relationships and access.
Preserve history that will not transfer
For tickets, audit events, previous device details, policy versions and deleted records, check the tool's documented scope. Record what the tool transfers, settle any missing details with the vendor, and assign someone to retain each source copy.
RMMBackup preserves supported records as read-only history for browsing, comparison and export when capture succeeds before deletion or loss of source access. It does not perform automated vendor-to-vendor migration or write records into the destination. See current backup coverage before relying on a source connection; an informational vendor guide does not establish integration availability.
Use product retention and plan rules to check which snapshots remain accessible, and download the required ZIP before changing a connection. Review deleted device history and outage access for questions that may arise later.
Complete the cutover checklist
- Confirm the final source export and its capture time.
- Reconcile transferred records and resolve rejected imports.
- Verify destination agent coverage, policies, scripts, monitoring, patching and remote access.
- Test technician and customer permissions and workflows.
- Record where non-transferred history is kept and who can access it.
- Confirm billing, cancellation, retention and account-closure dates.
- Keep rollback steps and escalation contacts available during the transition.
The migration use case explains how captured records help answer client questions during and after the move.
Provider guides
Use Browse by Vendor to find every published guide for a source or destination. Choose either platform to find the guides relevant to your move.