This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 16%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB5%3C/text%3E%3C/svg%3E)
Could you please provide assistance in resolving the error encountered during the Microsoft Exchange migration to O365 process? Thank you.
Migration rate:
Error: CorruptRestrictionPropertyTypeException: Corrupt property type in restriction. --> Corrupt PropertyTag found. --> Unable to create custom property with property key [{00020329-0000-0000-c000-000000000046}:'Keywords'] type [31].
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 5%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELC%3C/text%3E%3C/svg%3E)
Same issue recently encountered during the migration of few (not all) mailboxes from Exchange Server 2016 (Build 15.1.2507.35) to Exchange Online.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 98%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPR%3C/text%3E%3C/svg%3E)
I am having the same issue, does anyone have a fix?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Hi @Bab's
What is your type of email migrations? (Exchange 2010, Exchange 2013, and/or Exchange 2016?)
Do you have any operations before this issue occurred?
The type of migration is Remote Migration, but after increasing the concurrent maximum number of mailbox migration on the (endpoint migration - EWS) the error seems to have cleared. but I am still monitoring for the progress.
Not sure this is going to solve it for me, I get the error when trying a problematic mailbox on it's own. I think my issue is due to custom forms, possibly due to the fact our on-prem environment has archived emails in Veritas Enterprise Vault, this seems to use custom forms for the shortcuts (stubs)
I have the same problem with a customer! Only some mailboxes are impacted in each migration job.
It has been a while, how is everything going?
If you have any update about this issue, please feel free to post back.
On my side, the issue has been encounter during the mailboxes migration between 25th 29th March, from Exchange Server 2016 (Build 15.1.2507.35) to Exchange Online.
Executing the same mailbox migration after 30 of March, without change any other parameters, the mailbox migration completed with success.
I suspect in a transitory issue on the Exchange Online service, now fixed
It started working for us after posted answer, re-running the moves. The fix must have been applied for all.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 92%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJK%3C/text%3E%3C/svg%3E)
Had the same issue occur for us mid-march. Trying to migrate the mailboxes again to see if the issue has been resolved.
It seems that the problem has been corrected on the Microsoft side.
In my case, the problem was due to the usage of Dynamics 365 searchfolder properties.
These properties are now automatically ignored (excluded) from the migration.