Cutover into existing “Live” Tenant

When migrating into an existing Microsoft 365 tenant that users already are “live” in (i.e. they send/receive mail from an account in the target with a different domain than their source account uses), considerations must be taken to ensure proper mail delivery takes place before the cutover is performed. If the customer is performing the… […]

Read More…

File Migration Methodologies

If your project scope includes a file migration, the following considerations are important to understand. Single-pass migrationBy default, Transend performs file migrations in a single-pass directly after the Cutover is completed. If you require a staged migration that includes a pre-Cutover migration pass followed by a post-Cutover delta migration pass, please contact your project manager.… […]

Read More…

Onboarding credentials

Onboarding credentialsSource admin account credentials Target admin account credentials User List DNS registrar admin account credentials Follow the below steps to provide the requested Customer To-Do Items. If you need help, click here.Click the Files tab and download the following documents:a. Onboardingb. User List Update the Onboarding document with requested information and credentials. Populate the… […]

Read More…

Enable 2-Step Verification

To set up 2-Step Verification in Go Daddy, follow these steps: Log into Go Daddy with an admin account. Click the arrow next to Account Settings to expand the menu. Select Login & PIN. Scroll down to the 2-Step Verification section. Click Add Backup. Note: if no recovery number is currently set, this screen will… […]

Read More…

Assign Delegate Access to Transend

To grant Transend access to your Go Daddy account, you will need to assign Delegate Access to Transend. Log into Go Daddy with an admin account. In Account Settings, select Delegate Access In the People who can access my account section, click Invite to Access. In the Invite to Access window, enter the following: Name:… […]

Read More…

User Communication

Transitioning to a new email environment is a big change to end-users and can cause disruption if best practices are not properly communicated to them. A few days prior to cutover, communicate the timing of the cutover to users. And then the day of the cutover, send another reminder to ensure end-users are aware of… […]

Read More…

Set up target tenant

Transend requires that the target tenant has been set up, with user accounts provisioned, before it can begin your migration. Set up target platform & purchase licensesMicrosoft 365 Plans & Pricing Google Workspace Plans & Pricing Note: Users must be assigned licenses that include email. The following licenses do not include email, so do not… […]

Read More…

Provision Accounts

It is required that target accounts and objects are provisioned before the migration can begin. User accounts must also be licensed. Standard Project Type: User account provisioning to be performed by Transend (upon request) or by customer. Non-user objects (Advanced Provisioning) to be performed by customer. Advanced Project Type: Transend to perform supported provisioning, as… […]

Read More…

Prepare sub-domain for Microsoft 365-to-Microsoft 365 migration

Because only one Microsoft 365 tenant can validate access to a DNS namespace at a time, any M365-to-M365 migration that preserves users’ original email addresses will need to transfer domains between tenants. Further, you may need to either create a temporary DNS namespace to preserve access to the old tenant’s data after migration, or utilize… […]

Read More…

Prepare sub-domain for Google-to-Google migration

Because only one Google Workspace tenant can validate access to a DNS namespace at a time, any Google-to-Google migration that preserves users’ original email addresses will need to transfer domains between tenants. Further, you may need to create a temporary DNS namespace to preserve access to the old tenant’s data after migration. When adding an… […]

Read More…