Atera to Syncro migration: export, import, and validate the move
Syncro documents a one-time Atera importer for selected customer, contact, ticket, and ticket-comment data, plus a script that deploys the Syncro agent and maps devices to customers. Export and preserve Atera data first, run a pilot, and validate the destination before ending source access.
Plan an Atera-to-Syncro migration using Syncro's Atera importer and asset deployment workflow, then validate customers, contacts, tickets, devices, and retained history.
On this page
Preserve the Atera source first
Compare the Atera export boundaries and Syncro importer scope before deciding which source records need an independent copy.
Use the Atera data export guide to collect the reports and official API data your MSP needs. Keep the original exports unchanged and record filters, capture dates, counts, and gaps. Atera does not provide one all-data export, so inventory each required resource separately.
If RMMBackup is connected to Atera, confirm the selected collections completed successfully and download the snapshot ZIP you intend to keep. This preserves supported source records for later review; it is not the file Syncro's importer consumes.
Check what Syncro's Atera importer moves
Syncro's official Atera importer lists selected fields for:
- Customers: name, phone, address, and domain in notes.
- Contacts: name, email, title, and phone.
- Tickets: ID, title, status, ticket type, contact, priority, and resolved date.
- Ticket comments: body text.
The same documentation says Atera invoices are not imported. Ticket statuses may initially appear blank until added in Syncro, and no imported Atera ticket is placed under Syncro's Resolved status. Review ticket state explicitly before technicians begin work.
Pilot the importer and device deployment
- In Syncro, open Admin > RMM Settings - Migration Tools and choose Atera.
- Enter the Atera API key and a rate limit appropriate to the Atera plan.
- Run the documented import in an agreed test or onboarding environment; the public instructions do not establish a customer-selection filter.
- Review destination counts, relationships, ticket statuses, and comments.
- Prepare Syncro's customer database and obtain the documented deployment script.
- Run the pilot through Atera's scripting workflow and verify that the Syncro agent appears under the correct organization.
The script installs agents with customer mapping. Historical device transfer is not established by those instructions.
Validate operations before cutover
Compare source and destination customer and contact counts. Sample imported tickets and comments. Add or map required ticket statuses, then verify device-to-organization assignment, policies, monitoring, alerts, patch settings, scripts, remote access, and technician permissions.
Run the deployment in controlled batches. Keep Atera available until the agreed validation passes, then follow both vendors' current agent and remote-access transition guidance. Coordinate billing and old-agent removal only after destination coverage is confirmed.
Record exclusions separately from unknown transfers
List the records the importer transfers and any details that need separate handling. For required configuration, events or earlier device details, agree the transfer scope with the vendor and keep that checklist with the source copies.
RMMBackup does not run the Atera importer or write data into Syncro. It can preserve the supported Atera records captured successfully before the switch as a browsable, downloadable reference. See deleted device history and configuration backup for information that may need a separate record.
RMMBackup's Atera coverage is focused on supported RMM and customer-context data; the native importer's ticket support does not mean tickets are included in an RMMBackup Atera snapshot. Free allows one connected vendor and locks that account after the first fully successful backup. Full Access lets you keep both supported platforms connected, with one account per platform, and allows validated account switching; review plans and history access and keep the required ZIP before changing a connection.
Continue with the destination guides
Use the Syncro data import guide for organization and end-user CSV details when the dedicated importer does not cover a needed workflow. Return to the RMM migration checklist for reconciliation, cutover, rollback, and account-closure checks.