Skip to content

Commit

Permalink
Merge pull request #6955 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history 
Publish main to live, 11/07, 11:00 AM IST
  • Loading branch information
@aditisrivastava07
aditisrivastava07 authored Nov 7, 2024
2 parents c17326b + d45118b commit 2c0a645
Showing 1 changed file with 83 additions and 71 deletions.
154 changes: 83 additions & 71 deletions migration/mm-faqs.md
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
ms.date: 10/31/2019
ms.date: 11/05/2024
title: "Migration Manager FAQs"
ms.reviewer:
ms.author: heidip
Expand All @@ -21,107 +21,119 @@ search.appverid: MET150
description: Migration Manager FAQs
---

# Frequently Asked Questions: Migration Manager
# Frequently Asked Questions: Migration Manager File Share

**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.</br>[Learn more about the Cross-tenant OneDrive migration](/microsoft-365/enterprise/cross-tenant-onedrive-migration)
### File Share migration questions

**Question:** Can I migrate content from SharePoint Server? </br>
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:** Does the file share I'm migrating need to be on a Windows computer?

**Question:** Can I run the SharePoint Migration Tool (SPMT) on the same computer that I have the Migration Manager agent installed?</br>
Answer: Yes.
Answer: No. As long as you can access the file share from the migration agent, you can migrate it.

**Question:** Does the file share I'm migrating need to be on a Windows computer?</br>
Answer: No. As long as you can access the file share from the migration agent, you can migrate it.
**Question:** Can I manually assign a task to a migration agent I set up?

**Question:** Is multi-factor authentication supported by Migration Manager?</br>
Answer: Microsoft multi-factor authentication is supported; however third party multi-factor authentication isn't.
Answer: No. Migration Manager does it for you by automatically distributing tasks to the next available agent. However, you can target migration tasks to a group of agents.

**Question:** Can I manually assign a task to a migration agent I have set up?</br>
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:** How many tasks can an agent perform simultaneously?

**Question:** Where are local Migration Manager logs stored?</br>
Answer: The logs are stored here: `C:\Users\<Username>\AppData\Roaming\Microsoft\SPMigration`.
Answer: An agent can perform 5 to 10 tasks simultaneously, depending on the size of each of the tasks.

**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 needs to be reinstalled.

**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 adding more agents linearly increase the throughput? Is there a cap on the max number of agents?

Answer: 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. Multiple agents reading from the same source file share path 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:** 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?

**Question:** Can I rename my temporary working folder?</br>
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?
**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?</br>
*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:** What happen during incremental migration if I rename, move or delete a destination file or folder?

**Question:** Can Migration Manager migrate content to non-English SharePoint sites?</br>
Answer: Yes, Migration Manager can migrate content to non-English sites as long as the site title doesn’t include non-EN characters.
Answer: After a file or fold is migrated to destination, user **renames or moves** the file or folder, then remigrate,

**Question:** How many tasks can an agent perform simultaneously? </br>
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.
- The source file or folder is migrated to the destination

- The renamed/moved file or folder is kept

**Question:** What happens when you "pause" a task?</br>
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.
After a file or folder is migrated to destination, user **deletes** the file or folder, then remigrate,

**Question:** How long does an agent stay connected to Migration Manager?</br>
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.
- The source file or folder is migrated to the destination

**Question:** Is Migration Manager available for Government clouds?</br>
Answer: Yes. Here's how you configure it: [Government cloud settings](./mm-gov-cloud.md)
**Question:** In file share migrations, what is the content type of a migrated document?

**Question:** What’s the retention policy for the blog storage?</br>
Answer: When using the Migration API, customers and ISVs use the [SPO-provided blob containers/queues](/sharepoint/dev/apis/migration-api-azure-container-and-queue). [SAS URIs](/azure/storage/common/storage-sas-overview) 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?</br>
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](/sharepoint/dev/apis/migration-api-encryption).
Answer: In file share migrations, files are transferred to the SharePoint document library with the default "Document" content type. This process doesn't take into account any content type configurations that may be set on the library.

**Question:** Will my migration succeed if the temporary storage expires before content migration is complete?</br>
Answer: Yes. If your migration task was successful, your data will be migrated to SPO even if the temporary storage has expired.
### General questions on Migration Manager

**Question:** Does running a migration slowdown the tenant or impact SharePoint site performance while migrating? </br>
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](./sharepoint-online-and-onedrive-migration-speed.md)
**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 available.</br>[Learn more about the Cross-tenant OneDrive migration](/microsoft-365/enterprise/cross-tenant-onedrive-migration)

**Question:** How do I remove the Migration Manager agent from a computer? </br>
Answer: Rerun the Migration Manager agent installer and select the **Uninstall** button.
**Question:** Can I migrate content from SharePoint Server?</br>
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:** How do I update the Migration Manager agent? </br>
Answer: The agent is set to automatically update to the latest version by default.
**Question:** Can I run the SharePoint Migration Tool (SPMT) on the same computer that I have the Migration Manager agent installed?</br>
Answer: Yes.

**Question:** Does Migration Manager do incremental migrations? </br>
Answer: Yes. The jobs created in Migration Manager do perform incremental migrations when run subsequently.
**Question:** Is multi-factor authentication supported by Migration Manager?</br>
Answer: Microsoft multi-factor authentication is supported; however third party multi-factor authentication isn't.

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

**Question:** Is Migration Manager available for Government clouds?</br>
Answer: Yes. Here's how you configure it: [Government cloud settings](./mm-gov-cloud.md)

**Question:** Does adding more agents linearly increase the throughput? Is there a cap on the max number of agents?</br>
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:** What’s the retention policy for the blog storage?</br>
Answer: When using the Migration API, customers and ISVs use the [SPO-provided blob containers/queues](/sharepoint/dev/apis/migration-api-azure-container-and-queue). [SAS URIs](/azure/storage/common/storage-sas-overview) 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 (SharePoint Online) backend jobs 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?</br>
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](/sharepoint/dev/apis/migration-api-encryption).

**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>-admin.sharepoint.com/_layouts/15/regionalsetng.aspx` to change the setting.
**Question:** Can my migration succeed if the temporary storage expires before content migration is complete?</br>
Answer: Yes. If your migration task was successful, your data is migrated to SPO even if the temporary storage expired.

**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:** Does running a migration slowdown the tenant or impact SharePoint site performance while migrating? </br>
Answer: In general, site performance shouldn't be impacted by running a migration. There are many factors that prevent migration impacting site performance:
- 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](./sharepoint-online-and-onedrive-migration-speed.md)

**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:** Does Migration Manager do incremental migrations? </br>
Answer: Yes. The jobs created in Migration Manager do perform incremental migrations when run subsequently.

**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.
**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>-admin.sharepoint.com/_layouts/15/regionalsetng.aspx` to change the setting.

**Question:** In file share migrations, what is the content type of a migrated document?
Answer: In file share migrations, files are transferred to the SharePoint document library with the default "Document" content type. This process doesn't take into account any content type configurations that may be set on the library.
**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: For file share and cloud migrations, a file size of 250 GB is supported.

|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.

**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.
**Question:** In 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.

0 comments on commit 2c0a645

Please sign in to comment.