HomeAvePoint BlogHow to Successfully Migrate to SharePoint 2013

How to Successfully Migrate to SharePoint 2013

I recently had the opportunity to author an article for Computerworld NZ highlighting the steps an organization should take to ensure a successful SharePoint 2013 migration.

Migrating to SharePoint 2013 opens the door to a variety of advanced features for collaboration, but can also pose roadblocks in transitioning away from your former environment. To transition effectively, a thorough study of your current environment is necessary to determine the next steps. In the article, I explain the ins and outs of a successful migration, and examine key questions for pre-migration. These questions include:

  • What is the state of your current collaboration platform? Have a good overview of documents, network and hardware infrastructure, user mapping, security directory and implementation, and interactions with other systems.
  • How much content needs to be migrated? Consider the amount of content residing in your current environment, including documents, images, pages, the number of versions for each object, and content hosted on external file shares. Understanding the totality of your content will help you size up your destination environment.
  • What is the level of customization in your current environment? This question is most applicable for migrations from previous SharePoint versions to SharePoint 2013 or SharePoint Online. A migration can become more complex when it involves existing customizations, such as graphical and branding elements or those related to third-party tools.
  • What level of technical requirements are necessary for migration? Technical requirements are not an issue once the auditing of the current environment has been carried out. However, the level of functional requirements will often impact the duration of the pre-migration phase.

A thorough assessment will help you avoid potential migration issues and ease your transition into SharePoint 2013.

To read more about successfully migrating to SharePoint 2013 and the key questions to ask, please visit Computerworld NZ.

To learn how AvePoint can help provide SharePoint migration solutions for migrating content from various legacy systems into SharePoint, please visit our website.

Fabrice Di Giuliohttp://blog.digiulio.fr
Before joining AvePoint, I worked in AtoS as a SharePoint Architect and Technical Team Leader. I was involved in projects on on-premises global architecture and on the SaaS layer of private Cloud environments. I was a member of the Microsoft Partnership management team and a SharePoint trainer for either customers or internal trainings. Combining this experience and my knowledge about our solutions, I am very easy at speaking about governance and Office 365 benefits (as well as SharePoint of course!). From a personal perspective, I'm blogging (you can see my public blog at http://blog.digiulio.fr, in French but implementing the bing translator plugin) and writing articles about Dynamics CRM the French IT Pro Magazine. Since the 1st of January 2015, I am also awarded as a Microsoft Dynamics CRM MVP.

3 COMMENTS

  1. This is an excellent post with great details and talking points. The workloads that we see organizations moving to Office 365 are becoming more and more interesting — even with organizations that you would not expect to be moving to the cloud such as public sector and healthcare. At first we were seeing a lot of MySites and extranet migrations. Now with the advent of NextGen Portals and shared service integration, we’re seeing more adoption and adoption that takes advantage of the power of the cloud.

  2. Excellent post Fabrice! These are the small details that can quickly be overlooked when we are pressured by the Business to make the move or even pressures of a tight deadline. Discovery and Assessment is not only a pivotal portion of the Migration project lifecycle, it’s the foundation!

    This phase gives us the opportunity to determine the data in your environment which is actively used as well as mission-critical content that needs to be migrated over to the new system. This is also prime time to take a look at the stale content throughout the environment and determine the appropriate manner to deal with it – whether that’s archiving data for retention purposes or complete removal. Once you have taken inventory of all existing content, you will have a solid understanding of what you will be migrating and can smoothly transition to the next phase.

  3. Fairly new in this game, but I personally find that the bulk of our professional services hang around the area “How much content needs to be migrated?”. To figure this out, it leads to other questions “what content needs to be migrated?”, and “how should it be organised going forward?”; In particular helping clients transition from traditional file shares into Sharepoint for the first time.
    Working with our own deleveopment power BI visualisation File Share tooling, and stake holder interview processes, we tend to find the whole journey ratifies and develops the entire business processes related to digital content (pretty much the whole of every business). This is why I find it so interesting and exciting working in this emerging area of office365 and Sharepoint 2013

LEAVE A REPLY

Please enter your comment!
Please enter your name here

More Stories