SharePoint migration, the area where several challenges occur and all we need to do is to mitigate all the risk factors and provide a secured migration strategy.
In this blog, I’m going ahead to elaborate a very common approach which is applicable for most of our migration plan. After the migration is done, in most cases customer requires the OLD SharePoint site should be live in read-only state for some times and the site user’s must able to view the information like ‘ This site has been migrated to……’.
In many cases, we have seen there are couple of thousand users exist for one site collection and it is not feasible to notified all site users about the migration date and plan. In other words their browser link for the old SharePoint link is not going to change and providing this kind of information they can update the new link.
The objective is to display some kind of information about the recent migration to end user and allowed them to redirect to new site after pausing let’s say 10 sec.
We have a choice utilize out of the box Content Editor webpart for taking care this approach. Question is what will happens when we found there are many sub sites (don’t be surprised to see a site collection contains more than 500 sub sites).
For the similar scenario, we can use one simple console application which will dynamically put one content editor webpart from root level site collection home page to all its sub site home pages. Obviously you can implement this methodology as a kind of feature, if you want. I prefer the tool/console level approach because this is just need to run once and no need to deactivate or activate latter one, ultimately down the line the old site will be deleted. Read more…
