How to import organizations and documentation into NinjaOne

At a glance

NinjaOne documents separate imports for organizations, documentation and technicians. Agent deployment is another workflow. Choose the relevant import for each record type and validate organization assignments before deploying broadly.

Separate NinjaOne organization, documentation, and technician imports from agent deployment, with official templates and validation checks.

Published Updated

On this page

Prepare organizations before agents

Compare NinjaOne organization/document imports and native exports before planning historical access alongside agent deployment.

The Quick Deployment Guide describes a template organization followed by CSV organization creation. Review policy mappings, remote access and device approval in that template. Installer Management supplies organization-specific installation details and device tokens. FedRAMP uses a different documented workflow.

Import documentation using its own template

In Apps & Services, use Manage Templates > Import Document(s) from CSV, select a document template and download its CSV. The wizard validates organization and document names; follow its required-field feedback before importing. Template-library imports and document-row imports serve different purposes.

Pilot one organization's documentation. Compare populated fields and links with the originals, and check technician access. These instructions do not establish full-account history migration.

Add technicians and review roles

NinjaOne's technician account guide describes pasted tabular imports under Administration > Accounts > All users. Names and a unique valid email are required; phone formatting is validated when supplied. Invalid values can fail the entire import. Review role assignments after creation rather than assuming source permissions transfer.

Treat agent deployment as a separate workstream

The deployment guide covers existing RMM tools, GPO and Intune. Follow the Migration from other RMM solutions instructions in NinjaOne Academy for your deployment method. Check that the agent reports to the intended organization, and preserve earlier device history separately.

Reconcile the transition and keep captured history

Use the NinjaOne export guide for source-side copies and the RMM migration checklist for operational checks. Validate organization placement, inventory, policy application, alerts and remote access before retiring source agents.

The NinjaOne Beta integration keeps supported records and permitted documentation as browsable, downloadable history. RMMBackup does not execute imports or deploy agents. Check plans for accessible history and scheduling, and the migration use case for preserving a reference after a switch.

Official source

NinjaOne Agent Installation - Quick Deployment Guide

Related NinjaOne (formerly NinjaRMM) integration

Review current NinjaOne (formerly NinjaRMM) backup coverage and availability.