The support team is now able to perform managed migrations from third-party Microsoft Exchange providers. Please note that the third-party provider must have a publicly accessible OWA address. To perform a managed migration, the support team will need the following information:
- The OWA URL Address of the current Exchange provider.
- An import file containing the list of mailboxes to be imported. This file must be in .CSV format.
- Administrative credentials for the current Exchange provider if user passwords are not included in the import file.
The import file will need to use one of two formatting options, depending on whether the Administrative credentials are to be supplied.
If the mailbox migration is to be performed using an administrative account, please use the following format example:
Source Email,Source UserName,Source Password,Destination Email,Destination UserName,Destination Password,Flags
user1@domain.com,,,user1@domain.com,,,0
user2@domain.com,,,user2@domain.com,,,0
If the mailbox migration is to be performed using the individual mailbox passwords, please use the following format example:
Source Email,Source UserName,Source Password,Destination Email,Destination UserName,Destination Password,Flags
user1@domain.com,user1@domain.com,<password>,user1@domain.com,,,0
user2@domain.com,user2@domain.com,<password>,user2@domain.com,,,0
To request a managed migration, please perform the following steps:
1. Open a new ticket with the Subject "Managed Migration Request."
2. In the body of the ticket, provide the following information:
- Partner ID
- Domain name of the customer to be migrated
- OWA URL of the customer's current Exchange provider
- Administrative credentials of the customer's current Exchange account (if the individual mailbox passwords are not included in the import file).
3. Email the properly formatted import file to helpdesk@seattleserver.com.
- Please include your Partner ID and the customer domain in the body of the email.
Once we receive all of the above information, we will schedule the managed migration.
Note: We do NOT remote into your server.
While we are unable to provide specific estimates for the length of time required to perform migrations, on average even smaller initial migration sets can take multiple days to complete.
The support team will attempt to keep you updated with the migration process. We recommend planning all migrations accordingly.
