Custom Migration Methodologies

If you require a custom migration methodology, Transend is able to deviate from the default methodologies for additional fees. Please contact your Project Manager to discuss your migration methodology preferences. […]

Read More…

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…

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…

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…

Microsoft 365 User Communication Template

When migrating your organization to Microsoft 365, it is critical users are properly prepared for the transition. Below is a user communication template that can be customized to align with your business processes and operations. You may also want to include notification about any other platforms or services that may be impacted during the transition… […]

Read More…

Microsoft 365 (Exchange Online) – Day-Of Migration Reminder

The below templated can be customized and sent to users the morning of Cutover (or ~1–2 hours prior). Subject: Today: Email Migration in Progress – Action RequiredHello,This is a reminder that your email mailbox transition to Microsoft 365 begins today. Migration WindowToday: [DATE] Time: [TIME RANGE, TIME ZONE] What You Need to Do NowPlease complete… […]

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…

Google Workspace (Gmail) User Communication Template

When migrating your organization to Google Workspace (Gmail), it is critical users are properly prepared for the transition. Below is a user communication template that can be customized to align with your business processes and operations. You may also want to include notification about any other platforms or services that may be impacted during the… […]

Read More…

Google Workspace (Gmail) – Day-Of Migration Reminder

The below templated can be customized and sent to users the morning of Cutover (or ~1–2 hours prior). Subject: Today: Email Migration in Progress – Action RequiredHello,This is a reminder that your email mailbox transition to Google Workspace (Gmail) begins today. Migration WindowToday: [DATE] Time: [TIME RANGE, TIME ZONE] What You Need to Do NowPlease… […]

Read More…