If you use a Content Management System (CMS) to manage web or document content you will already know that one of the key issues faced is how to move existing content into the new system.
On paper content migration looks relatively easy. A team of people could spend the next six months copying files and web pages from their existing location into the new CMS.
However, this is not such a simple proposition - content migration projects tend to involve hundreds of minor changes to very large volumes of content.
There is an important distinction between Enterprise Content Governance and Enterprise Content Management.
By acting as centralized repositories of an enterprise's content, ECM systems are enormously valuable for content storage and management. And they're often touted as the cure-all for enterprise content woes. But ECM systems support the content publishing process, not the process of providing structure and control. More....
Having purchased your new Content Management System (CMS) you are working towards a successful implementation that supports your organization's overall strategy. You define new roles and workflow, create new standards for document deployment, web page design and development and release this to your user community for live operation.
To support this, your content lifecycle defines the creation, authoring, approval, retirement, archiving and deletion processes for new content.
However, existing web content or document stores were not created in this way - they exist outside this new content lifecycle. Data migration of existing content into a CMS requires significant metadata enhancement to comply with the new content lifecycle. More....
What are the Key Document Migration Issues?
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. More....
![]()