The trouble with SharePoint 2013 migration

For companies that are considering a SharePoint 2013 migration, the move may not be as turnkey as you think. Data migrations can be time-consuming, costly and difficult.

For more on SharePoint

SharePoint 2013 guide

Team sites break down silos

SharePoint 2013 and social media

In any migration, you have to consider your current environment, as well as governance and architecture concerns. And you need to review your data to determine what you will migrate. In addition to your evaluating your architecture and whittling down legacy information and sites, you need to review your taxonomy and metadata and consider secondary issues such as storage capacity.

"Migration is a scary, scary thing no matter where you're migrating from," said SharePoint expert Scott Robinson. "But when you're migrating into SharePoint from another platform, you have a whole host of issues to consider … where information is stored in a very different way."

In this podcast with Robinson, we'll explore some of the lessons learned from companies migrating to SharePoint, including the following:

  • The complications of migrating to SharePoint from another CMS platform
  • The important considerations involved in migrating to a new SharePoint CMS from an old one
  • The most common mistakes made in SharePoint migrations
  • Handling migration in-house vs. bringing in third-party support


This was first published in November 2013

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: