PSA Data Import

On this page

Start with the destination’s official importer

Choose the destination tool before reshaping the source export. A named importer can define user mapping, relationship handling and historical-record treatment that a generic create-record API leaves to an implementation project. For spreadsheet imports, use the current destination template and preserve an untouched source copy.

Match the tool to the job

For NinjaOne, use the end-user and ticketing-contact guide for people, or the separate Documentation CSV guide for template-based documentation. Confirm the destination PSA/Ticketing workflow with the vendor before preparing a historical-ticket transfer.

Prepare the mapping contract

For every source field, record its destination field, type, transformation, default and owner. Map people and parent records first: companies, sites, contacts, agents and groups. Then map tickets, conversation authors, contracts, time and financial relationships.

Choose how to preserve the original ticket number separately from the destination’s generated ID. Write down the time zone for source dates and verify whether the selected importer accepts original creation and update times. Keep a crosswalk that allows staff to find either identifier.

Protect the meaning of conversations

Public replies and internal notes require explicit visibility mapping. In Jira Cloud, Atlassian documents a CSV mapping that makes imported JSM comments public; use the linked guide to evaluate the selected route before transferring internal discussions. Treat attachments and inline images as their own acceptance checks, including the identity needed to retrieve each file.

Pilot, validate and correct

Build a pilot with normal and exceptional records: an inactive technician, duplicate contact, renamed customer, closed ticket, private note, large file and customized status. Inspect the destination as both an administrator and a requester. Count accepted, skipped and failed rows; reconcile files and relationships as well as parent records.

Review duplicate rules before retrying. Separate new-record rollback from updates to existing data. Save import settings, batch identifiers and error files so the next pass is reproducible. For a paid migration service, obtain the same acceptance criteria in its agreed scope.

Connect import to the full migration

Use PSA Data Export to obtain source records and PSA Migration to coordinate the final change window, communications and archive handover. Keep historical information outside the transfer scope in a readable source archive.

Guides in this topic

Import guides

• Import Autotask data with CSV templates
• Import ConnectWise PSA companies and contacts
• Import HaloPSA data: users, tickets and templates
• Import data into Syncro: choose the source-specific importer
• Import Atera data: CSV templates and ticket migration
• Import data into SuperOps: clients, sites and requesters
• Import Freshdesk data: contacts, companies and ticket history
• Import tickets into Zendesk: historical data and comments
• Import data into Kaseya BMS: Excel and migration services
• Import RepairShopr customers: CSV preparation and validation
• Import data into Freshservice: partner bulk migration APIs
• Import Jira Service Management Cloud data from CSV
• Import Zoho Desk data: module CSVs, Zwitch and assisted migration
• Import data into Zoho Billing: files, mapping and preview
• Import NinjaOne end users and ticketing contacts
• Import NinjaOne Documentation from CSV

Keep source history within reach

Keep your original source history within reach while preparing destination data. Join the waitlist for invitation-only BackupPSA access.

Email address

Join the waitlist

Website

We’ll only use your email to contact you about BackupPSA access.

Questions about your PSA? Email contact@backuppsa.com.

Related guides

PSA Data ImportPSA Data ExportPSA MigrationDeleted Record History