Prepare for a switch
Keep useful HaloPSA history available while teams learn a replacement system.
MSP PSA · Vendor guide hub
HaloPSA export, import and migration guides
Explore native tools for moving HaloPSA records, preparing a usable archive and recovering deleted information.
HaloPSA coverage should not be assumed to match HaloITSM or HaloCRM.
Choose a native HaloPSA workflow
Work through an outage
Look up a previously captured ticket, customer, or billing record while the source is unavailable.
Review an absent record
Open the last captured version of a record after it no longer appears in a later successful backup.
Records to assess
HaloPSA business-record context
- Tickets, actions, and notes
- Clients, users, and sites
- Time and contract data
- Invoices where licensed
Halo exposes tenant-specific API details and modules; available entities depend on configuration and licensing.
Backup preparation
- Create OAuth 2.0 client ID and secret using least privilege.
- Add the tenant, region, or subdomain details described in the credential guide.
- Validate the connection and choose supported record groups.
- Run a manual backup, then review collection results before relying on the snapshot.
Plan the full data lifecycle
Choose a native export method, check the destination importer, and validate a sample before cutover. Preserve readable source history for later client questions.
Invitation only
Keep HaloPSA history within reach
BackupPSA is invitation only. Join the waitlist and we’ll contact you about your invitation.