Web Migration

The challenges of content governance are constantly evolving as the volume of digital content published increases exponentially every day and new publishing channels emerge. Who, 12 months ago, for example, could have predicted that Twitter would become such a publishing phenomenon?

Vamosa understands this complexity and we know that dealing with the end-to-end life cycle of content in separate parts can make implementing an effective strategy for managing enterprise content more complex.

In response to enterprise needs, coupled with our understanding of the obstacles to enterprise-wide content management, we have launched two configurable software platforms that incorporate this end-to-end approach to content: Vamosa Enterprise Content Governance (ECoG) Suite for Documents and ECoG Suite for Web. 

ECoG Suite for Documents

ECoG Suite for Documents has been designed to enable the transformation of document repositories into clean, usable content stores that can be governed by ECoG policies. The suite automates the life cycle of documents, from creation to on-going maintenance, supporting taxonomy and metadata management, versioning, policies for records management and archiving, and so on.

ECoG Suite for Web

ECoG Suite for Web allows clients to take back control of web content by automating policies for all stages of the content lifecycle, from accessibility to tagging and from broken links to ECMS migration, making it findable, compliant and more usable. By adopting a SaaS approach to web maintenance, web properties are monitored 24/7 so any breach of policy is trapped and resolved.

Most importantly for enterprises, the suites offer all the functionality previously available in separate Vamosa products, including analysis, data cleansing and migration but bundled into a single installation that is then configurable to the customer’s environment and specific ECoG policies.

If you use a Document Management System (DMS) to manage document based content you will already know that one of the key issues faced is how to move existing content into the new system.

On paper document migration looks relatively easy. A team of people could spend the next six months copying files and documents from their existing location into the DMS. However in order to achieve an effective document migration project it is essential that you consider:

•    How many files can one person move in one day? A document migration project of only 100,000 pages might take anywhere between 10 to 100 days to complete.
•    What happens during this move? Do you place a content freeze over all of the files and documents for the duration of the migration project? What about moving attached documents and handling internal and external links? How can you incorporate this functionality into your document migration strategy?

A document migration does not simply mean changing a few attributes and then placing the content into a slightly different information architecture. Document migrations involve the wholesale change of properties, storage, information architecture and content lifecycle, therefore document migration projects tend to involve hundreds of minor changes to very large volumes of data. This can potentially become incredibly time-consuming and frustrating. To reduce this confusion and to improve data quality, eliminate redundant, obsolete and redundant information and match the requirements of your new system, you really need a tried and tested method.

Vamosa Consultancy Practice, with their collective experience gained on over one hundred client projects, can assist in implementing best practice content quality processes; such as when selected to undertake the migration of the website and corporate Intranet for the UK’s Department of Environment, Food and Rural Affairs (Defra).

Working with integration partner, digital media giant Euro RSCG, Vamosa’s solutions and expertise was the obvious choice to deliver a web and Intranet content migration for Defra.

Gregory Roekens, Technology Director at Euro RSCG said ‘We were asked to provide a best of breed and best value solution to Defra’s business content migration problem and Vamosa’s tools and methods have the reputation as the Central Government standard’.

Vamosa Consulting was able to successfully bring control and structure to all documents across Defra’s content stores, providing, de-duplicated and clean content. As a part of an ongoing Enterprise Content Governance strategy, Vamosa ECoG Suite for Documents also uniquely pinpoints breaches of policy for all document governance areas, and offers an automated process to resolve each breach, allowing document stores to be kept up to code.

Organizations use SharePoint for a variety of things, from Intranets to Extranets, from Customer Portals to document management and for team collaboration.

Recently there has been a significant amount of discussion around exactly what SharePoint is and what it offers. For example, a recent AIIM article highlights 8 things SharePoint 2010 needs to be a true ECM system. A blog by the Microsoft Team describes SharePoint 2010 in 1 sentence, 8 categories and 40 features. The Rez's SharePoint blog provides a comprehensive comparison of features between SharePoint 2007 and SharePoint 2010.

One element thats there has been great excitement around, is the SharePoint 2010 taxonomy implementation and management across sites and site collections. Organizations must spend time and effort building the appropriate foundation for utilizing the content taxonomy. That is all well and good when a green field project is started, but considerations must be given to data that is already stored in previous versions of SharePoint; how can that information be classified correctly when undertaking a SharePoint Migration? Microsoft does not provide a tool or utility which can be used to apply a new taxonomy and as a result many organizations may become stuck during a MOSS migration.

Vamosa recently announced a partnership with MetaVis to help both existing and new customers get a better ROI and increased value when moving into SharePoint 2010 from SharePoint 2003 or SharePoint 2007 environments, by ensuring the new taxonomy values can be applied to documents.

The MetaVis Suite does not simply help organizations migrate their existing content into the SharePoint 2010 platform; it also provides features such as  a graphical top down view of the web estate and it highlights dependencies between objects. This provides the administrator with a complete view of how their sites are structured. The 'Live Compare' feature of MetaVis provides useful functionality as it allows comparisons of two sites to be undertaken in real-time, listing the differences between sites at the granular level of identifying column differences between content types.

Synchronizing two SharePoint environments at the click of a button is only one of many features offered by Metavis that will help SharePoint Administrators perform their day to day tasks more effectively and efficiently, while ensuring their organization has an effective SharePoint Governance strategy.

As noted in a previous post  by Nic Archer it is anticipated that a third of organizations will in time employ a MOSS migration strategy and migrate to the new SharePoint 2010 platform. However in order to maximize organizational efficiency it is essential that all data is prepared prior to the SharePoint 2010 deployment to ensure a smooth content migration strategy.

By defining efficient content taxonomy structures prior to deployment, organizations are able to more easily move content into their new SharePoint environment resulting in improved site architecture and navigation within the new site. This task in itself can involve a significant amount of work before data is ready to be migrated.  If this stage is not meticulously carried out, the value of the content in the new store will be significantly depleted.

The suite of MetaVis tools for SharePoint, now allows SharePoint administrators to reclassify content by assigning new metadata values and new content types during a migration, allowing organizations to migrate more efficiently. Even post migration, MetaVis allows administrators to bulk update metadata, should this be required, further enhancing the findability of data for the user.

With MetaVis, SharePoint administrators can utilize the new Term Store, to graphically re-design and re-architect their content, significantly improving search and discovery of local documents for organizations that are located globally.
By utilizing the capabilities of the new SharePoint environment through MetaVis, administrators will be able transform the web experience, lower the cost of ownership of content management and deliver error free automated migrations, while creating effective content structures in SharePoint 2010 – the ultimate goal for all SharePoint administrators.

To learn more about the suite of MetaVis tools download the MetaVis Architect Suite Buisness Results Sheet.

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.

In short: when its in a zoo… Bare with me. Common Eland in Zoo

A document is a record of something that has been observed. Such a record can be anything – a utility bill, an employment contract, a sculpture in a museum, or a painting on a wall. All are examples of documents describing something else. The utility bill records and describes your usage of gas and electricity. The employment contract records and describes the details of the handshake you gave at that final job interview. The sculpture or painting documents – there’s that word – a historical event. All these examples of documents are records of something observed by something or someone else.

Paul Otlet (1868-1944), the father of information science, is known for his observation that documents could be three dimensional. As examples of such “documents” Otlet cites natural objects, artifacts, objects bearing traces of human activity (such as archaeological finds), explanatory models, educational games, and works of art.

Suzanne Briet (1894-1989), also known as “Madame Documentation”, states her case through the enumeration of six objects:

•     Is the star in the sky a document? No.
•     Is the photo of the star in the sky a document? Yes.
•     Is the stone in the river a document? No.
•     Is the stone in the museum a document? Yes.
•     Is the antelope in the wild a document? No.
•     Is the antelope in the zoo a document? Yes.

Suzanne Briet rules: an antelope running wild on the plains of Africa should not be considered a document. But if it were to be captured, taken to a zoo and made an object of study, it has been made into a document, it has been made evidence. So there is a process involved in making “the something” into a document – we call it documentation.

As humans, we’ve invented all kinds of devices to aid in the process of documentation: library cards, folders, URLs, bibliographies, tags, taxonomies, reference documents. They form part of the discipline that is documentation and the basis for content management.

With the advent of content management systems we seem to have lost some of the high-level abstract concepts that were clearly laid out in the early parts of the 20th century. As an industry sector, involved in content management, we’ve become too focussed on the implementation details of content management systems and the limitations that these systems face.

Context

“What is metadata? What is a document?” These questions typically go hand-in-hand and are often naively answered by: “the document is a file or a blob that is stored in database but is difficult too manipulate, so the metadata, table rows and columns, are used to facilitate manipulation and describe the document”.

Metadata provides context with which to consume the document. You’ll have seen this in a zoo. You walk up to the antelope enclosure and there’s plaque containing the name, Latin name and a map of the world with a particular part of Africa highlighted describing the antelope and its origin – metadata. The zoo is giving you context with which to understand the antelope document.

The same holds true for documents in a content management system. Documents are stored in a particular context described by their metadata. The folder, the author, draft/publish status, tags, taxonomy are all pieces of metadata to aid the consumer in consuming the document.

That consumer may be the content management system itself as it responds to the query “give me all documents in the /marketing folder” on behalf of a web visitor. The consumer can also be a records management system archiving documents “in a published state and that are older than 24 months”.

Documents never exist without metadata, without context. For example, the print-out of sales figures that I’ve thrown in the wastebasket is a fully-fledged document of our company’s sales figures telling the person that picks it out the wastebasket to treat (read “consume”) the document as a discarded document.

I’ve seen this catch people out on a few content migration projects when they try and de-duplicate content repositories. They classify documents as duplicates based on their contents alone, without ever taking context into account. De-duplication is tricky business because in doing so you are destroying metadata that is right-or-wrongfully been created to help consume documents.

The accurate consumption or manipulation of documents is intrinsically tied to the accuracy and completeness of their metadata. Is the print-out of sales data in the wastebasket to be trusted? Is the sales data accurate? How should the reader consume the document? Look at the metadata! Its in the wastebasket. This opens up the possibility: did I mean to throw the print-out in the wastebasket? Is the metadata accurate? The reader can only make that decision with more metadata. The reader could phone or email me and ask: did you intend to discard that print-out? Thereby creating more metadata and a better context with which to consume the document.

Content management systems merely store metadata, human beings create metadata – often by hand, sometimes using automated tools. The process of generating metadata or maintaining its accuracy is a human process. Computers don’t care about accuracy or completeness.

Adriaan Bloem, analyst at CMSWatch, touches on this by labeling enterprise search as a “brute force” approach. Adriaan also points out that metadata or context is neccessary to communicate. He’s right – otherwise how do we make sense of a document ?

What if metadata contains a document, i.e. when one document describes another? Doesn’t this form of reasoning collapse in on itself?

What if you took a photograph of the antelope and attached it to the information plaque outside the enclosure? So when the antelope is having an off-day and its hiding in the undergrowth, passers-by can still learn about it by reading the plaque. Now you’ve got one document (the photograph) describing another (the antelope), haven’t you? Aren’t both documents? Wrong.

We can describe documents with other documents. Suzanne Briet would argue that the antelope in the zoo is the primary document and any scholarly articles written about it are secondary documents. They provide context around the primary document. There’s is a document and there is context with which to interpret that document – metadata. Nothing else. Document… Metadata… Document… Metadata.

In an English language sentence “things” can be both subjects as well objects, yet can’t be both at the same time. In one situation the photograph is a document, described by metadata from a digital camera (exposure, shutterspeed), in the other situation it is metadata describing the antelope.

Confused? What is metadata ? In any given situation, ask yourself what the document is and by exclusion all that isn’t is metadata.

So what does this means for content management systems ? Are they all broken? Do we need metadata management processes as well as content management processes? Do we need a separate metadata lifecycle to run alongside a content lifecycle ?

The answer to those questions is unfortunately – yes. Yes, we do need separate metadata management processes. Yes, we do need a separate metadata lifecycle. Unless… we stop building content management systems in the naive fashion of blobs for documents and table rows and columns for metadata. We need to start building these systems so that there is no technical distinction between the content store and the metadata store. Having separate stores for content and metadata causes us to duplicate our efforts, causing us to define duplicate processes to support the lifecycle of both document and metadata.

Ironic, since a promise of content management is the removal of duplication.

As unstructured content grows exponentially, businesses need to capture, store, manage, integrate and deliver all forms of content across their enterprise. Knowledge workers  need the right information at the right time to make the right decisions.

Managing unstructured data (web content, email, Blogs, user-generated content) is inherently different, and in many ways more challenging, than controlling its structured counterpart. Controlling this ‘digital landfill’- as AIIM would have it – requires organizations to discover what content they have and understand what condition it is in. Through our extensive experience in enterprise content migration projects Vamosa is only too aware of how frequently organizations are faced with these challenges – for example when we recently worked with IBM.

IBM was required to migrate from their legacy system to Lotus Web Content Management (LWCM) in order to gain control of their digital content. A full understanding of their current content inventory was therefore required to ensure that only the necessary content was migrated.

Using Vamosa Content Analyzer IBM conducted a full content audit; which involved crawling all content and nullifying any obsolete or redundant content, ensuring there were no broken links and identifying any outdated pages. Once the appropriate content had been identified, it was enhanced, allowing IBM to remove duplicates and manage version control through automated classification and tagging.

Vamosa Content Migrator was then used to simply, automatically and quickly migrate the required content into Lotus WCM within the project’s timescales. Vamosa solutions allowed the project to be completed up to four times faster than alternative approaches, at a quarter of the price and with no impact on day to day operations.

To learn more about the key implementation steps required in order to achieve a successful migration into IBM LWCM, download the 7 Steps to IBM LWCM Migration white paper.

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.

Do you understand your content lifecycle? Do you even have a content lifecycle? A content governance model, such as Vamosa’s Enterprise Content Governance (ECoG) framework is built around control and governance of content from creation, through consumption and on to retirement/archival or deletion. Implementing a governance model will make a huge difference to overall content quality, with streamlined processes resulting in a high percentage of well tagged, standards-compliant and relevant content. There are other benefits too: including cost reductions from increased efficiency; and reduced maintenance and storage requirements. The big question for Records Managers, Web Content Managers, Librarians and other professionals is ‘How can I start to apply this framework and regain control of the information in my organization?’.

Content has always been difficult to control due to its diverse nature and it should be no surprise that it’s not going to get any easier. This article from the eDiscovery Journal raises some of the issues facing organizations in the Web 2.0 era. Not only is legislation being tightened around how information can be used and how it should be retained within organizations, but the number of ways that information can be created has increased dramatically. In addition to the content residing within Content Management Systems (CMS) and email servers, organizations now have to consider the new breed of collaboration and social networking tools that are growing rapidly within the workplace. User-generated content featured in instant Messaging, Blogs, Twitter, Google Wave, Buzz etc. all make it possible for information to exist in a wide variety of locations, yet still “owned” by the company. This type of information cannot be managed or controlled using traditional methods.

Failing to appreciate the need for governance introduces risk and is one of the reasons why enterprise organizations find themselves in a situation where they lose control of their content. There is often no real understanding of either the quantity or the value of information existing within the network. Misleading information can seriously damage a company’s brand and customer service, while duplication can result in increased storage and infrastructure costs. Ultimately, this lack of control leads to an increase in the so called “digital landfill” and the first thing to suffer is content quality and, in due course, the end user experience.

So, where do you start? The first stage of the ECoG governance model is “Initiate”. This really is the stage where you have to plan your strategy and think about the content you need – whose going to use it and when; what are they going to do with it – and also what you can live without. Retention of obsolete or irrelevant information is one of the biggest factors contributing to uncontrolled growth of content within organizations. The Initiate phase fits extremely well with the implementation of a CMS for the first time, or as a ‘take stock’ point ahead of migration into a replacement CMS, but it can also be undertaken on the back of a thorough analysis of existing content. This is the perfect opportunity to rationalize content and ensure quality and relevance are high before populating the CMS. A CMS will only manage content, it won’t deliver governance. For that you need a strategy and policies covering the end to end content lifecycle – ensuring that you not only obtain a high level of content quality, but maintain that level, in order to maximize the value of your information assets.

The boardroom is a busy place with every department competing for resource and time from the decision makers. But often, content is not discussed or not a priority for the board. However increasingly, these decision makers are on the hook for the content stored within their company, or that appears on their Web properties; whether or not anyone in the company created it or even knew about it.

The need for businesses to protect costs and competitive edge has never been greater. That’s why now is the time for organizations to control and structure their content properly across the enterprise and for the board to recognize the benefits for the business and its agenda.

Enterprise Content Governance (ECoG) is central to businesses optimizing their existing investment in enterprise content management systems, while reducing costs, improving corporate efficiency, ensuring compliance and reducing their carbon footprint. More specifically, ECoG addresses the following board-level issues:

• eDiscovery - Effective ECoG lowers the risk of being unprepared, and ensures that access to electronic content doesn’t end up being extremely costly.

• Brand Governance – Brand compliance is hugely important for today’s globalized organizations to ensure their competitive messages are consistently communicated to key (and often geographically distributed) communities of interest.

• Reduced Storage – Burgeoning content and the constraints of compliance are inevitably going to have an impact on storage. And while the unit cost of storage is starting to decrease and technologies such as virtualization are coming to maturity, more work can be done to reduce the amount of storage a business uses. In the process of migrating over 100 organizations from one Content Management System to another, Vamosa has found that as much as 50% of an organization’s content is typically redundant. Remove this content, and 50% of a company’s server farm can be freed up, offering a huge saving on operating costs.

• Corporate efficiency – And there are more significant, farther-reaching benefits to be had from effective ECoG. ‘Collaborative working’ and ‘knowledge management’ may be industry buzzwords, but the concepts they represent should be taken seriously by every organization. The ability for a company to capture, share, organize, find and use its knowledge efficiently has a direct impact on its ability to be productive, competitive and ultimately, profitable – yet not all organizations are properly equipped to do this.

To be able to control and structure content properly across the organization – i.e., to achieve effective Enterprise Content Governance – organizations need to improve their content quality. The board needs to understand this importance and put proper resource into achieving effective ECoG. To learn about the five significant steps in the process, download the whitepaper here.

Content Migration is complex; it is not simply a case of ‘lifting and shifting’ content from one content management system (CMS) to another. Web content is often inconsistently structured and spread across multiple locations and sites.

With this in mind, there is a growing requirement for content to be analyzed, enhanced and standardized prior to migration. The cost involved in manually reviewing and migrating content can be significant; but it can be minimized through the use of software to perform automatic analysis and migration – a solution recently provided by Vamosa for the Department of Health and Ageing of Australian Government (DoHA).

DoHA needed to migrate from their legacy CMS to IBM WCM within just eight weeks in order to achieve better control of their internet sites. Vamosa recommended a solution that involved an automatic cleanup and enhancement of their content. This process firstly involved identifying all of the content that was required to be migrated.

Using Vamosa Content Analyzer Vamosa Expert Services gained a clear understanding of DoHA’s content inventories and content management activities. The results showed that DoHA had 40 static websites containing 50,000 ‘must have’ pages that were to be migrated.

Vamosa Content Migrator then extracted all of the required content, copying it into the staging repository while allowing business to continue as normal for all DoHA’s employees. The next stage of the process involved exposing all of the content to Vamosa’s rules engine, Vamosa Content Quality Builder, allowing all of the content to be modified both for business requirements and to satisfy the requirements of the target system. The content was then loaded into the target system already ‘fit for purpose’ and ready for productive use.

Vamosa Content Migrator was used to simply, automatically and quickly migrate the required web content and linked documents to IBM Lotus WCM in the stated timescales. The Vamosa toolset in the migration process, compared with the manual alternative, lead to the project being completed

    * Four times faster
    * At a quarter of the price
    * With zero impact on day to day operations

Research shows that 85% of acquisitions are a failure in the eyes of the acquirer and one of the most common reasons: a lack of post-acquisition planning.

Buying another company and truly integrating it into your business is an operational challenge. Acquirers need a precise view of the shape and size of the integration plan and the more detail you can articulate then the quicker those acquisition benefits can be realized for your shareholders.

Many integration issues have been addressed in copious lines of print: sales channels, commission structures, accounting systems, headcount strategy, reporting structures, contracts, tax rates, surplus assets, IT Systems – the list is endless. However there is a new area emerging that is dangerously invisible to the Board – Digital Content integration. The world’s digital content is doubling every year and the lack of Governance applied to enterprise content is having a serious business impact on corporations worldwide including: expensive e-discovery audits, executives searching for, but not finding content, inability to migrate and merge content, duplication of content, conflict or breaches of corporate standards, or even a complete lack of standards altogether.

All of these issues are only compounded within the pressure cooker environment of a merger.

We have listed below the top big 8 issues we come across in our work at Vamosa:

1. Content acquired ruins your consistent messaging and corporate identity.
2. New logos are placed all over the new web properties you acquired.
3. Numerous competing Content Management Systems (related to systems that perform the same tasks) results in inefficiencies such as high operating costs.
4. A significant (could be as high as 60%) amount of duplicate content keeps the cost of content ownership high.
5. Content needs to be reassigned as organizational structures change above it.
6. Portal integration should follow quickly after the targeted company has been acquired. However integrating unfamiliar content into an existing portal can stunt integration.
7. Ownership of an Enterprise Content Governance framework is essential to give leadership to content authors.
8. Staff morale can drop rapidly within an acquired company if basic content retrieval, intranet usability and the quality of web sites deteriorates.

In future editions of this blog series we will explore some practical, in-depth solutions. As a taster – here are the headline solutions:

Issue	Solution
Branding of properties	The role of Vamosa Consulting Practise and Vamosa ECoG Suite for Web
Systems Consolidation	Vamosa's ECoG Suite for Web and interaction with Vamosa's Consulting Practise
Redundant and Reassigned Content	Using Vamosa ECoG Suite for Web to eliminate waste
Portal Integration	The deployment of Tagging technologies and how they integrate with Vamosa ECoG Suite for Web
Governance Frameworks	How to implement Enterprise Content Governance (ECoG) to extract real value from your content

To learn more about how to overcome these M&A challenges and how to ensure brand governance is maintained visit the Vamosa M&A page.

In Part 1 of this series, we highlighted the hidden challenges of merging digital content in the context of an acquisition. Acquired content often undercuts unsuspecting organizations by delivering blows across a range of exposed areas: from the content itself, to the technology on which it is served, to its audience – whether employees or customers. In this issue, we explore some of the solutions Vamosa provides to help organizations overcome these integration challenges and achieve their acquisition objectives.

Branding of Acquired Properties

The most obvious way in which acquired content negatively impacts an organization is by eroding its corporate identity. This is most apparent in the case of branding assets: logos, color palettes, and font choices, but many more signals of incomplete integration lurk below the surface. These signals may be acute but unobtrusive – contact email addresses pointing to pre-acquisition domains, obsolete product names – or subtly pervasive – material at sharply different reading levels, non-compliance with adopted accessibility and web standards. Through a combination of services and technology, Vamosa allows organizations to close the brand gap and ensure brand governance standards are adhered to. Taking advantage of Vamosa’s policy-driven rules engine, our Consultancy practice can design and configure a tailored package of content policies using Vamosa's ECoG Suite for Web, precisely targeting an organization’s most pressing content issues.

System Consolidation

It’s easy for companies to make a connection between public content and sales, but the burden of supporting post-acquisition content has deep implications for costs as well. While there are clear – and important – differences between content management systems, all are designed to facilitate the flow of information in a collaborative environment. That’s fine as a concept using one CMS but when you have multiple Content Management Systems – be careful, it can actual restrict collaboration. Reducing the number of content management systems required by the combined organization benefits both production and consumption; at a business level, this translates into elimination of sources of waste: licensing fees, hardware, lines of application code. Vamosa’s ECoG Suite for Web – with or without the deployment of our Consulting practice – allows organizations to accurately size their potential savings through systems consolidation, and then achieve them through migration into a unified platform. When decommissioning systems is not an option, Vamosa’s ECoG Suite for Web can apply metadata dimensions to content in place, enabling portal integration to make content findable or push it directly to relevant consumers.

Users of Content – Enabling Access

Lastly, acquisitions yield major challenges for the users of content. In the context of restructuring a company, it’s common for content ownership to change as departments are split and merged, and much of the content itself – internal HR documents, mission statements, functional group sites – is likely to become redundant or irrelevant. At an access level, reorganization manifests itself in changes to security groups. People often focus on security’s role in preventing information from getting into the wrong hands, but it’s just as important to ensure that new employees are quickly granted access to company information; neglecting this basic privilege is likely to precipitate a morale nosedive. Vamosa’s family of products and services allow business to quickly identify and eliminate swaths of redundant content while at the same time updating links to point to their corresponding active pages. Additionally, Vamosa’s ability to reassign content to new owners or groups ensures that information is editable by and available to the proper channels, breaking down barriers to collaboration and empowering an organization to be greater than the sum of its parts.








To learn more about CMS consolidation and CMS Migration, down the Content Migration: Seven Steps to Success White Paper.

While sitting with a customer recently I feared I was sounding like a broken record.  I wrestled over should I let this topic go that did not sit right with me?  As a supplier to this important customer, was it my duty to agree to a requirement that I knew would result in business resistance or should I highlight the consequences of implementing the perceived solution?

With resources readily available, through the internet, it is more common to come across customers who have already ‘self-diagnosed’ what they require from you even before any engagement has taken place.  With over 11 million hits coming back on the internet when you enter “content migration” into Google, the logic as to why this is such a popular search term for 2010 is apparent: the trend demonstrates that customers needs to find out more about content migration before approaching a CMS vendor and prior to selecting the best practice migration approach in order to ensure the best solution is delivered. ‘Surely’ – they tell themselves – ‘I can apply the same logic to selecting the best migration vendor as I would to (say) purchasing a car or house?’

Here lies the challenge for both the customer and the vendor; self diagnosis can be dangerous for both the success of your project and the future health of your web content; as the challenge of migrating content is a complex one.

I believe what sets Vamosa apart is how seriously we take our responsibility to perform a relevant and credible diagnosis for all customers.  All symptoms are identified before we progress to designing a solution.  During this diagnosis we discuss the consequences of such decisions and allow the customer to see potential negative effects for their end customer and also the impact this might have upon the acceptance of their new portal environment.

For this particular client, the self-diagnosed solution was to manually clean up 90% of their content post migration. However, the recommended solution was to clean up this content through an automated approach prior to the migration, helping to save both time and money.  The result for me was helping a customer with surfacing critical issues prior to the migration.  Finding the correct parameters to resolve these issues helped them to achieve a successful project. This is the way I have established long lasting relationships with all Vamosa customers during my seven years at Vamosa. Trust and understanding are key to a successful project.

Download the Content Migration: Seven Steps to Success White Paper to further understand the business benefits of taking a planned approach to content migrations.

We like a challenge at Vamosa, so when a major pharmaceutical company contacted us recently to discuss migrating their entire Intranet portal we were immediately interested. This was an ‘all or nothing’ situation for the customer, as both an internal project team and the CMS vendors themselves had already tried and failed to migrate the sites.

These previous failures didn’t scare us off however and actually made us keener to prove to the customer that Vamosa software and Expert Services consultants could actually achieve what they were beginning to think was impossible.

Being confident in our abilities, we agreed to deliver a two week proof of concept to demonstrate that we could move content, digital assets, metadata, portal navigation, portal structure, portlet placement and security (i.e. everything!) from the existing source system to a new target. The content, currently stored within Interwoven TeamSite with a WebLogic Portal front end, was moving to a new Oracle Publisher CMS with WebCenter Interaction as the portal front end.

The PoC was difficult, as we were pushing the boundaries of what was previously considered part of a content migration and literally creating an entire portal – with content and structure – automatically from scratch. So, a difficult two weeks, but ultimately very successful, leading to some gasps of amazement from the internal technical team when we ran through the whole process over a WebEx meeting. Needless to say, we won the piece of work for the full Intranet migration.

And then the next challenge: because so much time had been spent trying to figure it out before Vamosa became involved, there was very little time left to actually migrate the Intranet portal before the proposed go live date! Luckily we have years of experience in delivering content migrations to very strict deadlines, so were able to plan an approach with the customer and successfully execute the migration of 18 large sites on schedule and with a content freeze measured in hours rather than days.

This type of migration, very complex and with tight timescales, is only possible using the power and flexibility of Vamosa Content Migrator. Other migration frameworks can’t cope with this level of complexity and are restricted to moving only the CMS content and normally in quite an inefficient way. Content Migrator uses the core APIs of the target web portal and CMS and as a result achieves high performance through a reliable and secure interface provided by the portal and CMS vendors.

So, the moral of the story is: don’t be scared of a challenge, confront it head on with the right team and nothing is impossible!







Download the 'Content Migration: Seven Steps to Success' White Paper to further understand the steps required to achieve a successful migration project.