When migrating to a web content management system, it’s not just about transferring the texts. The real challenge (and work) is in migrating relationships, links, images, documents, versions and setting the right metadata. Regardless of whether the source of the migration is Hippo or another CMS.
In addition, the structure of each Hippo environment is different and often has customer or project-specific content types and functionality. Xillio's Hippo connector combines our knowledge of Hippo with our migration expertise and is easily configured to deal with these challenges and differences. Thanks to this connector, the focus is on improving and cleaning up content and not on the technical challenges.
In recent years, Xillio has migrated dozens of leading public websites migrated to and from Hippo, including for the Dutch government, railways and police departments. During this particular project, for example, 13 different ministry sites were migrated from nine different content management systems.
With the help of the Hippo connector the Dutch government was able to migrate in phases, and even was able to continuously synchronize a number of content repositories.
Hippo import connector
Our import connector uses a two-stage approach. In the first step, the structure is created in which all folders and Hippo handles are created so that the new Hippo IDs are known. In addition, the handles are updated with the actual content, assets and metadata, and the internal relationships are reconstructed.
Hippo export connector
Xillio's export connector uses the XML export feature built into Hippo. The extracted .xml files are automatically transformed into Xillio's Unified Data Model, from where it can be easily imported into any other CMS.
Click for more technical information about the Hippo connector.
Fill out the form and we will contact you as soon as possible.