🚀 Overview: Resolving the “Private Items” Folder Move Error in Outlook

In enterprise environments, IT administrators frequently encounter a specific limitation when users attempt to reorganize data between mailboxes. Specifically, when a user tries to move a folder containing subfolders from a shared mailbox into their primary personal mailbox, Microsoft Outlook may block the action. The client triggers a prompt stating: “Cannot move the items. Cannot copy this folder because it may contain private items.”

This behavior is not a corruption issue or a random bug; it is a “by design” security and structural enforcement within Outlook. It occurs specifically when the source folder in the shared mailbox has a nested hierarchy (one or more subfolders). This guide provides technical workarounds to bypass this restriction while maintaining data integrity across Outlook 2010, 2013, 2016, 2019, and Microsoft 365.

---

⚙️ Key Technical Details

The error is triggered by the presence of subfolders during a cross-mailbox move operation. Because Outlook cannot verify the “Private” flag status of all items across a nested directory in a shared context during a move, it prevents the action to protect potential data privacy. To resolve this, admins or users must use one of the following technical strategies:

🛠️ Method 1: Manual Structural Replication and Item Migration

This method avoids the “folder move” logic by recreating the destination architecture first and then migrating only the items.

• Step 1: Replicate the Directory
  • In the destination mailbox, right-click the parent directory (e.g., Inbox or the top-level Email Address) and select New Folder.
  • Name the folder (typically matching the shared mailbox folder name).
  • Right-click this new folder and create New Folder entries to replicate any subfolders from the source.
• Step 2: Transfer the Data
  • Navigate to the source folder in the shared mailbox.
  • Execute CTRL+A to select every item.
  • Navigate to the Home tab on the Ribbon, select Move, and then Other Folder.
  • Choose the corresponding new folder in the personal mailbox and click OK.
  • Repeat this granularly for every subfolder in the hierarchy.

📦 Method 2: PST Export and Import Routine

For large folder hierarchies, using an Outlook Data File (.pst) is the most efficient way to bypass the UI move restriction.

• Step 1: Exporting from the Shared Mailbox
  • Select the target folder in the shared mailbox.
  • Open the Import and Export Wizard:
    • Outlook 2013/2016/2019/M365: File > Open & Export > Import/Export.
    • Outlook 2010: File > Options > Advanced > Export.
  • Choose Export to a file > Next.
  • Select Outlook Data File (.pst) > Next.
  • Ensure the correct shared folder is highlighted and Include subfolders is enabled.
  • Save the file to a known local path via Browse and select Finish.
• Step 2: Importing to the Primary Mailbox
  • Open the Import and Export Wizard again.
  • Select Import from another program or file > Next.
  • Select Outlook Data File (.pst) > Next.
  • Target the .pst file created in Step 1.
  • Choose Import items into the same folder in: and select the user’s primary mailbox from the dropdown menu.
  • Click Finish to complete the data merge.

🛡️ Method 3: Escalated Delegate Access and Owner Permissions

⚠️ Important: This method grants significant permissions. A delegate with these rights can act on behalf of the shared mailbox. Ensure this aligns with your organization’s security policy.

• Phase 1: Configure Delegate Settings
  • Log into the shared mailbox profile.
  • Navigate to File > Account Settings > Delegate Access.
  • Click Add, select the target user, and click OK.
  • In Delegate Permissions, set the Inbox to Editor.
  • Crucially, check the box: Delegate can see my private items and click OK.
• Phase 2: Assign Root-Level Permissions
  • Right-click the top-level folder of the shared mailbox (the email address) and select Folder Permissions.
  • If the user isn’t listed, click Add and select them.
  • Set the Permission Level to Owner and click OK.
• Phase 3: Assign Folder-Level Permissions
  • Right-click the specific folder to be moved, select Properties, and go to the Permissions tab.
  • Add the user if necessary and set the Permission Level to Owner.
  • Once permissions propagate, the user should be able to move the folder hierarchy.

---

📅 Impact

Understanding the impact of this error and its solutions is vital for Helpdesk efficiency:

• User Productivity: Users may feel “stuck” when trying to decommission shared mailboxes or archive data. Providing Method 2 (PST) is usually the fastest “self-service” fix.
• Data Privacy: Method 3 bypasses private item restrictions. Admins should audit these permissions and remove the Delegate status once the move is completed to maintain a “Least Privilege” security model.
• Administrative Overhead: Manual replication (Method 1) is time-consuming for large structures, whereas Method 2 can be handled by the user without IT intervention if they have export rights.

---

Official Source: Read the full article on Microsoft.com