PSA Migration guide
Migrate Autotask PSA to HaloPSA
Plan Autotask PSA to HaloPSA migration using the official importer, source preparation, scope checks, pilot validation and cutover.
On this page
Use the documented Autotask PSA to HaloPSA route
Use Halo’s Configuration > Migrations > Autotask module with the documented API-user connection. The tool is maintained by Halo. See Autotask Migration.
Decide what transfers and what stays in the archive
Halo lists companies/locations, contacts, employees, products, service catalogue, billing codes, agreements and tickets. 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 HaloPSA 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
Test the connection, inspect the selected entities and plan their dependency order. Include a multi-site customer and agreement-linked ticket in the pilot. 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.
Test defaults and legacy ticket replies
Halo’s Autotask Migration guide uses an API-only source user. Test the connection, review import defaults and select the intended records before running the pilot. Prepare handling for replies that reference legacy Autotask ticket numbers after cutover; test a real-format reply against an imported ticket before switching inbound mail. Keep an ID crosswalk available to service staff.
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.