Automated large attachment processing during migration
A network-based solution for automatically processing large email attachments or other files during migration between email platforms or other platforms, as may be embodied by various systems, methods, and non-transitory computer-readable storage media, may involve downloading mailboxes from a source email platform and inspecting the mailboxes for emails containing attachment files. The solution may involve determining a file size of any detected attachment, comparing the file size of the detected attachment file to a predetermined attachment size limit, and uploading a copy of the detected attachment to a storage server for storage when the comparison determines that the file size of the detected attachment file exceeds the predetermined attachment size limit. The solution may further include modifying the email by replacing the detected attachment with a link to the copy of the detected attachment stored at the storage server and then migrating the modified email to the target email platform.
1. A system for automatically processing large email attachments during migration, the system comprising:
a source email platform hosted by a first computing device, the source email platform storing a plurality of mailboxes, each mailbox including a plurality of emails, and the source email platform including a first attachment size limit stored in a first memory;
a target email platform hosted by a second computing device;
a storage server; and
an application server communicatively coupled to the source email platform, the target email platform, and the storage server by a network, the application server having stored in a second memory a second attachment size limit and an executable application that, when executed by a processor of the application server:
receives a first identification of a first server type characterizing the source email platform and a second identification of a second server type characterizing the target email platform;
downloads the mailboxes from the source email platform;
inspects each downloaded mailbox for an email containing an email attachment file, wherein the application server downloads and inspects the mailboxes on a rolling basis as the mailboxes are received from the source email platform;
identifies a file size of a detected email attachment file;
compares the file size of the detected email attachment file to the second attachment size limit stored in the second memory;
determines whether a link has previously been generated for a copy of the detected email attachment file,
wherein responsive to a determination that the link has previously been generated, no copy of the detected email attachment file is uploaded to the storage server, and
wherein responsive to a determination that the link has not previously been generated and responsive to the comparison identifying that the file size of the detected email attachment file exceeds the second attachment size limit stored in the second memory, the application server generates the link, wherein the link permits read access of the detected email attachment file without write or edit permissions, wherein a copy of the detected email attachment file is uploaded to the storage server to be stored, wherein the link includes an HTML link containing a Universal Naming Convention (UNC) path that points to a location of the uploaded copy of the detected email attachment file stored in the storage server;
modifies the email by replacing the detected email attachment file in the email with the link to the copy of the detected email attachment file stored at the storage server, wherein an activation of the link provides access to a read-only version of the detected email attachment file; and
migrates the modified email to the target email platform, wherein the read-only version of the detected email attachment file retains an association to the detected email attachment file.
2. The system of claim 1 , further including a database associated with the storage server, wherein the copy of the detected email attachment file is stored at the database.
3. The system of claim 1 , wherein the storage server provisions a user account for each user associated with one of the mailboxes stored in the source email platform.
4. The system of claim 2 , wherein an address list of the migrated email includes a plurality of recipients, and the upload of the copy of the detected email attachment file attached by the application server includes uploading a plurality of copies of the detected email attachment file to the storage server for each of the recipients listed in the address list of the migrated email.
5. The system of claim 2 , wherein an address list of the migrated email includes a plurality of recipients, the application server uploads a single copy of the detected email attachment file to the storage server, and the storage server grants access to the plurality of recipients listed in an address list of the migrated email in accordance with certain predetermined permission information.
6. The system of claim 1 , wherein the application server identifies the file size of the detected email attachment file by reading metadata associated with the email attachment file.
7. The system of claim 1 , wherein the application server inspects the mailboxes after all of the mailboxes designated for download have been successfully received from the source email platform.
8. The system of claim 1 , wherein the second attachment size limit is automatically determined by an attachment size limit built into the target email platform.
9. The system of claim 1 , wherein the second attachment size limit is custom determined by an administrator.
10. The system of claim 1 , wherein the application server replaces the detected email attachment file in the email with the link to the copy of the detected email attachment file stored at the storage server by authenticating the detected email attachment file.
11. The system of claim 10 , wherein the application server replaces the detected email attachment file in the email with the link to the copy of the detected email attachment file stored at the storage server by further inserting the link into a stub file, removing the detected email attachment file, and attaching the stub file in place of the removed email attachment file.
12. The system of claim 11 , wherein the stub file is a word processing document.
13. The system of claim 11 , wherein the stub file further includes the link.
14. The system of claim 1 , wherein the link is a view link that permits a user to read the uploaded copy of the detected email attachment file without permitting the user to write to or edit the copy of the detected email attachment file.
15. A method to process large email attachments during migration, the method comprising:
downloading from a source email platform a plurality of mailboxes, each mailbox including a plurality of emails, and the source email platform including a first attachment size limit stored in a first memory; and
executing instructions that are stored, wherein execution of the instructions:
receives a first identification of a first server type characterizing the source email platform and a second identification of a second server type characterizing the target email platform;
inspects each downloaded mailbox for an email containing an email attachment file, wherein the mailboxes are inspected on a rolling basis as the mailboxes are downloaded from the source email platform;
identifies a file size of a detected email attachment file;
compares the file size of the detected email attachment file to a second attachment size limit;
determines whether a link has previously been generated for a copy of the detected email attachment file,
wherein responsive to a determination that the link has previously been generated, no copy of the detected email attachment file is uploaded to a storage server, and
wherein execution of the instructions responsive to a determination that the link has not previously been generated and responsive to the comparison identifying that the file size of the detected email attachment file exceeds the second attachment size limit stored in a second memory, generates the link, wherein the link permits read access of the detected email attachment file without write or edit permissions, wherein a copy of the detected email attachment file is uploaded to the storage server to be stored, wherein the link includes an HTML link containing a Universal Naming Convention (UNC) path that points to a location of the uploaded copy of the detected email attachment file stored in the storage server;
modifies the email by replacing the detected email attachment file in the email with the link to the copy of the detected email attachment file stored at the storage server, wherein the link provides access to a read-only version of the detected email attachment file; and
migrates the modified email to a target email platform, wherein the read-only version of the detected email attachment file retains an association to the detected email attachment file.
16. The method of claim 15 , wherein an address list of the migrated email includes a plurality of recipients and the uploading of the copy of the detected email attachment file to the storage server includes a plurality of copies of the detected email attachment file to the storage server for each of the recipients listed in the address list of the migrated email.
17. The method of claim 15 , wherein an address list of the migrated email includes a plurality of recipients, and the uploading of the copy of the detected email attachment file to the storage server includes uploading a single copy of the detected email attachment file to the storage server to be rights managed by the storage server with respect to access by the plurality of recipients according to predetermined permission information.
18. The method of claim 15 , wherein identifying the file size of the detected email attachment file includes reading metadata associated with the email attachment file.
19. The method of claim 15 , wherein the mailboxes are inspected after all of the mailboxes designated for download have been successfully received from the source email platform.
20. The method of claim 15 , wherein the second attachment size limit is automatically determined by an attachment size limit built into the target email platform.
21. The method of claim 15 , wherein the second attachment size limit is custom determined by an administrator.
22. The method of claim 15 , wherein the replacing of the detected email attachment file in the email with the link to the copy of the detected email attachment file stored at the storage server includes generating a stub file.
23. The method of claim 22 , wherein replacing the detected email attachment file in the email with the link to the copy of the detected email attachment file stored at the storage server further includes inserting the link into the stub file, removing the detected email attachment file, and attaching the stub file in place of the removed email attachment file.
24. The method of claim 22 , wherein the stub file is a word processing document.
25. The method of claim 22 , wherein the stub file further includes the link.
26. The method of claim 15 , wherein the link is a view link that permits a user to read the uploaded copy of the detected email attachment file without permitting the user to write to or edit the copy of the detected email attachment file.
27. A non-transitory computer-readable storage medium having embodied thereon a computer program executable by a processor to perform a method to process large email attachments during migration, the method comprising:
receiving a first identification of a first server type characterizing a source email platform and a second identification of a second server type characterizing a target email platform;
identifying from the source email platform a plurality of mailboxes, each mailbox including a plurality of emails, and the source email platform including a first attachment size limit stored in a first memory;
inspecting each downloaded mailbox for an email containing an email attachment file, wherein the mailboxes are inspected on a rolling basis as the mailboxes are downloaded from the source email platform;
determining a file size of a detected email attachment file;
comparing the file size of the detected email attachment file to a second attachment size limit;
determining whether a link has previously been generated for a copy of the detected email attachment file, wherein responsive to a determination that the link has previously been generated, no copy of the detected email attachment file is uploaded to a storage server, and
wherein responsive to a determination that the link has not previously been generated and responsive to the comparison identifying that the file size of the detected email attachment file exceeds the second attachment size limit stored in a second memory, generating the link, wherein the link permits read access of the detected email attachment file without write or edit permissions, wherein a copy of the detected email attachment file is uploaded to the storage server to be stored, wherein the link includes an HTML link containing a Universal Naming Convention (UNC) path that points to a location of the uploaded copy of the detected email attachment file stored in the storage server;
modifying the email by replacing the detected email attachment file in the email with the link to the copy of the detected email attachment file stored at the storage server, wherein the link provides access to either a read-only version of the detected email attachment file; and
migrating the modified email to the target email platform, wherein the read-only version of the detected email attachment file retains an association to the detected email attachment file.
28. The system of claim 1 , wherein the link to the copy of the detected email attachment file is encrypted.