New office users cannot reach the billing portal over VPN.
Use case
Keep useful history when you switch PSA platforms
Move forward without leaving old tickets, notes, agreements, and billing context behind.
The question your team needs to answer
“Can we cancel the old PSA and still find the full service conversation six months from now?” Flat exports can separate comments, people, agreements, and files from the ticket that gave them meaning.
What must already exist
The relevant record and relationship data must have been captured successfully before the switch, deletion, outage, or change. Permissions and vendor API coverage still define what is available.
Updated peer routes and verified access from the guest segment.
📎 route-review.txt · metadata capturedA practical workflow
- Choose the destination's documented importer and map its required source records.
- Export a representative customer, ticket conversation and related files.
- Reconcile the pilot and retain the source-to-destination identity map.
- Agree the final-change window and verify source history before cancellation.
- Give staff a readable archive and a clear owner for later questions.
Follow the migration checklist and plan archive retention.
A useful historical record includes its capture date, source identity and relationships. Review the native workflow before planning your archive.
Invitation only
Keep your PSA history within reach
BackupPSA is invitation only. Join the waitlist and we’ll contact you about your invitation.