I have a situation where a user has left the company, and we're allowing them to transfer their workspace emails to another workspace account. I understand that I need to authorize them to initiate this transfer, and they'll upload a CSV file to map the source email to the target email for migration. However, I'm concerned about the possibility of them uploading a CSV with multiple source emails to access more of our users' emails, especially if they have the same number of target emails. I can't verify their CSV for honesty since they won't grant me access to their workspace account. Is there a way to limit this risk or any effective workarounds?
1 Answer
That sounds tricky! A good approach might be to export the mailbox yourself and hand over the data to them to import on their end. This way, you avoid using any direct migration tools that don’t offer limitations. It takes the responsibility off your plate!
Ya, I had them download an Mbox file for the migration, but it was a massive 27k emails!