steveenmiller
New member
I am planning a move from an existing IMAP email environment to Microsoft 365, but I do not want to transfer every mailbox at the same time. Some employees have large mailboxes with years of correspondence, while others use their accounts mainly for recent communication. A staged migration seems easier to organize, but I am trying to understand how to manage the process without overlooking emails that arrive while the transfer is underway.
One concern is the time difference between the initial migration and the final cutover. If I transfer a mailbox today and employees continue using the old IMAP account for several more days, new messages may arrive after the first transfer. I would like to avoid running the entire migration again just to capture those newer emails. Is there a practical way to perform an initial transfer and then run a follow-up migration for items that have not already been copied?
I am also interested in how duplicate messages are handled during repeat migration runs. If the same mailbox is processed more than once, I would prefer not to create multiple copies of existing conversations in Microsoft 365. A method that skips previously migrated items could make staged transfers more easily, but I would still want to verify the final mailbox contents before switching users completely to the new platform.
Folder structure is another important consideration. Employees are familiar with their existing Inbox, Sent Items, Drafts, and custom folders. Reorganizing everything after migration would create unnecessary confusion. I would therefore want to check whether the original folder hierarchy, attachments, dates, and read/unread status can be retained in the destination mailbox.
While researching this workflow, I found the SysInfo IMAP to Office 365 Migration Tool . Its listed features include skipping previously migrated items, duplicate removal, folder-structure preservation, and migration reports. I am considering evaluating it for a staged migration, but I would like to hear how other administrators plan the initial transfer and final synchronization.
One concern is the time difference between the initial migration and the final cutover. If I transfer a mailbox today and employees continue using the old IMAP account for several more days, new messages may arrive after the first transfer. I would like to avoid running the entire migration again just to capture those newer emails. Is there a practical way to perform an initial transfer and then run a follow-up migration for items that have not already been copied?
I am also interested in how duplicate messages are handled during repeat migration runs. If the same mailbox is processed more than once, I would prefer not to create multiple copies of existing conversations in Microsoft 365. A method that skips previously migrated items could make staged transfers more easily, but I would still want to verify the final mailbox contents before switching users completely to the new platform.
Folder structure is another important consideration. Employees are familiar with their existing Inbox, Sent Items, Drafts, and custom folders. Reorganizing everything after migration would create unnecessary confusion. I would therefore want to check whether the original folder hierarchy, attachments, dates, and read/unread status can be retained in the destination mailbox.
While researching this workflow, I found the SysInfo IMAP to Office 365 Migration Tool . Its listed features include skipping previously migrated items, duplicate removal, folder-structure preservation, and migration reports. I am considering evaluating it for a staged migration, but I would like to hear how other administrators plan the initial transfer and final synchronization.