<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Need help exporting Office 365 to PST for archive purposes in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/need-help-exporting-office-365-to-pst-for-archive-purposes/m-p/499420#M40865</link>
    <description>&lt;P&gt;Our compliance team wants us to archive mailboxes for employees who've left the company over the past year — about 35 mailboxes total, all needs to go to PST for long-term storage. Never done this at this scale before, so looking for advice before I mess something up.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;A few concerns I have:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Most of these accounts are already disabled or deleted, so I'm not sure the native Microsoft tools will even work&lt;BR /&gt;I don't want to babysit 35 individual exports manually&lt;/LI&gt;&lt;LI&gt;Archive means I need this to actually be complete and verifiable later, not just "probably fine"&lt;BR /&gt;We don't have E5 licensing across the board, so I'm not sure eDiscovery is even an option for all these mailboxes&lt;P&gt;From what I've read so far, eDiscovery Content Search can work for archiving but gets complicated fast with disabled accounts and licensing requirements. A few people in another thread mentioned dedicated export software handles this better since it's built for bulk jobs and doesn't care whether the account is active or not.&lt;/P&gt;&lt;P&gt;Was looking at this &lt;STRONG&gt;DRS Softech Office 365 to PST export tool&lt;/STRONG&gt; since it seems to handle exactly this — bulk export including inactive accounts, with reporting so I can confirm everything actually made it into the PST files.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Sat, 11 Jul 2026 09:59:08 GMT</pubDate>
    <dc:creator>WilliamsWelsh</dc:creator>
    <dc:date>2026-07-11T09:59:08Z</dc:date>
    <item>
      <title>Need help exporting Office 365 to PST for archive purposes</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/need-help-exporting-office-365-to-pst-for-archive-purposes/m-p/499420#M40865</link>
      <description>&lt;P&gt;Our compliance team wants us to archive mailboxes for employees who've left the company over the past year — about 35 mailboxes total, all needs to go to PST for long-term storage. Never done this at this scale before, so looking for advice before I mess something up.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;A few concerns I have:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Most of these accounts are already disabled or deleted, so I'm not sure the native Microsoft tools will even work&lt;BR /&gt;I don't want to babysit 35 individual exports manually&lt;/LI&gt;&lt;LI&gt;Archive means I need this to actually be complete and verifiable later, not just "probably fine"&lt;BR /&gt;We don't have E5 licensing across the board, so I'm not sure eDiscovery is even an option for all these mailboxes&lt;P&gt;From what I've read so far, eDiscovery Content Search can work for archiving but gets complicated fast with disabled accounts and licensing requirements. A few people in another thread mentioned dedicated export software handles this better since it's built for bulk jobs and doesn't care whether the account is active or not.&lt;/P&gt;&lt;P&gt;Was looking at this &lt;STRONG&gt;DRS Softech Office 365 to PST export tool&lt;/STRONG&gt; since it seems to handle exactly this — bulk export including inactive accounts, with reporting so I can confirm everything actually made it into the PST files.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Sat, 11 Jul 2026 09:59:08 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/need-help-exporting-office-365-to-pst-for-archive-purposes/m-p/499420#M40865</guid>
      <dc:creator>WilliamsWelsh</dc:creator>
      <dc:date>2026-07-11T09:59:08Z</dc:date>
    </item>
  </channel>
</rss>

