Share your brand between tenants. Merger and acquisition (M&A) deals often task IT teams with meeting a difficult requirement: Deliver a unified email presence from Day One. On Demand Migration (ODM) Domain Rewrite makes it easy for you to enable users to communicate from a common email domain, delivering a single brand to the world while facilitating internal collaboration. With this powerful SaaS solution, you can:
Easily enable business users in all your Microsoft 365 tenants to use a common email domain for both inbound and outbound mail work. From Day One, present a unified brand to the world while empowering effective internal communication and collaboration.
Messages are securely routed to and from the ODM Domain Rewrite Service with TLS encryption, using certificates that you control. The project wizard walks you through adding custom DKIM and SPF entries to ensure that your organization’s messages are not flagged as spam or spoofing.
Eliminate the work of manually loading files to match source and target users; simply use the wizard to define attribute mappings. Choose which domain name (new or old) should be used when sending email; emails sent to either domain will automatically be routed to the user’s active mailbox. You can even control which mailboxes have domain rewrite enabled, and in which directions.
Skip the time-consuming, complex task of configuring mail forwarders and transport rules to process rewritten messages. ODM Domain Rewrite automates the process of routing configuration — and even regularly checks to ensure that the configurations you established are still in place.
Easily take advantage of other On Demand Migration tools, such as ODM Directory Sync, ODM Domain Move and ODM for Active Directory. You can use the same project that you configured for ODM Domain Rewrite, including your user mappings, tenant connections and local agents.
Quest On Demand is included in the scope of the Platform Management ISO/IEC 27001, 27017 and 27018 certification. It has also successfully completed Type 2 System and Organizational Controls (SOC) 2 attestation, reinforcing our commitment to customer data security according to the industry’s highest standards.
Keep migrated and un-migrated users in sync. If users can’t find each other in the directory, it’s hard for them to work together. But with On Demand Migration (ODM) Directory Sync, you can ensure productivity across your on-premises, cloud or hybrid environment on Day One of your merger, acquisition or consolidation project.
ODM Directory Sync smoothly handles even the most complex scenarios. With this cloud-based service, you can:
Empower users across your IT ecosystem to communicate and collaborate smoothly from Day One of your migration. ODM Directory Sync creates a unified Global Address Book and keeps it up to date regardless of the migration status of each user and group.
Easily configure workflows to automatically provision target accounts in preparation for an AD consolidation. Choose whether to create accounts as enabled or disabled, how to populate Exchange attributes during mailbox provisioning, whether to sync passwords, and more.
Have an unusual or complex migration scenario? Relax — ODM Directory Sync is highly customizable: You can easily control which objects to synchronize and which attributes to include for each object, as well as whether to copy attributes as-is or perform transformations that create customized values during the sync.
Use one solution for all your Active Directory and Azure AD synchronization needs, whether you need to sync from a single source to a single target, implement a bi-directional sync or perform a complex sync between multiple environments. ODM Directory Sync supports both directories as both source and target. When syncing between two AD environments, you can enable a near-realtime password sync that operates independently of other sync activities.
Track changes and speed troubleshooting with a clear, complete record of your workflow run history and object synchronization, including individual attribute changes. You can even run a workflow in test mode to analyze expected changes without writing to your production directories.
Quest On Demand is included in the scope of the Platform Management ISO/IEC 27001, 27017 and 27018 certification. It has also successfully completed Type 2 System and Organizational Controls (SOC) 2 attestation, reinforcing our commitment to customer data security according to the industry’s highest standards.
Keep your email flowing while your tenant is in transit. One of the most complex challenges of a tenant-to-tenant migration is moving domains without impacting user productivity. But On Demand Migration (ODM) Domain Move enables you to easily and accurately migrate your SMTP domain from one tenant to another. You can:
Avoid the hassle of creating complex mapping files and scripts. ODM Domain Move automatically removes the domain from each source object and adds it to the matching target object. When it’s time to complete the domain validation, it will remove the domain from the source tenant and add it to the target tenant, using just-in-time permissions
The project setup wizard automatically identifies any tenants that have objects synced from local domains and walks you through configuring dedicated agents for them.
Ensure that all inbound messages are delivered to the intended recipients — even while proxy addresses are still in the process of being moved. The dedicated relay service uses the mapping defined in your project to determine the correct target mailbox for delivery
Some tasks in a domain move cannot be completed automatically — but that doesn’t mean a valuable IT pro has to waste their time babysitting the entire process. ODM Domain Move will email the project administrator whenever they need to take action to update MX records, complete domain validation or remediate issues.
Have a clear, complete record of every action performed during your domain move. Clearly understand any object conflicts or other issues that require remediation to complete the domain move.
Easily take advantage of other On Demand Migration tools, such as ODM Directory Sync, ODM Domain Rewrite and ODM for Active Directory. You can use the same project that you configured for ODM Domain Move, including your user mappings, tenant connections and local agents.
Quest On Demand is included in the scope of the Platform Management ISO/IEC 27001, 27017 and 27018 certification. It has also successfully completed Type 2 System and Organizational Controls (SOC) 2 attestation, reinforcing our commitment to customer data security according to the industry’s highest standards.
As cloud adoption increases, so does your need to migrate any remaining on-premises Exchange mailboxes to Exchange Online. On Demand Migration for Hybrid Exchange securely migrates data to the cloud from on-premises Microsoft Exchange without requiring you to install or maintain any software for the move.
Our Hybrid Exchange migration tool allows you to migrate multiple mailboxes simultaneously, including data such as email, calendar, contacts and tasks. In addition, it allows you to manage mail forwarding and also migrate mailbox settings, such as permissions, rules and autoreply. It even allows you to reconfigure Outlook to connect users to their new mailbox.
On Demand Migration for Hybrid Exchange provides intuitive project management for migrating mail content from one environment to another. Use the project setup wizard to connect your environments and create a migration project that provides a full range of migration features. Track and manage your migration in one comprehensive dashboard.
When On Demand Migration for Hybrid Exchange migrates content from source to target, it does not disable the source mailbox. This allows you to perform phased migrations over time if you have a lot of mailboxes in your organization. You can also perform incremental migrations to pre-stage data and then perform a final migration. On Demand Migration for Hybrid Exchange copies permissions and delegation even for mailboxes that are not migrated together, using the matching defined in the project. Risk reduction Reduce the risk of unauthorized access by assigning RBAC policies to On Demand Migration for Hybrid Exchange users based on job functions, ranging from read-only access to full project administrator access.
Configure each migration task to only include the content that meets your project’s needs, whether you want to migrate all content as-is or whether you need more granularity. Choose to only migrate certain folders, apply date filters, and choose whether to include recoverable items. Decide whether to include the Archive mailbox and choose to migrate content to the Primary mailbox or to the Online Archive in the target. You can even choose to migrate contents to a specific folder in the target mailbox.
Ensure that migrating users always receive email in their active mailbox by having On Demand Migration for Hybrid Exchange automatically enable mailbox forwarding throughout the Exchange migration. Choose whether to migrate Inbox rules, permissions, delegation and autoreply settings.
Deploy the ODM Desktop Update Agent (DUA) to help users update their Outlook profiles and other Office applications to connect to their target account after their Exchange Online migration is complete.
During the migration event, you can view detailed event logs in the dashboard to monitor migration status and review any warnings or errors, and you can choose to receive notification emails each time a task completes. All tasks performed in our Hybrid Exchange migration tool are also viewable in the Audit logs to help identify who performed migrations and when licenses were consumed.
An Exchange Hybrid migration allows you to migrate mailboxes from on-premises Exchange to Exchange Online or from Exchange Online back to on-premises Exchange. The two environments can be connected using the Exchange Hybrid Configuration Wizard or can be separate, disconnected environments.
When you have a lot of mailboxes to migrate, you can perform phased Exchange Hybrid migrations, maintaining coexistence and collaboration between migrated and non-migrated users. For smaller migrations, you may prefer to migrate all mailboxes at once in a single cutover event to maintain shared permissions and keep users working together seamlessly.
The two methods for completing an Exchange Hybrid migration are performing a native mailbox move or performing a mailbox copy with a migration solution. The mailbox move method migrates the entire mailbox at once and deletes the source mailbox. The mailbox copy method migrates content and settings from one active mailbox to another. Both methods can migrate mailboxes between environments connected using the Exchange Hybrid Configuration Wizard, and the mailbox copy method can also migrate mailboxes between disconnected on-premises Exchange and Exchange Online environments.
The mailbox copy method is popular with many Exchange Hybrid migration solutions because it provides better flexibility by having both mailboxes accessible throughout the migration. You can customize the migration scope, merge with existing mailboxes, migrate mailboxes with legal holds, compare source and target data, and perform phased migrations over time while retaining all mailbox permissions. Depending on the solution you use for your Exchange Hybrid migration, you can also update Teams meeting links, provide automation to help end-users update their desktop Outlook profile, and update mail forwarding to ensure end-users always receive messages in their active mailbox.
An Exchange Hybrid migration lets you move mailboxes between on-premises Exchange and Exchange Online to help accelerate modernization to the cloud or to migrate to another environment as part of a merger, acquisition, or divestiture. Migrating to Exchange Online allows users to take advantage of the full integration capabilities with other Microsoft 365 workloads, with options to easily collaborate during phased Exchange Hybrid migrations. Exchange Online is secure and highly scalable, and you can decommission your on-premises servers once all migrations are complete. Exchange Hybrid migrations also provide the flexibility of migrating mailboxes from Exchange Online back to on-premises Exchange if required as part of an organization change.
Completing an Exchange Online migration is no small task. To maintain your organization’s communication and collaboration during and after a Microsoft 365 tenant-to-tenant Exchange Online migration, it’s vital that end-users have continuous access to their email data. In addition, the ability to preserve migrate legacy data is essential to meeting compliance requirements.
Quest On Demand Migration (ODM) is a solution for Exchange Online migration that not only migrates mail to the primary mailbox or archive mailbox for each user, but also ensures uninterrupted access by migrating permissions and delegates. In addition, it also preserves public folders, shared mailbox and Exchange resource mailboxes to meet stringent compliance obligations.
Migrate accounts to the target with ODM to prepare for your Exchange Online migration, or match to existing target accounts with defined matching attributes or with a mapping file. During the Exchange Online migration, you can choose to have ODM apply a license that automatically provisions the target mailbox using the available license plans in the target tenant.
Use ODM collections to organize mailboxes into logical batches for your Exchange Online migration. ODM migrates user mailboxes, shared mailboxes, and resource mailboxes, so you could choose to group your baches by mailbox type, by planned migration date, or using any other categorization that fits your migration project.
Configure each Exchange Online migration task to include the exact content and settings that meets your project’s needs, whether you want to migrate all content as-is or if you need more granularity. Choose to only migrate certain folders, apply date filters, and choose whether to include recoverable items. Customize whether to migrate inbox rules, permissions, litigation holds, and other settings. Decide whether to include Online Archives and choose to migrate content to the Primary mailbox or Online Archive in the target, and even choose to migrate contents to a specific folder in the target mailbox.
Enable calendar sharing between your tenants with ODM to display accurate free/busy information cross-tenant before, during, and after migrations. Choose to have ODM automatically enable mailbox forwarding throughout the Exchange Online migration so that migrating users always receive email in their active mailbox. Migrate mailbox permissions and delegates to ensure that users maintain access to other mailboxes and stay productive.
Once the Exchange Online migration is complete, ODM can automatically update migrated meeting entries to ensure that Teams meeting links are hosted in the new tenant so meeting organizers have the correct permissions and meeting controls. Additionally, deploy the ODM Desktop Update Agent (DUA) to help desktop users update their Outlook profiles and other Office applications to connect to their target account after their Exchange Online migration is complete.
The ODM dashboard discovers mailbox statistics to help you plan your Exchange Online migration, including mailbox sizes, number of items, and whether mailboxes have Online Archives. During the migration event, you can view detailed event logs in the dashboard to monitor migration status and review any warnings or errors, and you can choose to receive notification emails each time a task completes. All tasks performed in ODM are also viewable in the Audit logs to help identify who performed migrations and when licenses were consumed.
In addition to migrating mailboxes, ODM also supports public folder migrations of all types, including appointments, contacts, journal, mail, and more. Discover the source contents and then choose whether to migrate just the root structure or include all subfolders, whether to include content, and whether to migrate Send As and Send on Behalf of permissions for mail-enabled public folders.
ODM utilizes Role Based Access Control (RBAC) for all workloads, including Exchange Online migration, which lets you control what activities each authorized migration administrator can perform. Choose whether your users can create projects, discover mailboxes, match accounts, migrate mailboxes, manage collections, and more. Restrict mailbox discovery even further by only allowing discovery of mailboxes in a pre-defined group or CSV.
Coordinate an Exchange Online migration with migrations for other workloads
including OneDrive, SharePoint, and Teams, including user’s individual
Teams chats. For advanced integration and consolidation, consider ODM
Domain Rewrite, ODM Domain Move, ODM Directory Sync, and ODM for Active
Directory, all of which support both cloud-only and hybrid environments.
The two methods for completing a cross-tenant Exchange Online migration are performing a mailbox copy or performing a native mailbox move. You should closely research the features and limitations of the two methods to ensure your Exchange Online migration is successful.
The mailbox copy method is popular with many Exchange Online migration solutions because it provides better flexibility by having both mailboxes accessible throughout the migration. You can customize the migration scope, merge with existing mailboxes, migrate mailboxes with legal holds, compare source and target data, and perform phased migrations over time while retaining all mailbox permissions. Depending on the solution you use for your Exchange Online migration, you can also update Teams meeting links, provide automation to help end-users update their desktop Office applications, and easily coordinate with other workload migrations like OneDrive, Teams, and SharePoint.
Microsoft does not have a native method for merging two mailboxes, so a common workaround is to configure one of the mailboxes as a Shared mailbox and grant full access to the owner of the other mailbox. However, this requires the user to switch between the two mailboxes to view all the data and this option is only available if the mailboxes are stored in the same tenant since you cannot assign mailbox permissions cross-tenant.
If you want to merge two Exchange Online mailboxes, you can accomplish this by copying data from one mailbox to another using an Exchange Online migration solution. Migration tools like On Demand Migration include options to copy the content as-is, copy the data to custom folders in the other mailbox, or even copy the data to the online archive of the other mailbox. Once you have all the content migrated into a single mailbox, you can delete the mailbox that is no longer required. When planning to merge mailboxes, it is important to review the settings and size limits of both mailboxes prior to the Exchange Online migration to ensure that the merged mailbox does not exceed its quota.
Many Microsoft 365 subscriptions include features that enable data retention and backup functionality for workloads including Exchange Online. If you just need to retain data for compliance purposes, you can configure retention policies and apply them tenant-wide or to specific mailboxes. You can also enable Litigation Hold on an Exchange Online mailbox or create a custom eDiscovery Hold for the mailbox. These holds will retain all mailbox data even after a user deletes it from their mailbox, and the eDiscovery hold also allows authorized administrators to perform searches against the saved data.
If you just need a one-time backup of a single Exchange Online mailbox to store outside of the tenant, you can consider options like exporting the content to a PST or copying the mailbox to another tenant using an Exchange Online migration solution.
On Demand Migration (ODM) for Active Directory (AD) is an AD migration solution that enables you to migrate and consolidate AD environments, accelerating your enterprise M&A and modernization initiatives. This SaaS solution can integrate and migrate users, groups, and devices between Active Directory, Azure Active Directory, and hybrid directory environments without requiring trusts, SQL, network connectivity, or installing servers.
ODM for Active Directory is built in the Microsoft Azure cloud and helps you turn an AD migration into a repeatable process without trusts or installing servers. You can safely run your AD migration during normal business hours while your users can keep working during the migration without interruption.
The solution provides a management dashboard for scheduling and automation, is highly adaptable to custom configurations, and keeps migrated and un-migrated users and groups in sync during the AD migration.
You can customize ODM for Active Directory to meet the requirements of even the most complex AD migration. For example, you can merge two or more Active Directory environments without a trust relationship. ODM for Active Directory supports one-to-one, one-to-many, many-to-one and many-to-many configurations. You can also migrate workstations to any type of environment, including traditional AD, hybrid Azure AD, and even Azure-only environments.
On Demand Migration (ODM) for Active Directory helps your transition to the cloud by migrating Windows 10 and Windows 11 devices to Entra without reimaging and rebuilding profiles.
ODM for Active Directory lets you complete your AD migration on your own schedule, whether that’s during normal business hours or after-hours. You can even pre-schedule a migration to automatically start at a specific time. End users can keep working during the migration, with only a brief interruption when prompted to allow the computer to restart, and their desktop and applications will look exactly the same when they log back in, so they can continue working with minimal impact.
ODM for Active Directory lets you migrate any objects, settings, properties, workstations and servers within and between forests. It automatically updates permissions on resources that are migrating and can even update resources that are left behind, to ensure users do not lose access to vital files.
ODM for Active Directory builds upon Microsoft’s Offline Domain Join (ODJ) functionality that lets you easily migrate remote users without asking them to come to the office. Users follow a simple wizard to pre-enter their credentials and then they are ready for their AD migration.
Perform standard migrations using the out-of-box features or enhance your migration by configuring custom actions that automate changes to device and application settings needed for your business. ODM for Active Directory can run additional scripts and commands that update files, folders, and registry settings to ensure the migrated devices function as expected in the new environment.
Security is a top concern when you’re dealing with sensitive data.
ODM
for Active Directory avoids the use of remote procedure calls (RPC) and
remote
registry access, and it minimizes the use of open firewall ports. Plus, it
is
certified to the ISO 27001, ISO 27018, Privacy Shield and Veracode
standards.
Choose from our family of device migration solutions to meet your different needs. For example, if you're:
The below table may help you in understanding how your needs could match the Quest device solutions:
ODM AD
ODM AD Express
ODM Entra ID Devices
Project Management
Wizard-driven project setup
System-managed workflows
Discover and Match with CSV
Agent servers required for AD environments
Device migrations with an Entra ID or Hybrid Source or Target Environment
Workstation migration from AD/Hybrid to Entra ID
Workstation migration from Entra ID to Entra ID
Workstation migration from Entra ID to AD/Hybrid
Workstation migration from AD/Hybrid to AD/Hybrid
Device migrations from AD to AD
Server and workstation migration from AD to AD
VPN device migration using offline domain join
Intra-forest device migration
Basic AD Migration
Target user provisioning with basic attributes
Target group provisioning with basic attributes and membership
Customized AD Migration
Target user provisioning with full attribute sync, as-is or transformed
Target group provisioning and membership sync with full attribute sync, as-is or transformed
Contact migration with full attribute sync, as-is or transformed
Customizable workflows for directory sync and device migration
Coexistence
Ongoing directory sync
Password sync
SID History migration
NAS File Share ReACL, AD Processing Wizard
Performing an AD migration or consolidation can help strengthen your AD security, centralize your domain management, and improve end user experience. If your company currently maintains separate domains for different departments or regions, you can combine the domains to provide standardized management and security policies, while still maintaining the ability to provide granular access to the consolidated resources.
Conversely, you might be managing multiple Active Directory domains because of a merger, acquisition, or divestiture. Configuring integration between the domains can help provide coexistence by syncing passwords and providing cross-domain resource access, but this can result in increased risk and management effort. If you are maintaining separate domains after a tenant-to-tenant migration, your end users might struggle with managing multiple identities. You should always make sure Active Directory domain consolidation is part of your tenant-to-tenant migration discussions.
Active Directory is Microsoft’s original on-premises enterprise solution for organizing and managing a company’s resources such as users, groups, and devices. Active Directory objects are configured within organizational units that belong to a domain, which can itself belong to another domain or forest. Active Directory is managed by domain controllers, which can physically reside in a company office or datacenter or can run as virtual machines. When users need to access resources and applications on Active Directory servers, they must have direct network access or connect to a virtual private network.
Azure Active Directory fully resides in the cloud and removes the need for domain controllers, organizational units, and direct network access to physical servers. Microsoft maintains the infrastructure for your Azure tenant, scaling up as needed to support your company’s tenant activity. Users, groups, devices, and other resources are created and managed in the tenant and users only need Internet connectivity to access Azure resources. Azure Active Directory can also serve as an extension to Active Directory by enabling synchronization between the two environments, allowing users to authenticate to Active Directory for local resources while also having access to the cloud-only resources in Azure Active Directory.
Microsoft 365 and Azure tenants are complex cloud platforms that include many different components and resources. Microsoft supports tenant-to-tenant migrations for many of its individual workloads; however, you cannot migrate an entire tenant as-is, and there are many configurations and resources that must be directly configured in another tenant.
When it comes to AD migration, Microsoft supports migrating Azure AD objects such as users, groups, contacts, guests, and Azure-joined devices from one tenant to another. Microsoft also supports tenant-to-tenant migrations for Microsoft 365 content such as mailboxes, OneDrive, Teams, and SharePoint. You can use migration tools to perform these migrations, enable cross-tenant coexistence, and replicate resource access. Although there is no direct migration path for Azure applications, virtual servers, and most tenant policies and configurations, the Microsoft community has built a tool for exporting and importing many tenant settings to assist with your tenant migration.
With SharePoint serving as a core component of many organizations’ collaboration and communication platforms, a robust SharePoint migration tool is essential. Most of the documents and other valuable content created in Microsoft Teams channels is stored in SharePoint libraries. SharePoint applications can also be customized to include forms and workflows, and it’s critical to migrate the content and applications to the target tenant.
Quest On Demand Migration (ODM) is a SharePoint migration tool that makes it easier to migrate SharePoint server data while ensuring continued access and security through the preservation of site and document permissions, as well as content metadata for continued compliance.
A tenant-to-tenant migration starts with the site discovery process. With a strong SharePoint migration tool at your disposal, the discovery process will find all the sites, libraries, and lists on the source tenant. After discovery, you can match the source sites to sites on the target tenant or provision the sites.
User mapping allows for the permissions on the target tenant to be mapped to
what they were on the source tenant. Maintaining continuity of security and
access to migrated content is a critical business requirement.
Many migration solutions only migrate the last version of content (e.g. files). Thus, users will not be able to review previous versions of files for a history of changes. This lack of migrating versions is a significant problem for organizations that are required to maintain file versions for business or regulatory compliance reasons.
ODM for SharePoint can support migrating only the last version when the business requirement is to migrate as fast as possible and only the last version is needed. However, this SharePoint migration tool also supports migrating a subset of versions and all versions. While these migrations will take longer to run because of the increase in content, they will meet the business and/or regulatory requirements for organizations.
Many organizations use a mix of classic and modern team sites. Some of the modern team sites are members of a Microsoft 365 Group and others are not. While an upgrade path is possible, it can require substantial manual changes to site pages. Thus, ODM for SharePoint can support migrating classic-to-classic sites (default) and classic-to-modern sites to provide you with total flexibility.
Of course, the ODM SharePoint migration tool migrates the content stored in document libraries and lists. Incremental migrations can be run closer to cutover dates to ensure that all of the content is successfully migrated.
SharePoint users want to see the important metadata copied to the new
tenant. ODM for SharePoint supports the copying of the following metadata:
Created Date, Created By, Last Modified Date, and Last Modified By.
Consider these steps when planning a SharePoint migration:
Get additional detail on selecting a SharePoint migration tool in our white paper, SharePoint Migration Planning Guide. It details the essential steps in planning a SharePoint migration, and offers best practices and proven solutions for reducing risk, driving platform adoption and maximizing ROI. Our blog post, A Beginner’s Guide to SharePoint Migration Planning can also help you get started.
Our On Demand Migration SharePoint migration tool has a lot to offer! Sign up for a free trial of On Demand Migration. Or for a further deep dive, check out our blog posts, 12 Features to Look for in a Microsoft Teams Migration Tool or 12 Features to Look for in a OneDrive Migration Tool.
No. Microsoft has several updates on its SharePoint product roadmap.
It is easy to see that Microsoft Teams usage has grown rapidly and seems to be the leading collaboration tool from Microsoft. However, SharePoint Online is the primary application provider and storage container for Microsoft Teams. When users create a team, a channel, or store files and documents, they are using SharePoint. Of course, OneDrive for Business also uses SharePoint for storing files and documents.
A tenant-to-tenant Teams migration is extraordinarily complicated. Why? Because this widely-adopted communication and collaboration platform isn’t a just single, standalone application. Teams actually serves as the front end to many other Microsoft 365 components, including SharePoint, Exchange and OneDrive. That’s why it’s essential that IT pros manage their tenant-to-tenant Teams migration securely, accurately and efficiently.
Quest On Demand Migration (ODM) is a solution for tenant-to-tenant Teams migration that will ensure continued collaboration, and retain valuable data stored in Teams channels, conversations and documents. ODM also supports the migration and archiving of 1:1 chats which is crucial for preserving valuable communication history and ensuring continuity of collaboration within organizations. You’ll be able to merge or rename Teams as they are being transferred to the target tenant. Best of all, end users will be able to continue where they have left off, even after they have been migrated, including historical data.
With the volume of Teams that likely exist in your Microsoft 365 environment, no one person or group is going to know every detail about them – or even most of them. That’s why auto discovery is so important during a tenant-to-tenant Teams migration. ODM’s Auto discovery capabilities make it easier to identify who the Team members are, which Teams have been created and how the Team is being used, thereby helping you limit sprawl and track usage.
Ensure all content migrates accurately by boosting visibility into Teams
across your Microsoft 365 environment, including permissions, to avoid
post-migration headaches. ODM helps you determine which Teams are living in
across your environment and how the teams are used. This allows you to
prevent Teams sprawl by preventing superfluous or unwanted Teams from being
integrated into the new tenant.
Preserving important data stored in Teams channels, documents and conversations is essential to ensuring continued collaboration post migration. End users must have access to historical discussion data to continue collaboration and foster growth.
Microsoft does not have a dedicated solution to move a Microsoft Team from one tenant to another. Moving a Team and all of the content is very complex, making a tenant-to-tenant Teams migration even more challenging. The content in a Team is stored in multiple locations. See our blog post, Microsoft Teams tenant-to-tenant migration checklist: Preparing to migrate Microsoft Teams, for a short list of Teams content and storage locations. Another blog post to review is Microsoft Teams meeting content: Where is it stored? This blog provides storage details for Teams meetings.
Typically, you need to coordinate the Teams migration planning with the content migration planning of other workloads – including SharePoint, OneDrive, and email. Thus, there is not an easy copy-and-paste solution to moving content. While you can attempt to migrate some content with PowerShell, you will soon find that it is easier to migrate all content with using a comprehensive solution for tenant-to-tenant Teams migration.
Yes, it is possible to merge content from two channels into one channel. Our On Demand Migration Teams solution for tenant-to-tenant Teams migration allows for merging of source Teams into target Teams. Merging Teams channels will move the messages and contents together.
Of course, special consideration should be given when merging content from different types of channels (standard, private, shared). Learn more details about shared channels in our blog post, Microsoft Teams shared channels/Teams Connect – Everything you need to know.
There is really just one type of Teams product for businesses; but Teams is adaptable for many business uses. The flexibility in adding components to a Team is what defines how it is used. For example, there are three types of channels:
A second example is that Teams can contain Planner Plans for managing small projects. See the blog post, How to Use the Top Features of Microsoft Planner when it comes to preparing to migrate Planner plans and tasks.
A third example is that users can also use OneNote in Teams for taking notes during meetings.
These are just three examples of how to adapt a Team for business use.