How do I migrate from Zimbra to Office 365

https://migrationwiz.zendesk.com/entries/25289097

How do I migrate from Zimbra?

MigrationWiz Support
posted this on Aug 16 13:10
There are two modes to connect to your Zimbra server:
  1. In regular user mode, we just need access to SOAP web services typically on port 80 if HTTP or 443 if HTTPS.
  2. In admin user mode, we also need access to SOAP web services typically
    1. On port 80 and 7071 if the Zimbra URL is HTTP
    2. On port 443 and 7071 if the Zimbra URL is HTTPS
We’ll need to connect using both ports, some operations will go over the admin port, while others will go over the regular port 80 or 443.
To migrate from Zimbra, perform these steps:
  1. Specify a Zimbra URL on your Connector
  2. If you will migrate in admin user mode:
    1. Create a Zimbra administrator account
    2. Open port 7071 in your firewall. Should your firewall requires an IP lockdown click here.
  3. Test the connection to my Zimbra server
    1. Green lights mean you should be able to migrate from your Zimbra server!



https://migrationwiz.zendesk.com/entries/25417903

How do I migrate to Office 365?



MigrationWiz Support
posted this on Aug 18 16:16
Perform the following steps to migrate to Office 365:
  1. In a new Office 365 tenant: you have to provision all the Office 365 users. You can either:
    • Manually one-by-one or by CSV file bulk import.
    • Or synchronizing Active Directory objects:
      • If there are NO on-premise Exchange mailboxes associated with the AD users, you could use Microsoft DirSync.
      • If there are on-premise Exchange mailboxes, you are only able to use our MigrationWiz DirSync tool. The Microsoft DirSync detects your on-premise Exchange mailboxes, and assumes that you will migrate mailbox data using MRS. As a result, cloud mailboxes are locked and nobody but Microsoft's MRS can login to those mailboxes.
  2. Note that if the Office 365 tenant is already in use, you have on-premise Exchange mailboxes and Microsoft DirSync and ADFS enabled, cloud mailboxes are locked out.
  3. Make sure all users have licenses assigned to them (not kiosk licenses, full licenses).
  4. Provision a Global O365 administrative account and use it as an admin account for the destination on your connector.
  5. Grant full permissions to the administrative account.
    • For Office 365, when you submit a mailbox for migration, MigrationWiz attempts to automatically runs remote PowerShell commands to grant the admin account full permissions on all mailboxes. We often see some significant permission replication delays, sometimes exceeding 1 hour. Therefore, even though the admin account may have been granted sufficient permissions to login all end-users' mailboxes, it may take up to 1 hour before they become effective. Therefore often your best bet is simply to wait 1 hour and resubmit for migration.
  6. Test your credentials and make sure they are working.
  7. Office 365 has a 25 MB per item limit. From a practical perspective, the limits are a bit lower due to protocol overhead and encoding. As a result, items larger than 20 MB in size may fail to migrate. There is unfortunately no workaround since this limit is imposed by the destination.
  8. If you are going to migrate less than 5 mailboxes:
    • Make sure the admin account has a license assigned to it (this can even be a temporary trial license).
  9. If you are going to migrate more than 5 mailboxes:
    1. Office 365 will impose serious throttling. We recommend enabling impersonation in Advanced options -> Exchange Server to reduce it:impersonation.JPG
      • There is no requirement that the admin account must have a license assigned to it.
    2. As previously, we attempt to grant impersonation rights under the covers. The PowerShell commands may take a very long time to complete. You can either:
      • Grant manually impersonation rights yourself using remote PowerShell. You do not need to install any additional software in order to do this. Please be patient - the remote PowerShell commands can take several minutes to complete.
      • Wait ~30 minutes and resubmit the migration.

Was this article helpful?

Can’t find what you’re looking for?

Our award-winning customer care team is here for you.

Contact Support