Super Best Practices That are Super

One of the advantages of being an ISV in the Microsoft space and working with so many great consultants is that it gives me an opportunity to hear so many different methodologies and approaches to migrating. On the contrary, I get asked quite often for some best practices around using our Office 365 migration solution. I’ve collected a little list of suggestions and best practices and figured it would be good to publish out to the blog – feel free to add any ideas you’re holding onto!

  • Run our premigration scan to identify customizations or problem areas before you start migrating. Use this to clean up environment prior to migrating rather than identify issues as you go along. We liken this to throwing away trash before you move to a new home so you don’t have to deal with junk at the new place and can start fresh.
  • If migrating a large volume of data, turn alerts off in O365 because you don’t want to flush customer mailboxes.
  • Migrate in smaller batches when possible so you can isolate potential failures or issues as they arise. We record very detailed logs to track warnings, or failures but it’s easier to see the whole picture across a smaller job than it is to sort through a larger project.
  • Piloting your migration will help understand best times to migrate, networking, server capacity, and identify problem areas ahead of your migration. Use the results from your testing to help get the best throughput for your move.
  • QA as you migrate, not after total completion. You want to identify any potential changes you want to make prior to completion so you don’t have to do the same work twice.
  • After completion of a full migration, continue incremental migrations to carry deltas over to O365 while users continue previous environment’s usage before a complete cut-off so you can audit migration success.
  • Filter out unnecessary libraries/lists/files/etc. for example master page galleries, web part galleries.
  • Create user mapping ahead of migration so you can kick off the project quickly and don’t have to backtrack into mapping.
  • Migrate content type hub sites first and migrate consuming sites later, otherwise you will miss all the association between content types and their references.
  • Unique permissions are easier to manage on-prem – if you’re moving to the cloud it may be worthwhile to standardize permissions better.