Deleted Record History guide
Atera deleted records: recovery and history
Use documented Atera recovery options and validate the result, with earlier exports available for historical reference.
On this page
Start with native recovery
Atera lets you filter tickets by Deleted status, open the identified ticket and change its status to Open or Pending. Its guide also covers merged-ticket handling and restrictions on changing tickets already billed. See Manage merged/ deleted tickets.
Confirm identity and visibility
Record the native ID, customer, requester and last known dates before acting. Check whether filters, permissions, an archive or a merge explain the missing item. Ask an authorized administrator to confirm the record’s current state.
Check the recovered record
Use the audit log to establish the original ticket ID and status transition. Reconcile the conversation when unmerging, and check the restored record with the customer and billing context. Confirm retention with Atera for your case.
Use earlier captured history
Atera’s export FAQ excludes deleted records, so capture useful history before deletion and use the native restore path first when a ticket is already missing. An earlier export can show what was retained before the record changed. Keep its capture date and source identifiers visible, and restrict internal notes to the appropriate audience. For file evidence, open the saved file itself and retain its parent-record reference.
Plan the next capture through the Atera export guide. Related native documentation: Atera Data Export FAQ. The deleted-record history use case connects recovery preparation to longer-term archive access.
Plan ahead for useful record history
Preserve captured records before they change or disappear. Request an invitation to BackupPSA. We’ll contact you if you’re selected for an invitation.