PSA Migration guide
Migrate Autotask PSA to Syncro
Plan Autotask PSA to Syncro migration using the official importer, source preparation, scope checks, pilot validation and cutover.
On this page
Use the documented Autotask PSA to Syncro route
Start with a new Syncro account. The importer uses exact company-name matching, so assess any existing customer data with Syncro support before running it. The tool is maintained by Syncro. See Autotask Importer.
Decide what transfers and what stays in the archive
The documented transfer covers selected account/contact fields, ticket numbers, subjects and creation dates, and ticket-note text, dates and authors. 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 Autotask PSA 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
Review the View Import Results report. Use a customer whose company name differs between systems to test your preparation before the production run. 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.
Prepare required fields and exact-name matching
In Syncro’s current Autotask Importer guide, prepare the API Tracking ID and temporarily disable required customer fields before importing. Decide whether to include inactive customers. Review exact-name matches before starting: naming differences can produce separate destination customers. Keep a reviewed source-to-destination client crosswalk and restore required-field settings after validation.
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.