Considerations for Folder Binding

Understanding folder synchronization during IMAP migration.

Last updated: 2025-01-15 Plan & Prepare

Overview

Cloudiway synchronizes folders between source and target mailboxes before migrating emails. This synchronization step may fail for various reasons related to folder configuration and naming.

Common Folder Issues

👁️
Hidden Folders
NoSelect flag
📁
Name Conflicts
System folder names

Hidden IMAP Folders

NoSelect Flag Issue

In IMAP and Google environments, users can flag folders to hide them from IMAP access. When this occurs, Cloudiway cannot access the folder's content through IMAP, causing the folder and its contents to be ignored during migration.

Error Message

"Cannot access folder XXXX (NoSelect flag found), migration ignored"

Resolution

Request that the user remove the flag from the hidden folder to make it accessible for migration. This is done in the source email client settings.

System Folder Name Conflicts

Custom Folders with System Names

If a user creates a custom folder using the same name as a system folder, the contents will automatically merge into the system folder in the target mailbox.

Example Scenario

A user creates a custom folder named "Trash" for project-related items:

  • If trash migration is disabled, content is ignored
  • Even though it isn't the actual system trash folder
  • The folder name conflict causes unexpected behavior

Common System Folder Names

Inbox Sent Drafts Trash Spam Junk Archive

Pre-Migration Check

Before migration, review the source mailbox for folders with system-like names and rename them if they contain important content that shouldn't be merged with system folders.

We value your feedback

Help us improve your experience

What would you like to share with us?

Need direct support? Open a ticket