Transcription
Top Tips for Office 365 Tenant toTenant Migrations with Coexistence
BitTitan ExpertKelsey EppsSr. Technical Sales Specialist
Today’s Agenda About BitTitan Office 365 Tenant to Tenant with Coexistence Overview Demo User Migration Bundle DeploymentPro Considerations Next Steps
About BitTitan Founded in 2007 160 employees worldwide 187 countries served 36,000 customers 13m mailboxes migrated
About BitTitanMIGRATE MULTIPLE WORKLOADS WITH MIGRATIONWIZMigrationWiz is the industry-leading, 100% SaaS migration solution that helps you get email and datafrom nearly any Source to any Destination. Easy to use Well supported Secure Automatically scales Server-less Install (SaaS) Proven technology
BitTitan’s Tenant to Tenant Coexistence CapabilitiesHOW CAN WE HELP? BitTitan now offers setup Mail-Flow and Free/Busy coexistence for Office 365 Tenant to Tenantmigrations exclusively through the User Migration Bundle. Limited to Tenant to Tenant scenarios that involve changing the domain name – not available forkeeping the same domain name. No Advanced Options impacted. No workloads are impacted.
Changes in MigrationWiz Project FlowPROJECT SETUP (PRE-MIGRATION PHASE) Basic project creation remains the same. When Office 365 endpoints are selected for Source and Destination, you will have a new option to enableTenant to Tenant coexistence.
Changes in MigrationWiz Project FlowPROJECT SETUP (PRE-MIGRATION PHASE) Enter the primary source and destination vanity domain names. The Source domain is optional and can be left blank. In this case, we retrieve the list of sourcedomains available and enable coexistence for all domains. Global Admin Credentials Required.
Changes in MigrationWiz Project FlowPROJECT SETUP (PRE-MIGRATION PHASE) Select the Office 365 license type. When the mail enabled contact is converted to a user account with a mailbox, this is thelicense that will be applied.
Changes in MigrationWiz Project FlowPROJECT SETUP (PRE-MIGRATION PHASE) Select the groups that you want to include as part of this migration. If changes are made to the groups, they can be synchronized anytime during the migrationproject.
Changes in MigrationWiz Project FlowPRE-MIGRATION PHASE – MAIL ENABLED CONTACTS Users are discovered in the Source tenant and mail enabled contacts are created with an externalemail address of the primary domain, in the destination tenant. This will allow for reverse free/busylook up from the Destination to the Source as well as enable mail routing from the Destination to theSource. Autodiscover and import rates: 1,000 users/hour Creation of mail-enabled contacts and setup forward: 2,000 users/hour
Changes in MigrationWiz Project FlowPRE-MIGRATION PHASE – ORGANIZATIONAL SHARING Organizational Sharing and Individual Sharing are setup and enabled on the Source and Destinationtenants; Free/Busy between the tenants.
Changes in MigrationWiz Project FlowPRE-MIGRATION PHASE – APPLY USER MIGRATION BUNDLE Once the automatic process is finished the users are imported into the MigrationWiz project. Select all the users and apply the User Migration Bundle license.
Data MigrationPRE-STAGE MIGRATION Select the users in the migration batch and run a PRE-STAGE migration. At this point the mail enabled contact is removed from the destination and cloud user account iscreated with the Office 365 license applied. Mail items are migrated with a date range. A mail forward is setup on the Destination mailbox, with the address of the Source mailbox.
Data MigrationFULL MIGRATION Select the users in the migration batch and run the FULL migration. The rest of the un-migrated items are migrated. On a successful migration, a mail forward is automatically setup on the Source mailbox to forwardemail from the Source to the Destination. The mail forward is removed from the Destination mailbox.
User Migration BundleTHE KEY TO SUCCESS IS MULTI-WORKLOAD Save money when migrating multiple workloads for a user with a bundled license. Boost revenue withmulti-workload projects and deliver a superior cloud onboarding experience to your customers with ourUser Migration Bundle. Mailboxes Documents Personal Archives Outlook Configuration
DeploymentProOUTLOOK CONFIGURATION Configure Outlook remotely so you don't have to visit any desktops - managed from MSPComplete. Setup a new Outlook profile Import the auto-completes Import the signatures Re-attach PST files
Considerations User Migration Bundle is required for this migration. Valid Office 365 licenses are required in the Destination tenant. You cannot mix Office 365 license types in the project on the Destination. You cannot change from Office 365 license types after the project is setup.All the users must be in one project and multiple projects cannot be used. Migration can be completed in batches, but all the users need to be in the same project.Cloud accounts are created on the Destination. Azure Active Directory Connect cannot be used on the Destination to create accounts. Once the user accounts are created (with the BitTitan process), AAD Connect can be used to soft match and synchronize onpremise user accounts and passwords.
Additional InformationHELP.BITTITAN.COMOffice 365 Tenant to Tenant Coexistence Setup Guide End to end for the enablement of coexistence during basic project setup.What happens during a Tenant to Tenant Migration with Coexistence Project Setup? Outlines the automated activities MigrationWiz performs to establish coexistence.How do I sync changes in Distribution Lists or Groups for a Tenant to Tenant Migration? Outlines changes to distribution lists or groups.
Next Steps Get started for free with a BitTitan account https://www.bittitan.com/account/register Purchase User Migration Bundle Licenses Get started on your next migration project Have questions on how to get started? Contact us!
Thank you!
BitTitan now offers setup Mail-Flow and Free/Busy coexistence for Office 365 Tenant to Tenant migrations exclusively through the User Migration Bundle. Limited to Tenant to Tenant scenarios that involve changing the domain name - not available for keeping the same domain name. No Advanced Options impacted. No workloads are impacted.
