Because Microsoft OneDrive for Business is as critical as email for most organizations, having a OneDrive migration tool is essential. Just like mail users, OneDrive users do not want to lose the structures of their files and folders during migrations.
Quest On Demand Migration (ODM) is a OneDrive migration tool that makes it easier to migrate OneDrive sites to new tenants, allowing end users to preserve valuable data, including user and sharing permissions, ensuring continued access post migration. In addition, ODM allows you to filter OneDrive storage files based on folder, type, date or size to accelerate migration, as well as schedule migration tasks at times that are convenient for you and your organization.
A tenant-to-tenant migration cannot start without first knowing what is on the source tenant. For OneDrive migrations, that begins with a list of the user accounts that use OneDrive on the source. ODM is a OneDrive migration tool that collects statistics (count and size of files) for source OneDrive sites to help with migration planning.
OneDrive sites can also be provisioned in advance on the target tenant using PowerShell. Pre-provisioning OneDrive for hundreds to thousands of users may take up to 24 hours for the OneDrive locations to be created. Alternatively, OneDrive sites can be provisioned as part of the migration task.
Many migration solutions only migrate the last version of a file, leaving an end user unable to review previous versions of files or change histories. This lack of version migration can become a significant problem for organizations that are required to maintain versions saved in file storage structures for business or compliance reasons.
The ODM OneDrive migration tool can support migrating only the last versions of OneDrive documents when the business requirement is to migrate as fast as possible and only the last version is needed. However, ODM also supports migrating versions, whether it be a subset of versions, or all versions. While these migrations will take longer to run because of the increase in content, they will also meet stringent business and/or regulatory requirements many organizations require.
User mapping allows for the permissions on the target tenant to be mapped to what they were on the source tenant. This applies to the internal users, internal groups, and guest (external) users. This OneDrive migration tool allows shared permissions to be set to direct file permissions to avoid sending multiple share request messages to all users. Maintaining continuity of security and access to migrated files is a critical business data requirement.
OneDrive users want to see the important metadata copied to the new tenant. ODM supports the copying of the following metadata within OneDrive: Created Date, Created by, Last Modified Date, Last Modified By and document properties, ensuring the ability for end users to easily sort their documents
Some organizations may only need to migrate a subset of files to a new tenant. Perhaps they want to filter to only include the last 12 months of files. Or they want to exclude specific folders from the migration. ODM provides these capabilities to customize your OneDrive migration.
The ODM OneDrive migration tool allows you to automate migrations so they scale up during non-business hours and weekends when throttling rules are typically more relaxed. Conversely, you can scale the migration back down during business hours to reduce the load on the target tenant.
Use the Desktop Update Agent to add OneDrive accounts to your workstations
after the OneDrive migration completes.
Yes. But even with a solid OneDrive migration tool, there has to be enough available space on the target OneDrive. Initially, OneDrive for Business users have 1TB of storage. OneDrive administrators can increase this to 5TB of storage per user. You can contact Microsoft to provision OneDrive storage up to 25TB. Beyond 25 TB, storage is provisioned as 25 TB SharePoint team sites to individual users. That is a lot of storage space and should allow a user to transfer all OneDrive to another drive.
You can store up to 30 million files in a SharePoint library; but Microsoft recommends syncing no more than 300,000 files across all document libraries.
Although, you can move a large number of files over time, Microsoft recommends uploading batches of no more than 100 items at a time. You could be manually migrating files for a long, long time.
Thus, you should consider the performance impact on moving all your OneDrive files even though you may have space to do so.
The difference between copying and moving is that copying a file makes a duplicate of the file or directory in another location without affecting the original content. Moving a file transfers the original file or directory to another location and leaves nothing behind.
You can connect to more than one OneDrive on your computer: OneDrive for Business and OneDrive Personal. In File Explorer, you can move files between the folders in these OneDrive sites by selecting the files, drag and drop them in the new location.
The files you move from OneDrive Personal to OneDrive for Business are essentially recognized as new files. Thus, these files don’t retain metadata details such as Modified and Modified By.
Note: If you are moving files within the same disk drive, it will be faster than copying. This is because only the file path is modified for a moved file, the actual data stays in place on the disk. That is why a file move appears to run faster than a file copy.
Yes, OneDrive can store files locally. You will see the files in File Explorer. However, you can also save space by making files available online only. The files appear in File Explorer; but a cloud icon is displayed with each file. The files will not download locally until you open it.
Alternatively, you set files to Always keep on this device. These files appear with a green circle with a white check mark. These files are always available on your device – even when you are offline. But they are also available in OneDrive Online.
All OneDrive files are stored in the Microsoft cloud. OneDrive for Business is based on SharePoint. Each OneDrive for Business site is like a document library in a SharePoint site. Thus, your OneDrive files are stored in a document library; but the user interface represents a file explorer experience. OneDrive files can also be stored locally on your device on a disk drive.
Migrating Microsoft Power BI content can be complex, particularly when taking into account all of the data sources that can be used for reporting. On Demand Migration for Power BI simplifies the complex process of migrating Microsoft Power BI content during tenant-to-tenant migrations without the need to install or maintain on-premises software.
This Power BI migration tool focuses on shared workspace content, particularly end-user-created reports shared with businesses. It offers features such as discovery of workspaces, reports, semantic models, gateways, and connections, providing valuable insights for migration planning. It also generates pre-migration reports and supports the migration of shared workspaces, connections, and workspace permissions for supported data sources.
One of the main items to consider for a Power BI migration is the source data of the reports. This data is imported into Power BI, but it typically has a source that is external to Power BI itself. The source data can reside in on premises systems, in which case a gateway and connection is needed. It can also reside in online systems that do not require a gateway but would still have a connection to the source data. This Power BI migration tool collects information on gateways and connections, as well as determines the data source type, such as Microsoft SQL Server for example.
This Power BI migration tool allows you to generate a downloadable MS Excel-based report following the discovery processing. This report includes details of the workspaces, reports, semantic models, connections, gateways and permissions that were collected during the source tenant Power BI Service analysis.
The data presented can then be used for planning a tenant-to-tenant migration of shared workspaces that are covered by supported data sources.
The tenant-to-tenant migration of shared workspaces is the focus of On Demand Migration for Power BI, and it’s based on the source data from which the reports within the workspaces were created.
On Demand Migration for Power BI currently supports reports based on imported Microsoft Excel data, Microsoft SQL Server (on premises) and Microsoft Azure SQL (online).
The migration of shared workspaces would include reports and semantic models contained within the workspaces. It also allows for renaming of workspaces in the target tenant to handle naming conflicts.
The source data connections are a vital part of report functionality and are necessary to ensure that reports can continue to display the information they are designed for. This Power BI migration tool will migrate connections for supported data sources and will reconnect these connections to the original systems the reports are designed for, such as Microsoft Azure SQL. This does require an authentication component for the source system and the migration process allows for providing these credentials and then removing the credentials from the migration system.
The migration of reports and semantic models creates a static image of the data in the target tenant at the time of the migration. To ensure that the reports are maintained and refreshed post migration, the workspace migration will reconnect semantic models to migrated connections in the target tenant. This allows for the data connection to be processed by the migrated reports, along with any source data changes refreshed in the new tenant and semantic models.
While gateways can't be migrated directly, as these do require an installation and configuration component, the migration process does allow for mapping gateways between the source and target tenants. The gateways would need to be created in the target tenant prior to migration. Once this is completed a mapping (or matching if the names are kept the same) can be provided for use when reconnecting data source connections.
This Power BI migration tool give you access to shared workspaces and reports, which are essential for maintaining business continuity post migration of Microsoft Power BI Service objects. The migration process will set sharing permissions on shared workspaces based on the source workspace access permissions, along with defined roles. This will leverage the On Demand Migration for Accounts processing that will provide source and target account matching.
This Power BI migration tool covers shared workspaces currently and the supported data sources, imported Microsoft Excel data, Microsoft SQL Server and Microsoft Azure SQL Server.
Microsoft Power BI personal workspaces, applications and pipelines are not included.
Microsoft limitations for extracting data from the Power BI Service do apply.
For details on supported migration processing please review our On Demand Migration User Guide section: What We Migrate.
Migrate all your workloads with one comprehensive tenant-to-tenant Office 365 migration tool. On Demand Migration is a Microsoft 365 tenant-to-tenant migration tool that allows you to simply and securely consolidate and migrate all your Microsoft 365 tenants running such workloads as Exchange, OneDrive, SharePoint and Teams, as well as on-premises Active Directory and Entra ID. An intuitive dashboard gives you complete visibility into your migration project. Track progress in real-time, all while ensuring coexistence during the migration of your Exchange mailboxes and other Microsoft Office components.
Migrating Active Directory and Entra ID is one of the most challenging components of an enterprise M&A or modernization initiative. On Demand Migration (ODM), a leading Microsoft 365 migration tool, helps you integrate and migrate users, groups, and devices between Active Directory, Entra ID and hybrid directory environments, without requiring trusts, SQL, network connectivity, or installing servers. This cloud-based SaaS 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 AD or Entra ID migrations. Plus, you can modernize and migrate your devices to the cloud. With ODM you can:
Capabilities covered under this use case include:
Establishing coexistence is the first step toward integration, and is a crucial component you must plan for from the outset of your Office 365 migration. After all, if users can’t communicate between tenants or access their Exchange mailbox, business operations become chaotic. On Demand Migration (ODM) offers short and long-term coexistence services for local and cloud-based environments. These capabilities are particularly critical during the hybrid migration projects due to the business-critical nature of the sub-systems they are servicing, such as email messaging and calendaring. You can use this SaaS solution to:
Capabilities covered under this use case include:
Preserving valuable user content during a Microsoft 365 tenant-to-tenant migration is essential to ensuring that end users can communicate and remain productive after a migration. On Demand Migration (ODM) helps you migrate user-created content in Exchange and OneDrive, acting as a comprehensive Office 365 migration tool. With this SaaS solution, you’ll ensure that users never lose access to their data, including content stored in public folders and PST files. In addition, you’ll preserve document versions and metadata associated with each document, while still retaining the ability to exclude unwanted data to increase migration speed and reduce data loss. With ODM you can:
Capabilities covered under this use case include:
Maintaining shared content is pivotal to ensure end user productivity after a Microsoft 365 tenant-to-tenant migration. On Demand Migration (ODM) helps you keep users collaborating by migrating documents, conversations and other valuable data stored in SharePoint document libraries, Teams channels and Microsoft 365 Groups. Using this cloud-based SaaS solution, you can make sure end users will continue to participate and interact in discussions, even after they have been migrated, including all historical data and email messages. In addition, you’ll fully preserve the metadata, site and document permissions, to make the transition seamless to end users. With ODM you can:
Capabilities covered under this use case include:
One Solution. Many Workloads. Migrate all your Microsoft 365 workloads including Exchange Online, OneDrive, SharePoint Online, Teams, M365 Groups and Chats, Power BI, Email Domains, Active Directory, and Entra ID using our comprehensive Office 365 migration tool.
Worldwide Available. ODM is a 100% Azure based SaaS platform with redundant and highly available infrastructure located in independent regional data centers in Australia, Canada, North Europe, United Kingdom, and United States.
Complete Control. Intuitive project management interface provides visibility allowing you to stage, schedule and resolve problems in your migration project, including email migration and Exchange server transitions.
Coexistence for Collaboration. Maintain user communication and collaboration throughout the migration so your users can keep working with minimal impact on their Microsoft Outlook or Outlook Web access.
Secure Migrations. Get the security standards, service level and scalability you need. ISO certifications include ISO/IEC27001:2013, ISO/IEC 27017:2015 and ISO/IEC 27018:2019. Also SOC2 Type 2 attestation. Our Microsoft 365 migration tool ensures encryption and protection against malware and spam during the migration process.
The Market Leader for Migration. Quest offers more than 30 years of migration expertise and a support organization that is unmatched in the industry. We have seen it all and are here to help you simplify your Office 365 migration, whether you're dealing with on-premises Exchange servers, PST files, or cloud-based email accounts.
On Demand Migration is available under a number of subscription scenarios, including T3, T5 and T7 options.
1. Services required | 2. Can be sold standalone
T3
T5
T7
Add-On
Azure Users and Groups
Exchange Online
OneDrive
SharePoint Online
Microsoft Teams & Groups
Power BI
Active Directory & Entra ID (Device) Migration (Note 1 & 2)
Directory Sync (Note 1 & 2)
Domain Rewrite (Note 2)
Domain Move (Note 1 & 2)
Microsoft Teams Chat Add-On
Hybrid Exchange (Note 2)
Yes, while most organizations have all their Microsoft resources contained in a single Office 365 tenant, some companies have multiple tenants. This is most common when a company has gone through a merger or acquisition but has not consolidated their tenant resources. In these scenarios, each Office 365 tenant is separate, having unique tenant IDs, separate directories, and unique email domains they are authorized to use.
For companies that plan to manage multiple tenants long-term without consolidating, Microsoft recommends configuring a multitenant organization to simplify cross-tenant collaboration in Teams and SharePoint. Third-party Directory Sync and Domain Rewrite solutions will also help enable consistent branding and user experience for the remaining Office 365 workloads. Performing a tenant to tenant migration will allow you to centralize all resources into a single instance to simplify management and reduce costs.
A successful tenant-to-tenant migration requires thorough planning and testing and should start with a complete assessment of the tenants to inventory Microsoft 365 objects and settings. This discovery will help identify the resources and content in scope for migration so you can create a realistic project plan and timeline.
You will need to manually configure some settings, policies, and licenses in the target tenant, but you can utilize native and third-party migration solutions to easily migrate identities, domains, and content from one Microsoft 365 tenant to another. Decide whether you will perform a big-bang cutover or a phased migration, and then perform test and pilot migrations before proceeding with velocity migrations.
Use Entra migration tools to migrate Microsoft 365 objects such as users, groups, devices, and domains from one tenant to another. For larger migrations, these tools can also provide long-term coexistence through directory synchronization and domain rewrite.
Migrate individual Microsoft 365 workloads using Microsoft solutions or perform a complete tenant to tenant migration using a third-party migration tool like On Demand Migration. Migrate content, settings, and permissions for mailboxes, OneDrives, Teams, private chats, Power BI, and SharePoint and finish the migration by switching user identities and updating Office applications.
Tenant-to-tenant migrations allow organizations to consolidate multiple Office 365 tenants but can be challenging if performed without proper planning and testing. Some common technical concerns include the potential for data loss, broken links in migrated content, and missing permissions in the target. To mitigate these risks, compare the supported migration features for each Office 365 workload using different migration methods, research what types of data are not supported for tenant to tenant migration, and perform thorough testing to confirm migration functionality and data fidelity.
A common business challenge is reducing the impact on user productivity, especially when users are not migrated together. Larger organizations often require a phased migration approach due to the number of users and data to be migrated. These companies may be able to reduce the overall duration of their Office 365 migration by reducing the migration scope, pre-staging resources in the target, and only migrating recent mailbox content and the latest versions of files. In longer phased migrations, organizations may implement a coexistence solution to simplify collaboration between migrated and non-migrated users. Most migration solutions will also provide guidance and best practices on orchestrating your tenant to tenant migration for maximum throughput.