The migration tool can handle the majority of mail server connections automatically, thus improving speed and convenience. It is ideal for customers whose legacy environments are supported. In addition, the tool can work well with environments with simple troubleshooting requirements, which do not require detailed logs.
The service is not designed to migrate data that entails complex programming. The tool runs in the cloud and it is perfect for moving data from a single server. If the free data migration service is unsuitable for your specific requirements or legacy environment, you can opt for one or a combination of alternative tools.
The service provides a practical solution for your organization when migrating old email from various platforms. These include Office 365 and Microsoft® Exchange servers like Exchange 2007, 2010 and 2013. Supported servers are compatible with Exchange Web Services (EWS). You can also rely on the tool to move data from IMAP servers, including Exchange 2003, Yahoo and Gmail.
When resorting to alternative G Suite migration tools, the ideal options are determined by a variety of factors. These include data sources and data types. In many cases, your organization needs to use multiple tools to ensure a smooth migration.
For a smooth migration, you should adhere to G Suite migration conditions. It is important to upgrade to the suite if you are using the legacy free edition of Google Apps. The migration tool only supports existing G Suite user accounts. This means that your entire team's accounts must switch to G Suite before moving. The requirements also extend to licenses; all users must have valid licenses.
The tool is not designed to set up new G Suite accounts as part of the migration process. When migrating email, ensure that Gmail is enabled for all your users. The same applies to contacts and calendar migration.
It is important to note that resellers are unable to handle migrations on your behalf via the reseller console. You can only handle the process via your Admin console. On the other hand, your legacy environment should have a Transport Layer Security (TLS) certificate because the migration tool communicates over this cryptographic protocol, which is often referred to as SSL.
You must ensure that the certificate for the protocol is signed and trusted by a reputable authority. Self-signed certificates are not accepted. When setting up your certificate, you can verify the installation using a verifier. This allows you to determine whether your TLS certificate is trusted before proceeding with the migration. It is recommended that you indicate port 993 when verifying a certificate for an IMAP server.
When migrating from an IMAP server like Exchange 2013 and webmail providers, you are required to select a legacy environment role account. Simply enter a valid username and password, which is applicable to your mail server account. The details can be entered when prompted by the Admin console. Once the role account is selected, you proceed to set the SSL certificate.
Even migrating a single large mailbox can be troublesome for the G Suite Admin Console's migration tool. Issues usually arise in estimation but overall performance is slow throughout a migration. While useful and convenient for small one - off migrations - we would not recommend the G Suite migration service for a company or department migration from another platform or Google account.