A web content migration is a complex process, whether it involves a migration between Adobe Experience Manager, formerly known as Adobe CQ, or any other CMS system. Transferring a web page or the HTML is just the tip of the iceberg. Often, content migration requires a structure adjustment, content improvement, or metadata enrichment. The real complexity is located underwater: the conversion of the structures, content types, versions, values, value lists, and reconstructing relationships, links to other pages, files, and images.
During content migration, CMS data models are often constructed differently from one another; at times, several content types can be consolidated or eliminated altogether. Each CMS has its own implementation of pages or component-based content types.
Xillio has performed hundreds of WCM migrations, and as a result gained a wealth of knowledge that Xillio was able to leverage to create a robust Adobe Experience Manager connector, which is currently in use in migration service projects.
You will probably acknowledge that a website migration does not happen for no reason, there are always strong overarching reasons to start such a migration process, because it’s clear that it’s quite complex.
Using a detailed step-by-step plan, this white paper gives you guidance on how to successfully complete a migration of a web content management system.
In this video we demonstrate a web content migration from Drupal to Adobe Experience Manager using Xillio's Unified Data Model.
Fill out the form and we will contact you shortly