Migrating from Yahoo! – CloudM

The following instructions are designed to assist you in migrating mail from Yahoo!.

Please make sure that the following prerequisites are complete before continuing onto the CloudM Migrate setup.

Prerequisites

Destination Platform Prerequisites - Office 365

The following prerequisites are for migrations that use Modern Authentication as the Authentication Method. Modern Authentication is the recommended method as Basic Authentication is being deprecated.

Ensure that you have an Admin User in your Azure AD account. The Global Admin Role is recommended, but not mandatory. Please note that Multi Factor Authentication must be disabled for the specified admin accounts when migrating Microsoft Teams.
Ensure that a Test User has a license with a mailbox.

Destination Platform Prerequisites - Google Workspace

These steps should be completed in your Destination environment.

You will be required to set up a Service Account. Please refer to the Setting up the Service Account and enable the APIs within Google Workspace for CloudM Migrate article.

CloudM Migrate Hosted makes migration as simple as possible. The only other prerequisite is the installation of the CloudM Migrate Hosted application. When accessing CloudM Migrate Hosted for the first time, you will be prompted to install the app, simply authorise and you are all set.

Select your configuration

Source Platform - Yahoo!

Choose Yahoo! as the migration source and enter your Yahoo! settings into CloudM Migrate and then click next.

CloudM Migrate will now perform a small connection test to verify that the details you have entered are correct. If this fails you may have entered something incorrectly. If you are failing to resolve the issue please contact CloudM Support via the chat icon.

Destination Platform - Google Workspace

Select Google Workspace as your destination platform.

Select where you would like your data to be migrated. If you have purchased Goggle Workspace for Business or Google Vault you may want to migrate data directly into Google Vault.

To enable Google Vault for your domain, please see the following article: http://support.google.com/vault/bin/answer.py?hl=en&answer=2584132

Enter information for your Google Workspace admin account.

Domain Name - The domain name you will be migrating from. This should be the Internet domain name, not the local domain name.
Admin Username - An administrator account for the domain specified, this will usually be an email address for a Super Admin.
Service Account Email Address - Before attempting to configure CloudM Migrate, you should have created a Google Cloud platform project and created a service account for it. Input the service account's email address in this field.
Private Key - The file path to the P12 key that was generated and downloaded when creating the OAuth service account.

If you cannot find the private key, go back to Google Cloud Platform service accounts, select your project (if not already selected), use the option button on the right of the service account and click Create Key. Select P12 and download the key file.

Once you have configured the settings, select Next. CloudM Migrate will perform a connection test against your domain to verify that everything has been entered correctly.

If your Google Workspace system is brand new or for any reason the users being migrated have not been created in Google Workspace, CloudM Migrate can create your users for you. Simply go to advanced settings, to the user settings section and enable Create Users.

Destination Platform - Office 365

Select Office 365 as your destination platform.

Enter information for your O365 admin account.

Admin Username - The email address of an administrator within your Office 365 environment.
Admin Password - The password for the administrator account specified earlier.
Domain Name - The domain name of your Office 365 environment, this might be the part after the @ in your administrator email address. If migrating from several different domains, several migrations will be needed.
Test Username - A non-admin user who is already present in the system.

CloudM Migrate will perform a connection test against your O365 domain to verify that everything has been entered correctly.

If you are on a Small Business or Kiosk plan and need to use delegated access to migrate from Office 365 then you need to make an advanced settings change. Click Advanced Settings and under the Account Details section select Credential Method and change it to Delegated Access.

Office 365 Configuration and Provisioning

CloudM Migrate includes a number of platform configuration and provisioning options for Office 365 migration that enable advanced automation scenarios. These options can be executed during the migration process and will run as part of the migration of users' data. See here for detailed information.

There are special considerations when you need to preserve the user's domain in the target tenancy. This is because you cannot have the same domain in two Office 365 tenancies at the same time. The recommended approach to achieve this is detailed below:

All users to be migrated in the source tenancy will have a primary SMTP email address ending in their current domain e.g. 'user@company.com'. Check that each of these also has at least one alias. This will be needed later to avoid having to delete users in order to stop mail going to their original mailboxes
Provision users mailboxes in the target tenancy with their primary SMTP email addresses based on the '.onmicrosoft.com' domain.
Configure CloudM Migrate with the target domain based on the new tenancy's '.onmicrosoft.com' domain. This will be used for both the bulk migration pass and the delta pass.
On completion of the delta pass, all the users should have their current primary SMTP address switched to their alias. This will in-effect stop mail from being received and be the start of the mail 'down-time'.
Remove the 'company.com' domain from all users in the source tenancy. It is essential that no objects remain assigned to this domain otherwise you will not be able to remove the domain from the tenancy.
Remove the 'company.com' domain from the source tenancy.
Add the 'company.com' domain to the target tenancy
Assign the 'company.com' domain to all the users in the target tenancy and make this the primary SMTP email address
This ends the 'mail down-time' as mail will now successfully flow to the users again in the new tenancy.

Select which users to migrate

It's now time to add which users you'd like to migrate.

Unfortunately when migrating mail from Yahoo! you will not be able to use the Get Users button from the actions menu. You can manually import users via a CSV file using the Import Users option or simply add them individually via the plus icon.

Selecting a star next to any specific user or users will prioritize their migration. When a migration starts, threads will be assigned to any starred user so that their migration can start immediately.

At this point you can choose what to migrate for each user, when migrating from Yahoo!.

Enter your user's full email address within the Export Name field. If you have already created your G Suite users then you will just need to enter their username.

You must enter your users' passwords in the Password field.

Select how much mail to migrate

CloudM Migrate lets you decide how much mail you'd like to migrate to your shiny new system.

If you are changing your email address as part of the migration you can verify that the domain names are correct here. You can also specify specific address replacements in the respective section of the advanced settings.

For more information on domain and address replacements, see this page.

Start your migration

We know that you may want to start your migration in the middle of the night, or over the weekend, but we don't expect you to stay up in order to do so. With CloudM Migrate, you can decide to schedule exactly when you'd like the migration to occur.

Start the migration.

Review your migration results

During the migration process, CloudM Migrate will report back in real time exactly who is being migrated and the items being processed. All you now need to do is sit back, relax and wait for your migration to complete.

Check the progress of your migration.

Once complete you can download a full report for your migration.

For more information about this page, please visit the summary page.