Use Atera’s bulk import to bring in sites, customers, users, contacts, assets, and related custom fields.
Overview
Q: What data types can be imported into Atera?
A: Sites, customers, users, contacts, assets, and custom fields.
Q: Where do I find the import feature?
A: Admin > Data Management > Import data in the Atera console.
Q: Which file formats are supported?
A: CSV conforming to RFC 4180.
Templates & Required Fields
Q: Is there a template for each import type?
A: Yes, downloadable templates exist for sites, customers, users, contacts, and assets.
Q: What fields are required for each import?
A: Each template lists mandatory columns (e.g., site name, customer name, email). These must be valid for a successful import.
Q: Can I change template headers?
A: No. Do not rename or remove header columns.
Preparing Your Data
Q: Is there a record limit per file?
A: No strict limit. For reliability, split very large files if needed.
Q: How do I avoid duplicates?
A: De-dupe your CSV first; duplicates or clashes with existing records will block import.
Q: Are special characters supported?
A: Yes. Save files as UTF-8 for international text and accents.
Importing Specific Objects
Q: Can I import sites in bulk?
A: Yes. Complete the Sites template and upload.
Q: How do I import customers?
A: Use the Customers template; keep headers unchanged and validate all data.
Q: Can I import users/contacts?
A: Yes, but ensure the related site/customer exists first. Users/contacts must be imported one customer/site per file.
Q: Can I import assets?
A: Yes. Select the asset type, download its template, complete it, and upload. You may pre-create assets before agents are installed.
Q: How do I add new asset types for import?
A: Create them first in Admin > Data Management > Custom assets, then use the matching template.
Custom Fields
Q: Are custom fields importable?
A: Yes—create custom fields first in Atera. They’ll appear as columns you can populate.
Q: Can I import asset metadata like S/N, warranty, vendor, tags, IP/MAC/VLAN, owner, lifecycle status?
A: Yes. Add these as custom fields and populate the corresponding columns.
Validation, Mapping & Errors
Q: What causes import failures?
A: Missing required fields, invalid emails, duplicates, header changes, or referencing non-existent parent records (e.g., users without an existing customer).
Q: How are errors shown?
A: Atera displays row-level error messages indicating what to correct.
Q: Can I re-upload only failed rows?
A: Yes. Fix the errors and re-import the failed rows.
Bulk Update & API
Q: How do I bulk update existing records?
A: Include unique identifiers (as per template). Matching records will update instead of duplicating.
Q: Can I automate or schedule imports?
A: Not via the UI. Use the API for programmatic syncs and large-scale migrations.
Q: Can I import data exported from another system?
A: Yes. Reformat the export to match Atera templates and field mapping.
Not Supported / Limitations
Q: Can I import tickets or ticket history?
A: No native ticket import. The API supports limited ticket creation; contact Support for migration options.
Q: Can I import attachments or images?
A: No. Upload attachments manually after the data import.
Q: Can I import monitoring thresholds, SLAs, device relationships, or roles/permissions?
A: No. Configure these manually post-import.
Q: Is there an undo/rollback for imports?
A: No. Delete or update records manually if needed.
Q: Can I import passwords or sensitive credentials?
A: No, for security reasons.
Post-Import & Usage
Q: Where do I see imported data?
A: Immediately visible in Sites, Customers, Assets, Users, Contacts pages.
Q: Is imported data available for analytics and automation?
A: Yes—usable in reports, filters, and workflows once mapped.
Q: Can I assign assets to folders or contacts during import?
A: Yes—use the folder and contact email columns in the asset template.
Q: What about tags/categories?
A: Typically managed after import (not directly mapped during asset import).
Troubleshooting & Support
Q: What should I check if an import fails?
A: Verify required fields, valid emails, no duplicates, correct parent records, unchanged headers, and UTF-8 encoding.
