 Danny says, I have a client I recently took on who has Exchange 2010, which I'm going to migrate to Office 365. The issue is someone in the past has lifted the message size restriction and they have emails over 150 mix. Office 365 doesn't support messages this size, so I was unable to import them. Has anyone come across this and what solution have you used other than opening each mailbox searching for large emails manually exporting them and then saving them somewhere else? There are a lot of mailboxes included users who have left, so not a slick process in being Exchange 2010. And the answer is probably not going to be of any help to you. Unfortunately, the maximum Microsoft 365 has released a methodology for you to get message restrictions lifted up to 150, but over 150, I really don't know what to tell you there. And unfortunately, exporting them and zipping them might be the... I was actually looking to see if there was an add-in that would let you zip stuff and I have not come across one so far. That's one area to keep in mind. A prior article that I have included to show here to Christian does go into at least some degree of PowerShell that might help you in locating the messages that are offending, but as to whether or not you can move them in, I don't know. You might try zipping one and using it as an attachment and seeing what will happen on the far end. But frankly, I think nothing will happen and you're just going to be stuck with those few messages that are going to be over there. Like I say, the PowerShell may help you in finding them and going through the mailboxes. From a change perspective and why we've dealt this when we've done Exchange migrations, it wasn't. It was the user had to go and do that themselves and get it ready as part of the program. If you had something that was going to be that big, it wouldn't be migrated and would actually be lost. So it's either go through and delete them or delete attachments or save them. So they were kind of the instructions that we would give prior to migration and we would know specifically who those people were because there weren't that many of them usually to have really big ones like that. And then we'd actually would work with them or bring them into some training or help them to just understand the steps that they might need to do, whatever that looked like prior to migration. Well, one other option. But it was an awful lot then. It was an email that went out, are you going to lose it basically? Yeah. Well, that's one thing. Let the user driven, that's the least expensive way to go and search. The one thing I was going to throw out there is that there are third-party tools. AppPoint has one that will, as part of that migration, help you facilitate that. We'll go in, identify all of those that exceed the limitations, flag them and then can automate the how they're treated. So there's a, it's not a free tool, but it's not very expensive. And so there are third-party tool options for that as well that will automate all of that. This is not a new problem because plenty of other companies have done this, but it's just a reality with the movement of the cloud with a lot of them just didn't think about and didn't plan for when they set some of those standards or lack of standards. Yeah.