Export the specific archived messages required for a migration or authorised review. The current hosted-cloud workflow uses log search; the old standalone Archive Export facility is deprecated.
IN THIS ARTICLE
01 Request an export
- Open incoming or outgoing log search with the correct authorised scope.
- Filter to the intended domain and set In archive = Yes. Add date and participant restrictions.
- Review the results, then select the required messages. If selecting all matching results, verify the full search scope first.
- Choose Export message from archive from the selected-item actions and apply it.
- Enter the requested filename, description, password and archive-size options, then start the export.
02 Verify the delivered files
Use the notification and export-status controls to obtain the completed download. Store it in restricted storage, open a sample and check the message date, body and attachments. Record the exact domain and search window covered.
Common questions
Why is the export still pending?
Inspect its status and progress rather than starting overlapping requests. Larger selections can take time, and a failed request needs its specific error reviewed.
What if I cannot see export actions?
The role or archive-protection policy may restrict them. Request a scoped export from the authorised administrator.
Does exporting remove the archive copy?
An export and deletion are separate actions. Do not select a delete operation unless it is specifically approved and all preservation requirements have been resolved.
Check that the destination can read the exported format before cancelling an old service. Keep the password separate from the download link and avoid sending archives through ordinary email when a controlled transfer is available. Record who received the export and remove temporary duplicates according to the agreed retention plan.