Assisting business in migrating content

-
More specifically, assisting the business in migrating content from an old HTML/ASP/ASP.NET website to a new SharePoint site.

These old site are probably 10 years old, filled with out of date data, poorly updated, with no owners or any accountable members. When migrating you want to provide the end users with the following

  • Content is current and updated regulary
  • Permissions are assigned and maintained
  • Content is easy to find
  • Content and site is inviting

in otherwords, everything that the current site is not providing!!

So how do you do it? Well, depending on your timelines, the following approach proved successful.

  • Identify the taxonomy of the new site
  • identify owners of each node of the taxonomy
  • Get them all in one room and prepare them for whats to come
  • Provide simple templates that will help the owners get content in the strucutre that matches the pre-defined taxonomy (define restrictions and governance rules of the sharepoint site)
  • Give the owners time to populate the templates with content (3 weeks seems ike a good amount of time on average)
  • QA the completed templates
  • Create the site structure based on taxonomy and completed templates.
  • Use trained data capturers to migrate the content from the template to SharePoint.
  • QA and Go live.
Seems like a bit of work, on average, this type of engagement takes about 10 weeks. depending on the size of the site being migrated.

it takes this long because it not a simple copy and paste, if we did that, all the faults of the old site will be carried over to the new site, and that will compramise user adoption.

If anyone else has been faced with the task, but had a different approach, let me know.

Comments

Post a Comment

Popular posts from this blog

Why there is a shortage of SharePoint experts

-
Image
Microsoft has been very successful to promoting their SharePoint product, even though SharePoint has been around for a while, there 2007 and now 2010 version is something every organisation wants. With Microsoft practically giving away SharePoint licenses to organisations via EA agreements – we are reaching a very unique and rather unexpected situation where the demand for SharePoint developers is surpassing the demand for Web developers. This shift in demand are forcing IT departments and Web Development companies to reduce the size of the web development teams and increase the size of their SharePoint team, in other words, take staff originally hired for web development and get them into SharePoint development. This is currently the "normal" approach in getting SharePoint experts, many IT Recruitment companies still don’t understand this shift in demand, and are not yet focusing in the SharePoint space, some recruiting companies haven’t even heard of SharePoint and
Read more

Don’t use SharePoint 2010’s mobile view for internet presence sites

-
Image
SharePoint offers a lot; it’s a platform that provides BI, ECM, Search, collaboration and a lot more including WCM.  It’s the Web Content Management (WCM) component that makes it’s a great platform for internet presence sites and with the more appealing pricing structure available for internet presence, it is becoming the preferred choice to internet deployment. Without any effort from the SharePoint deployment team, SharePoint provides a “mobile friendly” view of the site been created.  In theory, this sounds great, this means that we can create a SharePoint site, apply a nice appealing brand to it (it is an internet site, so the look is important), spend some time on the structure the content so information can be easily found (very important for internet sites), configure search correctly and then fill the site with information and images knowing that it will automatically work out the best way to display this information on mobile devices, right?   WRONG! SharePoint offers
Read more

The move from Technical Expert to Manager

-
Image
Let me start of by explaining how things were before I became a Manager. I worked my way to a Senior ASP.NET developer with a decent amount of SharePoint exposure; it only took me 7 years. And in those 7 years I was usually poorly managed; • scope was poorly defined and not managed • no clear plan was in place or plan omitted crucial steps • timeframes were unrealistic • no quality checks were in place (faults were discovered during client demo's) • clients expectations were not managed • communications were poor • processes were not followed • resource allocation was poor (I once requested a .NET developer and my Manager believed he solved the problem when he got me a junior network administrator who knew a little HTML) • poor risk management In many cases I had reached a point where I had very little faith (or respect) for my manager that I insist that they present me with the requirements and leave me alone so I can “do my magic”, this involv
Read more