PSA Data Import guide
Import NinjaOne Documentation from CSV
NinjaOne Documentation imports rows from a CSV matching a selected document template. Download that template in the product, populate it, preview the results and review the import history.
On this page
Use the Documentation CSV importer
This workflow creates records in NinjaOne Documentation. Select it when your source information belongs in a Documentation template. Ticket history and people use separate workflows; use the people-import guide for end-user accounts and ticketing contacts.
Download the template for the destination document
NinjaOne's Documentation CSV Migration Tool guide places the importer under Administration > Apps > Installed > Documentation. Choose Manage Templates > Import Document(s) from CSV, select the template type, and download its CSV.
Populate the downloaded columns and save a working copy. The file must match the selected template. Spreadsheet cells do not reproduce interactive field controls such as dropdowns. The documented workflow creates documents; it does not update existing documents through templates, so plan retries deliberately.
Preserve organization and document identity
The Apps & Services guide describes required organization and document names. Use the exact destination organization name so a record is assigned correctly. Check the selected template's requirements before importing. An arbitrary collection of PDFs or Word files is a different input from populated template rows.
Keep the original source data and a row-to-organization mapping. Include similar customer names, empty fields and multi-line text in a small pilot. Review who should be able to read the resulting documentation.
Preview errors and review import history
Upload the CSV and select Preview. Correct reported errors in the working file and re-upload it, then save the changes when the preview is ready. In Import History, review the document, date, technician, status, rows attempted and rows imported. Keep these results with your source mapping before attempting another batch.
Validate the resulting records
Open the imported documents in their destination organizations. Check field values, formatting and access with the responsible technician. Reconcile successful rows and failures, and decide how to handle corrections without creating duplicate documents.
Continue with PSA Data Import, the NinjaOne guide hub and the migration archive use case. Keep Documentation scope explicit in the migration plan.
Keep source history available after your move
Join the waitlist for invitation-only BackupPSA access, or contact us about your platform.