Migration Methodology

As an experienced Consultant, I find it’s difficult to say when considering a data migration strategy which step in the process is most important. The success of a data migration methodology really depends on all the components of a solution working well from beginning to end. But it’s certainly true that a successful data migration project cannot take place without a robust means to push content into its new home, whatever that might be.

Since virtually every content management system (CMS) on the market is different, there is no silver bullet for loading content quickly and dependably. Each application programming interface (API) is different and can vary greatly in terms of quality style and completeness. Some may require a custom web service, deployed on the target environment and called remotely.

But this solution isn’t quite optimal. What if the client’s target environment is completely inaccessible for some reason? Perhaps the client’s security model forbids deploying foreign services. Microsoft’s SharePoint 2010 CMS circumvents the necessity to deploy remote services with its client object model. After getting your hands on the required libraries the SharePoint 2010 API is suddenly at your fingertips. Using this technique, a data migration can be accomplished using a locally deployed custom service after supplying the required credentials!

While I found SharePoint’s client object model to provide a promising new way to connect to a CMS, I thought the API was incomplete and sometimes poorly documented. Luckily, the out-of-the-box web services packaged with MOSS provided the methods I required. I am excited at the prospect that more CMSs will start packaging up libraries that provide the tools necessary to connect to an environment with a remote machine. It simply provides a safer solution for the data migration and one that doesn’t require deploying anything on the client’s machines! The big upshot of the client object model implies that projects are less likely to face resource bottlenecks because additional access to secure systems is not required. A smaller gap between the development and testing periods allows more time for refinements and a better quality data migration solution.

It seems that Microsoft is leading the way in this regard.

  Download our Data Migration - Seven Steps to Success White Paper to gain a further understanding of the data migration best practices that should be considered when beginning a migration project.

Moving house is said to be one of the most stressful things to do in life. First, you need to find the new house considering the requirements you need. A 3 bedroom or 4? A big yard or small? Lots of storage or minimal? City or country? Next, you need to negotiate the terms of sale and close on the house. Then comes the actual move. This is the part of the process where you go through the years of built up stuff and decide whether to be rid of it or not. This process often brings to light stuff you haven’t seen for years, broken items you’ve saved ‘just in case’ and some keepsakes. Overall, you are cleansing your household contents.

This same process applies when a corporation approaches its Enterprise Content Management (ECM) decisions. However, it’s a constant surprise these decisions are made without having all of the facts at hand. Knowing answers to questions, such as: how much content exists; how often is content accessed in a week/month/quarter/year; who owns the content; what happens to old content; what content adheres to today’s standards; and when changes are made, how does the change impact on the other content; is the only way to truly understand what is in a corporation’s household content and is an essential part any data migration strategy.

Many ECM novices and veterans most likely have a question mark over what is in the content inventory, so getting to grips with this is often the main problem and is only done when a move is in sight. But content tooling is available and should be used to not just manage content (which most ECM systems already do), but govern it on an ongoing basis. These content tools provide answers to all of the questions that should be known before a content migration is even considered, as you’ll then be better placed to decide on the necessary requirements for the new system.

You wouldn’t move house without taking inventory of your household contents and you shouldn’t make ECM decisions without this analysis either.








Download the ‘Five Steps to Discovering the Real Shape of Your Digital Content,’ 
to learn more or check out the Vamosa Migration Methodology.

The issue of controlling content and privacy popped up in the news last week; as Facebook has reviewed its privacy practices after a new feature exposed private information and wrested control away from users as to what content was shown to whom.

Personally I find the amount of personal information on the public internet  astounding  and this is just the random non-sensitive information. If my birth date gets out on the web, at worst I might get an extra birthday card or two; but corporate entities cannot afford to let sensitive information become public without often facing heavy legal penalty; not to mention what it does to their reputations. Facebook is reported to be losing users as a result of their miscalculation. The more sensitive the information the larger the risk becomes. Structuring content leads to predictable data. Predictable data leads to predictable areas of sensitivity and predictable areas of sensitive material can be controlled and protected.

Now I am not saying that if Facebook had implemented a more cohesive content model and massaged their content into those structures that they wouldn’t have exposed this private information. But I am stressing the importance of understanding the content structure and which portions will be provided to whom. Content Management Systems are one part of this equation – they should control the content as expected so long as it is stored in the right place. That is the key; so long as it is in the right place.

Structure and predictability are cornerstones of any successful migration. Taking content that was once fragmented and moving all the like parts together into a common structure(s) is the first step. And it can be an undeniably complicated step. With complication comes the need for traceability/auditability; the need to understand where content is going and what that content is. This applies whether that content is within the content model or the content object itself.

Having an auditable process, addresses that need. The Vamosa methodology provides two reports, one of which audits where every object will end up and the second that details what content will exist where within each object. This became an invaluable tool even prior to the content migration for a recent project I was on. We used these reports to discover that two of the security parameters required to control user access to sensitive content were inconsistent in the source content! Without that insight we could have had a Facebook-like situation when it came to the migration execution.

Knowing where your information is, when and how it is being consumed and by whom is important and is an essential component in any smart content migration strategy.


To learn more about where your content may lie download the Five Steps to Discovering the Real Shape of Your Digital Content White Paper.