1. Preserve Atera first
There is no single all-data export. Inventory each required entity, keep original files unchanged, record filters and counts, and preserve attachments, invoices, and history that the destination importer does not cover.
24 controls · Official-source boundaries · Public CSV · No signup
Export Atera to Syncro without mistaking an import for a migration.
Use this source-dated worksheet to preserve Atera records, map ticket states, run Syncro's documented importer, deploy destination agents in a controlled pilot, rebuild what does not transfer, and reconcile every endpoint before source retirement.
Download the CSVUse the full migration workbookCompare Atera and SyncroOpen the migration guideUse the Data Package
2. Map before importing
Create the required Syncro ticket statuses, map customers deliberately, record the approved API rate limit, and test representative records before repeating any uncertain import.
3. Deploy agents as a separate change
Customer and ticket import does not enroll endpoints. Pilot Syncro's documented deployment workflow on authorized, representative devices and prove identity, policy, monitoring, remote access, and rollback.
4. Rebuild and reconcile
Rebuild scripts, monitoring, patching, permissions, and integrations as destination configurations. Run both platforms only within a bounded authority model, then reconcile every endpoint and exception.
What the documented importer covers
The current Syncro documentation describes a one-time Atera importer and a separate endpoint-deployment script. Treat the listed scope as a starting point, then verify the live vendor documentation and your own pilot results on the migration date.
| Area | Documented path | Required validation |
|---|---|---|
| Customers | Selected name, phone, address, and notes/domain fields through Syncro's Atera Importer | Compare source IDs, names, domains, counts, and near-duplicate mappings. |
| Contacts | Selected name, email, title, and phone fields through the importer | Check parent customer, duplicates, inactive contacts, and required custom data. |
| Tickets and comments | Selected ticket fields and comment body | Create source statuses first; sample every state; inspect comment order and retained metadata. |
| Endpoints | Prepare customer mappings, then use Syncro's generated script to install its agent through Atera | Pilot enrollment separately; verify identity, organization, policy, monitoring, workflow, and removal. |
Preserve or rebuild what does not move
A successful importer receipt is not proof that the destination can deliver the service. Use separate owners and acceptance tests for each gap.
Invoices and attachments
Syncro says Atera invoices are not imported. Atera says bulk exports do not include attachments. Preserve required copies with parent-record mapping, hashes, access control, and retention ownership.
Profiles and automation
Atera says automation settings, thresholds, and monitoring profiles are not exportable. Inventory purpose, assignments, privileges, dependencies, schedules, exceptions, and recovery before rebuilding.
Patch and alert behavior
Validate approval rules, rings, reboots, exclusions, reporting, alert routing, ticket creation, assignment, notifications, escalation, and closure across a representative cycle.
History and acceptance
Preserve required operational history, reconcile source and destination counts, explain every exception, stage credential revocation, and record named operational and business acceptance.
Official sources checked November 10, 2026
Use the current vendor pages—not this worksheet alone—when executing a migration.
Atera Data Export FAQ
Documents per-entity report and API exports, pagination, excluded deleted records, attachment limits, and non-exportable automation, threshold, and monitoring-profile settings.
Syncro Atera Importer
Documents imported customer, contact, ticket, and comment fields; invoice exclusion; ticket-status behavior; rate-limit input; customer preparation; and the deployment script.