Posted on
Wie Sie SharePoint Content Datenbanken richtig aufsplitten

On October tenth, Microsoft will finish support for SharePoint Server 2007. For a lot of organizations, Microsoft ‘office’ SharePoint Server (MOSS) 2007 was the version that could see adoption over the enterprise, paving the way in which for that break-out success of SharePoint 2010 along with a truly enterprise-wide platform. The 2007 version is how the idea of SharePoint like a “Swiss Army knife” was created, with the concept that it may be formed into whatever your business needed so that it is.

Should you adopted that type of thinking, and formed your SharePoint 2007 atmosphere right into a fully-customized and deeply-integrated means to fix satisfy the unique requirements of your business, the idea of moving from the platform most likely appears daunting. I’ll admit that i’m a large fan of “If it ain’t damaged, why repair it?” method of technology. Actually, I frequently tell audiences to disregard the sometimes high-pressure sales tactics of Microsoft along with other OEMs who attempt to talk customers into upgrading solutions without first understanding the price of moving — and the price of not moving (missed possibilities).  However, as we’re speaking about SharePoint 2007 particularly, I have faith that the most recent versions (whether on-premises or online included in Office 365) have dramatically improved the capacity and user encounters of SharePoint.

By not relocating to SharePoint 2016 or Office 365, you’re losing measurable productivity and business value.

SharePoint migration isn’t just about moving your sites and content to a different system, but ought to be considered an chance to fix mistakes and problems, to reorganize and reinvigorate your atmosphere, and also to fully leverage each of the features and abilities that SharePoint provides. And as you have anxiously waited such a long time to maneuver out of your 2007 atmosphere, you might also need the advantage of years of community experience. I’d venture a reckon that there’s no workload scenario or personalization that somebody locally hasn’t experienced and overcome. Now it’s your decision to leverage that learning.
Within an article captured (SharePoint 2007 Finish of Existence: Your Last Opportunity to Evolve), Shyam Oza outlined numerous technical and management factors for organizations considering upgrading their 2007 environments. He’s some good advice that will help you result in the transition simpler:

  • Take a listing of the items your workforce really loves in SharePoint 2007 and also the features which are mission important to your company. Have a very good knowledge of the characteristics which allow your finish users to complete their daily work.
  • Identify any custom code that’s crucial in your legacy deployment. It’s important to determine if you want to refactor that code, purchase a 3rd party application or make use of a native capacity within the latest version of SharePoint. There’s lots of chance to rebuild these older encounters with technology advances like web parts, SharePoint Designer, Flow and PowerApps.
  • According to your inventory, determine whether individuals priority features remain or maybe there’s a substitute around the modern platform. Use individuals abilities being an access point for training and delighting the users within your business.
  • Educate your finish users around the latest version of SharePoint. Host workout sessions or “lunch and learns” just to walk users with the updated features. For instance, not every users knows that “…” means “click for more options.” Others won’t know ways to use the “share” button correctly. Should you take time to undergo these records together with your workforce, they’ll become more wanting to provide your new deployment a whirl.


Some good advice — however i would expand around the last point about finish user education. In my opinion, the greatest element in migration success comes lower to 1 factor:

  • Involve your finish users within the planning process early, and leverage them during your implementation and testing.

Involving finish users early and frequently will dramatically boost the rate of success associated with a SharePoint migration, and also the reasoning is straightforward: Those who make use of the system wish to have a voice in how it’s formed, and most importantly, those who make use of the system probably the most (and make and manage all the documents and workflows within in) are usually the best individuals to decide on how to migrate that content. If you’ve seen certainly one of my migration planning sessions, you’re likely heard me recite a planning truth that especially rings true with migration planning:

“The more you involve people along the way,
the much more likely individuals will support that process.”

Transparency comes with an amazing impact on people — even when they don’t accept the end result, if finish users are members of the discussion, and feel heard, they are more inclined to support individuals decisions.

Some recommended techniques for involving your finish users may include:

  • Review and approval of the suggested/refined information architecture.
  • Establishing regular and consistent feedback mechanisms, for example surveys, user groups, online forums, and something-on-one sessions with key stakeholders.
  • Creating your present-condition and future-condition designs and documentation.
  • Creating use cases around your most typical and demanding business processes.
  • Prioritizing your future-condition design by involving finish users inside your piloting, test migrations, and broader project planning efforts.
  • Defining what success appears like, so that you can correctly scope any project and never finish in scope-creep limbo.

Your migration approach (and underlying change management processes) ought to be flexible, recognizing that no quantity of planning in advance covers every scenario. Migrations ought to be an iterative process, giving your finish users an chance to check the waters with any new functionality, and supply feedback on which works, and just what doesn’t work. Ultimately, a effective migration has more details on proper planning and alter management of computer does with additional features. Within the finish, your objectives ought to be a good alignment involving the technology and business needs, quick access to timely and relevant content, and happy finish users.

I frequently like to indicate that SharePoint migrations tend to be as an iceberg: a specific item at first glance may be the technical part of the effort — the moving of information and attributes between environments — but underneath the surface is how the actual work begins. Moving from MOSS 2007 towards the new edition of SharePoint is a massive planning effort, so leverage the understanding and expertise of individuals who’ve gone before you decide to. That’s the advantage of community!

And make certain to download the disposable sources obtainable in AvePoint’s SharePoint 2007 Finish-of-Existence Toolkit to help kick-start your planning process.