Frequently Asked Questions: Migration Manager

Question: Is there a Tenant to Tenant (T2T) migration solution? Answer: Yes. Cross-tenant OneDrive migration is now available outside of Migration Manager. A cross tenant migration solution for SharePoint is currently being developed and scheduled for release in Spring 2023.
Learn more about the Cross-tenant OneDrive migration

Question: Can I migrate content from SharePoint Server?
Answer: At this time, Migration Manager supports the migration of file shares and cloud sources including Google, Dropbox, and Box It doesn't support the migration of content from SharePoint Server. See SPMT (SharePoint Migration Tool) for SharePoint Server migration.

Question: Can I run the SharePoint Migration Tool (SPMT) on the same computer that I have the Migration Manager agent installed?
Answer: Yes.

Question: Does the file share I'm migrating need to be on a Windows computer?
Answer: No. As long as you can access the file share from the migration agent, you can migrate it.

Question: Is multi-factor authentication supported by Migration Manager?
Answer: Microsoft multi-factor authentication is supported; however third party multi-factor authentication isn't.

Question: Can I manually assign a task to a migration agent I have set up?
Answer: No. Migration Manager does it for you by automatically distributing tasks to the next available agent. However coming soon, if you want to target migration tasks to a group of agents, you'll be able to do so.

Question: Where are local Migration Manager logs stored?
Answer: The logs are stored here: C:\Users\<Username>\AppData\Roaming\Microsoft\SPMigration.

Question: Can I rename my temporary working folder?
Answer: Yes. By default the name of the folder is %appdata%\Microsoft\SPMigration. Through the Migration Manager UI, you can configure the physical location of the folder where logs and reports are stored on the agent's machine including renaming your working folder.

Question: What should I do if I don't have enough storage space? Answer: When you are in Manager Manager, you can see the available disc space. Choose a drive that has enough storage before starting your migration.

Question: When using the Migration Manager tool, is there a limit to the number of path characters you can enter?
*Answer: Yes. When entering the source path into the text box, you're allowed a maximum of 255 characters. However, during migration the file path can be up to 32,767 characters in length. After it's migrated into SPO, the path is limited to 400 characters.

Question: Can Migration Manager migrate content to non-English SharePoint sites?
Answer: Yes, Migration Manager can migrate content to non-English sites as long as the site title doesn’t include non-EN characters.

Question: How many tasks can an agent perform simultaneously?
Answer: An agent can perform 5 to 10 tasks simultaneously, depending on the size of each of the tasks. However, the agent won't take any new tasks until all the existing tasks have completed.

Question: What happens when you "pause" a task?
Answer: Pausing a task doesn't release the agent to another task. The agent remains unavailable to accept a new task until the task is resumed and completed, or if the task is deleted.

Question: How long does an agent stay connected to Migration Manager?
Answer: The connection between an agent and Migration Manager stays active as long as the computer is still running and the SharePoint admin credentials that were used to sign into the agent are still valid. If the agent does becomes disconnected, the agent holds the token to the Migration Manager for up to seven days. After which the agent will need to be reinstalled.

Question: Is Migration Manager available for Government clouds?
Answer: Yes. Here's how you configure it: Government cloud settings

Question: What’s the retention policy for the blog storage?
Answer: When using the Migration API, customers and ISVs use the SPO-provided blob containers/queues. SAS URIs are provided to access those containers/queues. The SAS URIs are valid for three days from creation for containers and 21 days for queues. After the SAS expires, the content in the blob containers/queues won't be accessible. SPO backend jobs will delete the content in the container/queues within 30 to 90 days of the creation.

Question: Is the data in the SPO provided containers encrypted?
Answer: Yes. We mandate that the data uploaded to SPO provided containers must be encrypted using AES CBC to ensure the data is secure. To learn more, see: OneDrive for Business and SharePoint Online Migration API encryption.

Question: Will my migration succeed if the temporary storage expires before content migration is complete?
Answer: Yes. If your migration task was successful, your data will be migrated to SPO even if the temporary storage has expired.

Question: Does running a migration slowdown the tenant or impact SharePoint site performance while migrating?
Answer: In general, site performance shouldn't be impacted by running a migration. There are many factors that prevent this from happening:

  • Migration runs as a background activity and doesn't compete with end-user traffic
  • SharePoint and OneDrive infrastructure has built-in throttling rules that project the reliability and availability of the system. To learn more about migration throughput and factors that affect migration speed, learn more at: General migration performance guidance

Question: How do I remove the Migration Manager agent from a computer?
Answer: Rerun the Migration Manager agent installer and select the Uninstall button.

Question: How do I update the Migration Manager agent?
Answer: The agent is set to automatically update to the latest version by default.

Question: Does Migration Manager do incremental migrations?
Answer: Yes. The jobs created in Migration Manager do perform incremental migrations when run subsequently.

Question: Does adding more agents linearly increase the throughput? Is there a cap on the max number of agents?
Based on our current data, the average speed of migration scales linearly to the number of agents, unless the overall throughput hits the upper limit of your network bandwidth. If multiple agents read from the same source file share path, that can also impact throughput. There’s no limit on how many agents you can install. We have many customers who perform migrations using 20+ agents. Note: A single agent can process up to 10 tasks at a given time.

Question: The date and time in Migration Manager isn't my local time. How can I change the setting to my local time zone? Answer: Migration Manager uses the time zone setting in the SharePoint Admin center to convert to your time zone. To update the timezone of the SharePoint Admin Center, browse to https://<your host url> to change the setting.

Question: Can Migration Manager convert GSuite products to Office 365 products? Answer: Yes. When Migration Manager migrates the data from Google Workspace, the documents are converted to Office 365 format.

Question: What does % complete mean? Answer: The % complete indicates the progress of the overall task migration, including the number of files migrated and the preparation work required for the remaining files to be migrated. Note: The % isn't linearly proportional to the number of files remaining to be migrated.

Question: What is the maximum file size that can be migrated? Answer: In cloud scenarios, the limit is 15 GB. For file share migrations, a file size of 250 GB is supported. See below.

Scenario Maximum file size migrated
Google to Microsoft 365 using MM 15 GB
Dropbox to Microsoft 365 using MM 15 GB
Egnyte to Microsoft 365 using MM 15 GB
Box to Microsoft 365 using MM 15 GB
File share to Microsoft 365 using MM 250 GB
File migration to Microsoft 365 using API 250 GB
SharePoint Server to Microsoft 365 using SPMT 250 GB
File share to Microsoft 365 using SPMT 250 GB

Question: How many task rows can I run at once when migrating content from a cloud provider? Answer: At a maximum, only 50 task rows can run simultaneously. This total includes both scanning and migrating. This limit does not apply to file share migration.