Content Migration News & Articles

The notions of web and enterprise content governance are gaining more and more attention -- partially, due to growing concerns around eDiscovery and other compliance challenges. Everyone has some sort of content (and its volumes are growing at the speed of light), but do you have standards, policies and procedures around it? How do you enforce them?

The challenge many organizations face is compliance (or lack of it) with internal and external policies and regulatory standards. This is exactly the challenge Vamosa (news, site) is trying to address with its new product called Check & Fix.

Competition in the Web CMS market is cutthroat. Not a single weakness goes unnoticed. Not a single slip goes unattacked. But it’s just business as usual, right? We all seize opportunities, especially in tight times.

FatWire (news, site) is no exception. Demonstrating as much, the web content management vendor has launched a "rescue program" for Interwoven and Vignette customers who are apparently plagued by their recent acquisitions by Autonomy and Open Text respectively.

What is FatWire offering as bait? Free licenses and "proven migration tools" valid until the end of September. Should you consider?

Armedia's (news, site) new Content I/O Suite ties three software components together to create an integrated content collection, migration and delivery solution, one that the company thinks will take clients handily over a number of common enterprise content management hurdles.

Announcing the Google Blog Converters project! 

Tired of Blogger? Want to move to WordPress? Or vice versa? Problem solved! Google's new Open Source project enables you to easily move blog posts and comments from service to service. 

There is probably no worse strategy for an intranet or public website than content migration. It is doomed to failure from the very start.

If you have ever seen “content migration” go from being a single line in a project plan to being a never-ending saga of tedious database scripting and failed migration attempts, then take heed: there is a tool available.

It often seems that the primary purpose of localization is to create unreadable English that is cheap to translate into unreadable German.

Best practices and advice that focus on the implementation of a content management system are numerous — much of this body of knowledge is focused on tool selection and the technical implementation. What is often overlooked — or at least under appreciated — is the work that needs to go in to migrating content from legacy sources, into the new system.

Whether you are migrating content from an existing CMS, a file structure or a blog, there are a number of things you need to think about, plan for and decide upon. In this article we’ve collected some thoughts and guidance from a few people who know a thing or two about content migrations.

Not all vendors out there believe that you should be able to move back and forth between Lotus Notes and SharePoint. AvePoint, provider of SharePoint infrastructure and administration management solutions, continually brings to market migration tools to move content from another product to SharePoint. Their latest migration tool is the DocAve Lotus Notes Migrator.

Your team has gone through the initial discovery analysis and you have selected your new web content management system. All is going well as you kick off the planning until someone on your team asks, “What about the content migration?”

You look to your agency and they just shake their heads, your guys from IT are staring back at you wide-eyed and your CMS vendor stutters back in response, “Uh..uh..uh well, that’s usually the customer’s responsibility.”

Paul Trotter, CEO of Author-it Software Corp., is a man who knows what he is talking about. If you don’t believe me, just take a look at his bank balance.

He just published a White Paper on the implementation challenges presented by Content Management Systems as a whole. It ought to be required reading for boardroom-types, IT managers, webmasters — just about anyone whose job entails management of digital content.

But for those just waking up to the fact that they need a CMS, and are fretting over the issues involved in getting it up and running, you might want to take a look.

It is universally known that a content management system is only useful when it has content to manage. Unfortunately, the problem of how to migrate content either into a new CMS or from one CMS to another is rarely considered ahead of time and is far from trivial.

This is the third and final article in our series on migrating content from a previous version of Vignette to Vignette V7. The first article in the series painted the broad overview and in the last article we talked in detail about the Content Analysis part of the process. Now, we continue by digging into the final planning phase: Defining the Migration Approach.

When we left off from part one in this series, we mentioned that there are four steps involved in the content life cycle migration process — analyzing the content, deciding on a migration approach, the actual migration and post-migration processing. Here in part two, we go into detail on the Content Analysis step.

Vignette revamped its Web Content Management technology with version V7 to adopt industry standards J2EE, XML and Web Services. While this move helped customers lower total cost of ownership by leveraging open standards and application server services, it posed new challenges in migrating existing sites running on earlier versions V5/V6.

V7 introduced an entirely new architecture, making V6 implementations almost obsolete. Customers going for the V7 platform have to model, design and rebuild the site.

Along with re-engineering the site, one of the most critical tasks in V7 migration is to rebuild the content into new V7 server from an old story server. As re-creating the whole site content is quite a tedious task, customers might wonder if there is any way out.