Migration Manager in the SharePoint admin centre

Kevin Egan 66 Reputation points

Hello, I wish to migrate two different file shares to one M365 tenant and looking to use the migration manager from the SharePoint admin centre.

I notice when you install the migration agent you connect it to the file share...so my question is... would I need to install 2 instances of the migration manager on two separate virtual machines and connect each of them to the separate file shares? or can it be done from one instance of migration manager on one virtual machine?

A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
10,073 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Ling Zhou_MSFT 14,605 Reputation points Microsoft Vendor

    Hi @Kevin Egan,

    Thank you for posting in this community.

    You can install two migration agents in one virtual to connect to each of your two file shares.

    When you run the setup file, you are prompted for two sets of credentials: Global or SharePoint Administrator credentials, depending on your destination, and Windows credentials with read access to the source. You just need to set the correct login credentials for your two file shares when creating different agents.

    It is not recommended that you use the same agent because each agent has a working folder. This folder is used to save logs, reports, and any temporary folders. If something goes wrong during the migration, we can easily find which file share has the problem.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Kevin Egan 66 Reputation points

    If both file shares on same network then both source file paths can be added on one agent, if on different networks then install 2 instances of the agent on separate VM'S

    0 comments No comments