How to import customers, contacts, and assets into Atera

At a glance

Atera documents bulk CSV imports for sites or customers, users or contacts, and assets. Use the template for each record type, create parent records and asset types first, keep headers unchanged, and validate a small de-duplicated file before a full import.

Prepare Atera CSV templates for customers, contacts, sites, users, and assets, follow dependency order, avoid duplicates, and validate import results.

Published Updated

On this page

Check access and download fresh templates

Compare Atera imports with its native export methods to check which source objects need separate preservation before mapping a file.

Atera's official instructions place imports under Admin > Data management > Import data and describe CSV or RFC 4180 files. The feature requires an administrator role and is plan-dependent. Download the current template from the target account for each resource instead of reusing an old file.

The documented workflows cover sites or customers, users or contacts, and assets. Atera's terminology differs between IT Department and MSP accounts, so follow the labels shown in the target account.

Import parent records before dependent records

  1. Import sites or customers first.
  2. Import users or contacts after their related site or customer exists.
  3. Create any required asset types before importing assets.
  4. Import assets with the matching customer or site and asset type.

Keep template headers unchanged and fill every mandatory field. The official customer template includes customer identity and address fields; contact and user templates require their parent plus name and email fields; asset templates depend on the selected asset type.

Prevent duplicates and file-wide failures

Clean the working CSV before upload. Atera documents rejection cases involving duplicate or existing contacts and users, contacts or users mixed across parents in a way the import does not accept, invalid email addresses, missing required parent records, and changed headers.

For asset imports, duplicate serial numbers can reject the entire file. Atera states that serial-number comparison ignores capitalization and surrounding spaces. Blank serial numbers are not checked the same way, so they can create an additional asset; reconcile them before upload. The documented asset import creates new assets rather than updating or merging existing ones.

Validate the imported records

Start with a small file. Compare imported counts with accepted rows, inspect several records in Atera, and verify customer or site relationships, custom fields, and asset types. Preserve the import file and any error output with your field-mapping notes.

Native Atera imports write supported records into Atera. RMMBackup does not run this import or convert a snapshot ZIP into an Atera template. Use the Atera data export guide for source-side collection and the RMM migration checklist for cutover validation and history that will not transfer.

Import boundaries to confirm

Ticket history has a separate documented path: Atera's Ticket Migration service. Professional Services coordinates ticket/comment files after technicians and contacts or users exist in Atera. The documented support-access token expires after five days. Use the linked vendor templates and confirm the migration window with Atera; this is distinct from the self-service asset CSV workflow.

Official documentation supports the record types and process above; it does not establish that every Atera configuration, ticket detail, historical event, policy, or relationship can be recreated through these CSV imports. Check current Atera documentation and the target account for the exact fields you need. Preserve unmatched fields separately instead of forcing them into an unrelated column.

Official source

Import data to Atera

Related Atera integration

Review current Atera backup coverage and availability.