locked
Sharepoint Migration tool Feature Requests RRS feed

  • Question

  • I have been using the SPMT for some time now to migrate users Home drives to Sharepoint/Onedrive

    I enjoy the tool. however there is TONS of room for improvements. I am not sure this is the place to post this, but couldn't find a better location

    1) For existing migrations that I can resume, it would be AMAZING if when a migration completed. I could get back to my other tasks/migrations to kick them off. However it appears you have to leave the tool, re-auth, etc...very pain staking

    2) Folder /file restrictions. It is nice to be able to filter on file types, however since I am performing alot of home drives, most users have the same folders that would not need to go to onedrive (appdata for example)

    3) ability to Sort the running migration & possibly filter. I sometimes have about 100 users that I bulk load via the CSV. As these migrations take place, it appears the order is completley random. I Also dont understand why/how a few users will be on Round 3, where some other users are still queued for scanning.

    4) ability to alter the migration settings after the first time you run the migration. As it is now, you can only modify the migrations settings prior to submitting the job. I have created a migration on accident that I had setup to Not copy invalid characters, however I could not get back in to change that. I had to remove the migration , re-create it & setup my options

    5) since you allow the tool to copy to onedrive, it would help TREMENDOUSLY if you could add something to the tool, that we can elect to NOT have the migrated files sync down to the users local machine when OneDrive Syncs. This one is major. The whole purpose of home drives is to offload files so that your local harddrive doesnt fill (also to provide redundancy in event of failure.) Some of our users only have 20+/- gb free space on local drives, but then have 20+gb in their home drive, so you can see how this can cause issues.

    Thats all I can think of for now, I am sure Ill think of others

    Friday, January 12, 2018 4:35 PM

All replies

  • I know I just mad a bunch of statements...but no one from MS wants to chime in?


     the folder for the migrations reports/logs should take the name of the migration if you decide to name it. I typically name all mine, & then when I go back in to grab the reports I have to run the utility again, & open from there so I know which is which.

    or I have to locate the summary file, see the users in it, & then copy/rename the folder appropriately 

    I have 5 very large file servers (1 per site location) that I will be using this tool on. 

    I would think MS would want this type of real-world feedback as well as possibly work with me on some issues I have been noticing from time to time


    Wednesday, January 17, 2018 3:03 PM
  • I'd like to add that we should be able to list a Sub folder path or drill down to a folder when choosing the destination of our migration data.  Instead of just giving us just the basic options, "Documents, Site Assets, Site Collection Documents, etc.." it would be helpful to list the entire folder hierarchy and let us decide.  I know that it is an option with the SPO Migration Package cmdlets " -TargetDocumentLibrarySubFolderPath".
    Monday, February 19, 2018 4:02 PM
  • You can mention the subfolder name if you use the CSV option.  For more info - https://support.office.com/en-us/article/how-to-format-your-csv-file-for-data-content-migration-9183b289-f1cf-4c69-8240-8bfcdf3809bb 

    Thanks - Hari

    Tuesday, February 20, 2018 3:33 PM
  • Hello Steve,

    These are really good feedback.  I will take all the above except the 5th one to the SPMT team.  I will post back as and when I get an update.

    Thanks - Hari

    Tuesday, February 20, 2018 3:37 PM