SharePoint & Office 365 Migration
Checklist

Before you begin

 planning it’s important to understand, as much as you can, what content you have, who owns it, how it is structured and how important it is. This is important for many reasons, including enabling to shorten your migration time by removing redundant, obsolete, and trivial data (ROT), helping create a governance plan for structuring your data and securing sensitive content, and prioritizing which segments of content

 

You can create a plan that will not only save you and your organization tons of time in the long run by checking for customizations that may need to be rebuilt, functionality that can be replaced with new features, content whose stakeholders may need to be more involved in the project, and data that can be moved in its current structure and form. Doing so will also give your organization the opportunity to set up for long term success and a higher rate of adoption as your business users begin utilizing their new technologies. 

Steal our Checklist!

  • Farm Overview 
  • Farm Topology 
  • Web Applications 
  • Content Databases 
  • Site Collections 
  • Lists and Libraries 
  • Pages and Items 
  • Users and Groups 
  • Solutions & Features 
  • Web Parts 
  • Master Pages & Page Layouts 
  • Site and List Templates
  • Custom Content Types  Custom
  • Columns  and Alerts 
  • Event Receivers 
  • InfoPath and Managed Metadata Service 

 

Design Your Migration

Once have a good idea of the types and structure of the content you need to move, segment the information you have gathered and communicate with business stakeholders to understand what is important to them. Discuss security, structure, features that may need to interact with the data in the new destination, and how the content itself ties in to the business user’s daily tasks.

 

This part of the migration typically involves lots of interdepartmental communication, so one of the best things to do during this stage is take a deep breath, 

As you gather details, focus on the end user experience and how the future structure will relate back to the implementation. This includes what workflows will interact with data, how that data will be stored, secured and then archived or deleted when it’s no longer essential. Try not to force end users to add more than two to three pieces of metadata to any document, and automate as much of the process as you can. As you plan, keep in mind that there may be third-party tools that can help you make your requirements a reality. Try to avoid microservices for individual use cases though as no one wants to manage 300 paid apps, especially when there may be workarounds via Office 365 Services.

Data Migration

Get your migration plan OFF the ground With DFSM consulting TODAY!

Talk with an Expert Today

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Talk with an Expert Today

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.

Download Template

You consent to the processing of your
personal data by clicking on the button.
Terms of use.