Ninbucket

-->

Feb 08, 2020  I read a lot of these Migration-Assistant-hanging threads for a while looking for help, and I just wanted to note here on macrumors what ultimately worked for me. I was migrating from a Mac Mini to Mac Pro, both with Intel chips. I attempted it with an Ethernet connection between the two computers.

The SharePoint Migration Tool (SPMT) is a tool that migrates your files from SharePoint on-premises document libraries or regular file shares and easily copies them to SharePoint in Microsoft 365. It is available to all Microsoft 365 users.

Current and pre-release versions

Download and install SPMT using one of the links listed below.

Before you begin

Review the system requirements, settings, and permissions behavior before beginning your migration.

• SPMT prerequisites
  
• SPMT settings
  
• Understanding permissions when using the SharePoint Migration Tool
  

Important

• To migrate at the organization-level, you must be signed in as a global or SharePoint admin in Microsoft 365.
• To migrate at the site collection level, you must be a site admin.

Allow or prevent Custom Script (NoScript)

In Microsoft 365, tenants you can control whether users can run custom script on personal sites and self-service created sites.

During migration, some web parts require this setting set to allow. Otherwise, the web part will not be migrated.

At least 24 hours before you start migration, do the following:

1. Go to the Settings page of the new SharePoint admin center, and sign in with an account that has admin permissions for your organization.

   Note

   If you have Office 365 Germany, sign in to the Microsoft 365 admin center, then browse to the SharePoint admin center and open the Settings page.
   If you have Office 365 operated by 21Vianet (China), sign in to the Microsoft 365 admin center, then browse to the SharePoint admin center and open the Settings page.

2. At the bottom of the page, select classic settings page.

3. Under Custom Script, select:

   Allow users to run custom script on personal sites
   Allow users to run customer script on self-service created sites

   Leave these settings in place for the duration of your migration.

   Note

   Changes to this setting might take up to 24 hours to take effect.

   For more info, see, Allow or prevent custom script.

Note about logging in

When you first launch the SharePoint Migration Tool (SPMT), you are prompted for your Microsoft 365 username and password. The credentials you provide will be to the migration destination.

Mac User Migration Hangs At Looking For Incompatible Software Download

Authentication supported

SPMT supports the following authentication methods:

• NTLM
• Kerberos
• Forms
• ADFS
• Multi-factor authentication
• SAML-based claims
• Client certificate authentication

Important

If the on-premises server is configured to support multiple authentication providers, including Windows authentication, then Windows authentication will not be supported. If this describes your environment, use other authentication methods instead of Windows authentication.

I have a 2006 Macbook Pro running Mac OS X 10.6.8. I have talked to the apple Genius, they told me that the software that the 2006 editon MacBook Pro can run is the LION 10.7 Version ONLY. https://omgmood.netlify.app/2006-mac-pro-editing-software.html.

Where is your data currently located?

Before you start using the SharePoint Migration Tool (SPMT), note where your data is located, and where you want those files located after migration. You will be prompted for the current location of your data files and the location of the SharePoint site where you want them copied. SPMT lets you select from two sources from which to migrate your data: from an on-premises SharePoint Server 2010 or 2013 site, or from a local file share or network path.

• SharePoint on-premises: If you select the SharePoint on-premises option, you are prompted to enter the name of the SharePoint Server site where your files are located and prompted for your credentials for that site. You will indicate what document library you wish to migrate.

  Note

  SPMT supports SharePoint Server 2010* and 2013.

• File share: If you select the file share option, you are prompted to enter the location of the file share, the URL of the SharePoint site, and the document library where they will be copied. The files are not deleted from the source.

Using the SharePoint Migration tool

To install the current release download, go to: SharePoint Migration Tool

Migrating data files from SharePoint Server document libraries

1. Start SPMT, and then enter your Microsoft 365 username and password.

2. Select Start your first migration.

3. Select SharePoint Server.

4. Enter the SharePoint Server site URL where your content is located, and then select Next.

   Important

   Proxy connections are not supported. Using Proxy connections yields errors such as 'SharePoint login fail' or 'cannot load document library'.

5. Enter your username and password to the SharePoint Server site; username must use the format of someone@example.com. Select Sign in.

   Note

   If you have already signed in to that site once while using this tool, you won't be prompted again for the same site.

6. Select the document library where your files are located. The dropdown contains all your possible choices.

7. Enter the URL of the SharePoint site where you want your files migrated.

8. Select the document library to where your files will be copied.

9. Select Add. This task is added to the list. If you want to select another set of data files to migrate, select Add a source.

Migrating data files from a local file share

1. Start SPMT, and then enter your Microsoft 365 username and password.

2. Select Start your first migration.

3. Select File Share.

4. Enter the source path of the file share where your content is located, and then select Next.

5. Enter the URL of the SharePoint site where you want your files migrated, and then select Next.

   Note

   If you have already signed in to that site once while using this tool, you won't be prompted again for the same site.

6. Select the document library to where your files will be copied, and then select Next.

7. My belkin router. This task is added to the list. If you want to select another set of data files to migrate, select Add another source.

8. When you have finished selecting your sources, select Next.

9. Review your settings, and then select Migrate.
   

To use a JSON or CSV file for bulk migration

If you have many sources to migrate, you can use either a JSON or CSV file to do a bulk migration. To learn more on how to create a JSON or CSV file for data content migration, see How to format your JSON or CSV file for data content migration.

1. Start SPMT, and then enter your Microsoft 365 username and password.

2. Select Start your first migration.

3. Select JSON or CSV file for bulk migration.

4. Enter the full path of your .CSV or .JSON file where your content is located, and then select Add.

5. Enter the URL of the SharePoint site where you want your files migrated, and then select Next.

   Note

   If you have already signed in to that site once while using this tool, you won't be prompted again for the same site.

6. Select JSON or CSV file for bulk migration. Enter the location of your file, or select Choose File to locate it. Select Add.

   For this video, I chosemacOS High Sierra as the older Mac OS, but you could install Mojave, Sierra oralmost any older Mac OS. Which mac apps are 32 bit. However, if you migrate and run into any issues, our support team is always happy to help. I also chose the Office for Mac 2011 suite as the32-bit application, because several users have told me that it contains the setof 32-bit apps that they most want to run in Catalina.After you finish this setup, you will be able to run 32-bit apps on your Mac running macOS Catalina.Try and run 32-bit apps on your Mac.Let us know inthe comments which 32-bit apps you need to run on macOS Catalina and how thisis working out for you. Parallels Desktop allows for migration of operating systems from Boot Camp, an old PC, other virtualization products, and more but we cannot guarantee that individual applications will migrate appropriately without contacting their individual support based on their licesning policies. We cannot dictate the licensing restrictions that Adobe has in its user agreement policy.

   If you are migrating files from an on-premises SharePoint Server, you are prompted for your username and password for that site unless you provided those credentials in previous steps.

   If any errors appear in your file, it is detected on a line-by-line basis. The error indicates which line or lines contain(s) the errors. You cannot proceed until you correct the errors in your file.

   Important

   We do not support proxy connections. Using Proxy connections yields errors, such as 'SharePoint login fail' or 'cannot load document library'.

7. If you want to select another set of data files to migrate, select Add a source; otherwise, select Next.

8. Review your settings, and the select Migrate.

Monitoring and reporting status of migration jobs

After you select Migrate, the progress of your migration jobs appears. As they complete, you can view either detailed or summary reports of an individual job or a single summary report that includes all migration jobs submitted during this session. To learn more, see Using the SharePoint Migration Tool Reports.

Resuming migration jobs

If you need to close SPMT before a submitted job has completed, you can restart the tool from any computer.

Note

Mac User Migration Hangs At Looking For Incompatible Software Windows 10

To resume a submitted migration job, it has to have been running at least5 minutes. It pauses at the point you closed the SPMT. If your submitted job was running less than five minutes before the tool closed, you must resubmit the job.

To resume migration jobs

1. Launch SPMT. Using the same Microsoft 365 username and password you used when you originally submitted the job, select Sign In.

2. After you sign in, a screen displays any paused migrations, providing details about what has been completed and what remains.

3. If you want to add additional migration tasks, select Select new sources and destinations; otherwise, select Next. Your migration jobs will be resumed. If you are migrating files from an on-premises SharePoint Server, you are prompted for your username and password for that site.

Incremental migration

After a migration task has completed, you can save it to be rerun at a later date, allowing you to copy only those new or updated files in the source location.

Note

If you wish to make changes to this setting, do so before your initial migration job is submitted. This setting is global; it will apply to all subsequent tasks you submit.

When this setting is on, an incremental check of the SharePoint target environment is performed. Files are evaluated as follows:

Availability

Note

Currently, the SharePoint Migration Tool is not available for users of Office 365 operated by 21Vianet in China.
It is also not available for users of Microsoft 365 with the German cloud with the data trustee, German Telekom. However, we do support it for users in Germany whose data location is not in the German datacenter.

Related Topics

This method of troubleshooting can be useful in many situations. I used to use it when I was a video editor and had a corrupt clip within a huge collection, but Avid wouldn't tell me which clip was corrupt. You remove half of whatever it is that's causing problems and try. Divide the bad half and try again until you're down to only the bad piece(s). It can be tedious, but it can sometimes be the only solution.
Great hint for general troubleshooting.

Nothing wrong with, and I support 'more novice' tips being posted.
Not only that, but sometimes, us long-term guys get to be wise-a$$es and forget basics. :)
I can't count how many times I've gone for the most complex fix only to have missed an easy one that would have saved some time. :)

The Kernel Panic mentioned in this thread can only occur when a version of the BRESINKx86Monitoring driver from January 2009 or even older (this was 7 product releases ago!) is being copied to a system with Intel Core i technology. Certain specifics of Core i processors were not known in early 2009 yet, so the drivers of that time could not foresee a certain incompatibility which can lead to a Kernel Panic. This issue was immediately fixed when Apple released the first Core i systems in March 2009.

The general hint to give here is to check the system installation for hardware-specific software, and to update these software products to their latest releases before cloning. This will avoid such problems before they can occur, and the migration will run smoothly.

Just so you know, I wasn't pointing fingers at your work Marcel, I suspected the case was exactly as you described. Something new came along that could not have been anticipated. Thank you for confirming my suspicions! I appreciate your work on the temp utility.
From now on I will check the start up items before any more migrations. Most likely in 4 years since this spiffy new iMac seems pretty solid.
One funny co-incidence, I moved the old tower into another room and the display stopped working. The power indicator blinks 3 times, so it's off to Apple for service. I suspect my old system is jealous of the iMac.
I have enjoyed this site for some time, so I am hoping in a small way I'm giving back by sharing my experiences.
Rich