PSA Migration guide
Migrate Atera to Syncro
Plan Atera to Syncro migration using the official importer, source preparation, scope checks, pilot validation and cutover.
On this page
Use the documented Atera to Syncro route
Prepare the Atera API key and the source-plan rate limit for Syncro’s Atera importer. The tool is maintained by Syncro. See Atera Importer.
Decide what transfers and what stays in the archive
The importer covers selected customers, contacts, ticket fields and comment bodies. Plan a separate invoice archive and explicitly map Atera ticket statuses to the Syncro workflow. Confirm attachment bytes, internal-note visibility, inactive-agent mapping, time entries, custom fields and original dates against your required record inventory. Assign an archive location and owner to each item outside the agreed transfer scope.
Prepare both sides
Use the Atera export guide to retain a source copy and the Syncro import guide for destination preparation. Keep a crosswalk of customer, person and ticket IDs, including any destination IDs created during the pilot.
Validate a representative pilot
Check which transferred tickets count as resolved in Syncro; the guide warns that imported Atera statuses can leave them operationally open. Reconcile the active queue before moving inbound support. Inspect a long conversation, private note, attached file, custom status and inactive technician. Compare source and destination from a service-agent view and a requester view, and save the results with the job record.
Agree on cutover and final changes
Document the last source export, the final import batch and the person approving the reconciliation. Confirm whether the selected tool updates previously imported records or requires another approach for changes after the initial pass. Keep source access until counts, relationships, visibility and files have been accepted.
Move inbound channels and automation at the agreed time. Give staff the ID crosswalk and readable historical archive. Follow the PSA migration checklist for the shared cutover steps and the migration archive use case for later access.
Preserve history through a platform change
Keep old service conversations accessible after cutover. Request an invitation to BackupPSA. We’ll contact you if you’re selected for an invitation.