Advanced Options for Zimbra

This quick start guide provides you with the basic information to configure CloudM Migrate for a migration from Zimbra. It is highly recommended that you read the application documentation in full for your platforms in order to understand all of the options available to you during a migration.

Email

  • Migrated Incoming Shared Folders – Set this to true to migrate folders that have been shared with the user being migrated. This can result in data duplicated between accounts, and is generally not recommended.
  • Categories – Migrate categories from Zimbra to labels or categories. Supported only on Zimbra 7 and above.
  • Use Metadata Date – Use metadata from Zimbra to determine the email date. Useful in the case of non-RFC822 date email headers.
  • Allow Duplicate Messages - Allows you to migrate copies of emails which exist in multiple folders. As copies have the same message ID as the original email, CloudM Migrate will only migrate one version of the email by default.
    • If you have two identical emails in the same folder, only one will be migrated (as we use both the message ID and folder ID to differentiate between copies).
    • This option is only available when migrating from Zimbra to Microsoft 365.

Contact

  • Migrate All Group Members – Migrate all personal contact group members, even if they are not in the user's personal address books. This may create contacts that are from the GAL or inline group members when they are part of contact groups, but not present in the user's personal address books.
  • Migrated Incoming Shared Folders – Set this to true to migrate folders that have been shared with the user being migrated. This can result in data duplicated between accounts, and is generally not recommended.

Calendar

  • Migrated Incoming Shared Folders – Set this to true to migrate folders that have been shared with the user being migrated. This can result in data duplicated between accounts, and is generally not recommended.

Task

  • Migrated Incoming Shared Folders – Set this to true to migrate folders that have been shared with the user being migrated. This can result in data duplicated between accounts, and is generally not recommended.

Other

  • Unavailable Wait – If a Zimbra server is placed under too much load, the server may respond with '503 Unavailable' messages. Clients must back-off at that point or the server will continuously report 503. Specify the delay that will be applied if the server responds with 503.
  • Direct Mailbox connection – Use a direct connection to the mailbox server for each user rather than connecting through the main proxy address.

 

Was this article helpful?
0 out of 0 found this helpful