PSA Data Import guide
Import NinjaOne end users and ticketing contacts
NinjaOne provides separate bulk imports for end-user accounts and ticketing contacts. Choose the record type first, then prepare the spreadsheet for its organization and permissions.
On this page
Choose end-user accounts or ticketing contacts
End-user accounts receive configured access to NinjaOne features. Ticketing contacts identify people who communicate through tickets. Technicians have their own account and permission workflow. Choose the destination identity before importing a list of people; a contact import and an account invitation have different outcomes.
Import end-user accounts from a spreadsheet
Follow Create or Import End User Accounts. Open Administration > Organizations, select the organization, then End Users > Import Users. Paste the spreadsheet columns into the importer.
Supply first name, last name and a unique email address; phone is optional. The documented name limit is 150 characters and email limit is 64. Email must be unused by existing technicians and end users. Include the country code for phone values and preserve the leading plus sign when preparing them in Excel. Invalid values can fail the entire import.
Select the imported people and assign their intended roles before completing the import. Check invitation status afterward. Test with a small authorized group before sending invitations to the full list.
Bulk import ticketing contacts
The Ticketing technician and user permissions guide documents a separate Contacts > Import Contacts action in the organization editor. Paste three populated columns in this order: First Name, Last Name, Email. Email values must be unique.
Check that each resulting contact belongs to the intended organization. A contact can receive ticket communications and submit tickets through the configured email domain. Review end-user account access separately when a person also needs access to the platform.
Importing from Active Directory or Microsoft Entra ID
For ongoing identity provisioning, review NinjaOne's SSO and SCIM integration. It describes Microsoft Entra ID and organization/role mappings; that configuration excludes on-premises Active Directory. Identify which directory you use before choosing a workflow. An AD device-discovery job is a different task from provisioning user accounts.
Validate people before migrating service history
Reconcile source people, destination organizations, contact identities and account roles. Check a duplicate email, an international phone number and users belonging to different customers before expanding the batch. Preserve the source list and an identity crosswalk for subsequent ticket preparation.
Use PSA Data Import for relationship planning and the NinjaOne hub for related workflows. Documentation CSV imports have their own templates. Plan historical service records through PSA Migration and the migration archive use case.
Keep source history available after your move
Join the waitlist for invitation-only BackupPSA access, or contact us about your platform.