PSA Data Import guide
Import Atera data: CSV templates and ticket migration
Import Atera customers and contacts with native CSV templates, or prepare ticket history for Atera Professional Services. Check matching before retrying.
On this page
Choose CSV import or Professional Services ticket migration
Atera has separate routes for customer records and historical tickets. Use the native CSV importer for customers, contacts and assets. Atera Professional Services coordinates ticket and comment migration from other systems.
Prepare the native CSV import
Under Admin > Data management > Import data, download the template for the selected object. The MSP plans listed are Growth, Power and Superpower, with administrator permission. Keep column headers unchanged. Create customers before contacts; contact rows require customer name, email, first name and last name. Create the asset type before downloading its template.
Check object-specific matching before retrying
The detailed Import data to Atera guide specifies new-only asset imports. Duplicate serial numbers, including case or surrounding-space differences, reject the entire file. Correct the file before uploading again. Empty serial numbers can create duplicate assets. Contact troubleshooting also calls for new contacts and one customer per file. Apply these object-specific rules instead of treating the broader Import FAQ as a universal update promise.
Prepare historical tickets with Atera Professional Services
The official Ticket Migration guide provides a vendor-operated route:
- Add destination technicians and end-users first, resolving inactive-person mappings.
- Prepare the separate ticket and comment files using the current specifications supplied by Atera.
- Arrange support access with the documented token, which expires after five days.
- Coordinate the migration window with Atera support or your Professional Services representative before using destination ticketing.
Blank technician values leave tickets unassigned. Review reassigned authors and owners during the pilot. The public format links include image-based material; obtain usable current specifications before constructing production files.
Validate the result before cutover
Check a closed ticket, an unassigned ticket, an inactive technician, public replies, a private note and a downloadable attachment. Compare source IDs, dates, relationships and files against your acceptance list. Keep a batch record that distinguishes new records, rejected files and any agreed manual correction.
Use the Atera export guide, data import pillar and PSA migration checklist to connect preparation to cutover. Browse the Atera guide hub for backup and recovery planning.
Import users or contacts for the right Atera edition
The native import guide uses Customers and Contacts for MSPs, and Sites and Users for IT departments. For MSP customer people, choose the Contacts template. Create its customer first, then supply customer name, email, first name and last name. The IT-department Users template instead uses Site name. Technician accounts are a separate preparation step for ticket migration.
Keep one customer's contacts in each file and follow the object-specific duplicate rules above. Opening a template in Excel is useful for editing; preserve the required CSV format and column names when saving.
Keep source history within reach
Keep your original source history within reach while preparing destination data. Join the waitlist for invitation-only BackupPSA access.