Public Folder Migration Failed – A Corrupted item was encountered: Folder ACL

Summary: A Corrupted item was encountered: Folder ACL is an error message encountered while migrating and synchronizing mailboxes or Public Folders between Exchange Server or from on-premises Exchange Server to Exchange Online (Office 365). In this article, we have discussed the solutions to fix the error and complete the mailbox migration. You can also avoid the error by downloading the EDB to PST converter tool. You can use it to directly export the mailboxes or Public Folders to another Exchange Server or Office 365 tenant.

Public Folders work fine. But when it comes to migrate them to an Office 365 tenant, it may be a bit chaotic. Issues may arise, especially when you have large Public Folders.

In case of a hybrid setup – be it Exchange Server 2010, 2013, 2016 or 2019, following are the steps to migrate the Public Folders:

However, sometimes, at the last step you might end up facing the below given error.

A Corrupted item was encountered: Folder ACL

However, you can avoid this error by following the fixes discussed below or using an EDB to PST converter software, such as Stellar Converter for EDB. The software lets you export the mailboxes and Public Folders from Exchange database (EDB) to Office 365 in a few clicks.

How to Fix the ?A Corrupted item was encountered: Folder ACL? Error?

Troubleshooting this error can be of a hassle. Although the process is supported by Microsoft, it involves a good number of scripts and depends on several factors of the Exchange Server, such as it is healthy and running well. Also, there are too many points of failure which could take a while to understand where the issue is.

When migrating Public Folders to Office 365, you must also take the limits into consideration, as given below.

You would also need to consider the size of the items. An item cannot be larger than 49 MB. During migration, large items may be skipped or the whole process may stop.

Public Folders are known to give issues, especially when they?re large-sized. Although they are still highly used, it seems that Microsoft is phasing them out when it introduced Shared Mailboxes and Microsoft Teams/ Groups. This is great, but you will end up with the dilemma on how to export the Public Folder to a PST file.

One of the solutions would be to export the Public Folder to PST and import it directly into Office 365 by using the Blob Storage for import and the XML file to start the migration. Unfortunately, you cannot use the New-MailboxExportRequest cmdlet to export Public Folder to PST. Instead, you can use the Outlook to export Public Folder to PST. For this, you need to have a dedicated resource with Microsoft Office installed.

However, there are some limitations when it comes to exporting Public Folder to PST by using Outlook.

An Alternative Solution

So, is there an alternative to avoid these problems? The alternative is a small but very powerful application called Stellar Converter for EDB. With this sofwtare, you can easily open the live or a copy of the Public Folder (EDB) Exchange Database file and browse through it with no issues.

You can also search and view the items. You can export all or selective data to PST files. The application can easily handle large PST files. You can also export the data to other file formats such as EML, MSG, etc.

You can also use Stellar Converter for EDB as a migration tool. Instead of exporting to PST and then importing into Office 365, you can directly export the Public Folder to your Office 365 tenant without any limitation of PST file size or public folder size. It is the ideal migration application to shorten the migration process, without complex configurations or manual scripting.

Related Post