Best Practices
The following best practices will help optimize migration performance, reduce errors and enhance your overall migration experience.
General
- Let the migration complete before organizing data – If migrating in stages, once the first job has started do not reorganize messages or folders in the source or target environment until the entire migration is complete. Reorganization of a mailbox in-between migration stages could result in duplicate data or folders.
- Assign licenses to users – Make sure every user has been assigned a license in the target platform.
- Pay attention to storage – Ensure all target mailboxes have enough storage for the source data.
- Disable MFA – It’s recommended MFA is disabled on admin accounts. If migrating with end-user passwords, we recommend MFA is disabled on each user account.
- Validate results online – If migrating to a cloud-based platform (Microsoft 365, Google Workspace), it is recommended you log into the web browser rather than a locally installed client (i.e. Outlook) to validate results. The web browser will display immediate results, while local clients can take time to sync. If Transend’s support is required, we will require screenshots from the browser rather than a local Outlook client.
Pilot Testing
It is recommended you perform pilot testing in advance of a production migration. View Pilot Testing Guidelines for general recommendations.
Performance Guidelines
The following Performance Guidelines define system requirements and recommendations to ensure a successful migration.
Optimize Resource Usage
It is recommended to close all other applications on the Console and Remote Agent machines to avoid competition for system resources.
Disable Scanning Software
Antivirus programs, including Windows Defender Real-time Protection, will slow down the migration and may cause a crash. If possible, disable it completely. Otherwise, you must set some scanning exclusions for Transend application processes and working data folders. Keep in mind that some antivirus programs may turn back on automatically based on organizational policy settings.
View more information about disabling Anti-virus software.
Disable Windows Update
It is recommended to disable Windows Update from installing any updates during the migration. If updates are installed and Windows forces a reboot as a result, it will cause active migration jobs to crash.
Disable Multi-Factor Authentication
Multi-factor authentication (MFA) is a policy that requires the account owner to verify login attempts with a second device of their choosing. We recommend you disable MFA prior to migration.
Disable Server backups
It is recommended you disable/pause any on-prem server backups scheduled to perform during migration processing.
Provision User Accounts
Prior to migration, both the source and target accounts must be provisioned and licensed.
End-User Communication
Prior to migration, we recommend communicating to end-users migration expectations, including the timing of the migration and associated best practices.
Update DNS Records
Most migration projects require updating DNS records to perform important mailbox migration related tasks.
Time Zone Considerations
Prior to migration, it is recommended you set each migration machine Windows OS to the same time zone as the on-premises mail servers.
Important: Do not use UTC- Coordinated Universal time zone as this may result in incorrect dates/times when migrating from or to on-premises email servers.
Power & Sleep Settings
It is recommended to set your computer Power and Sleep Settings so the computer does not power off or go to sleep while performing migration processing.