Digital landscape: Ziggo

The outcome

In April 2014 Ziggo went live with a full new and responsive website. All content was migrated, rewritten and provided with the right metadata. Quite an achievement, which significantly improved the user experience. The project was a huge success due to a close collaboration in a multidisciplinary team and an excellent exchange of knowledge. Ziggo is a happy customer. Something we are very proud of.

Old situation

Ziggo used an outdated content management system (CMS), which was managed by their own technical team. This CMS was cluttered, slow and responsible for a long page load time. It was not only challenging to develop new functionalities, even simple adjustments were very time-consuming. As a result of which Ziggo was not able to quickly respond to changes in the market.

Project objectives

A better user experience with:

  • A new responsive design
  • A stable platform and a new CMS
  • The possibility to make quick technical changes
  • Several improvements in technology and SEO content

“Ziggo is a happy customer. Something we are proud of”





Satisfied customer


In the autumn of 2013, Ziggo started together with UnitID, Enrise, Mobiquity en Xebia to create a CMS that met the requirements of Ziggo. Our employees joined in January 2014 to migrate all content.


Consistent implementation

During a migration it is important that a new CMS remains uncluttered and clean. Clear terms of collaboration about publishing content are important, particularly if multiple people work in a CMS.

In this project it was occasionally quite a challenge, because many components and functions required various content entry processes. Our content managers trained the employees who joined the migration to quickly familiarise them with the system.


The migration

Migrating the content was an important part of the project. A total of more than five hunderd pages were moved to the new CMS (Hippo).

During the migration, the developers and the content team worked in close collaboration. As soon as the developers delivered new functionalities the team was ready to work on it. The content team consisted of two senior content managers from Crossphase, a web editor and several content experts from Ziggo.

Within the project our employees had multiple tasks:

  • Monitoring the planning
  • Ensuring a consistent implementation
  • Testing of new functionalities


This migration was heavily dependent on the subcontractors of the development team. It increased the risk of a rapidly increasing workload and chaos. And consequently, this would impact the lead time and costs. With a careful planning and flexible anticipation, all went well.

The project was divided in two parts: Customer Service and Products.

  • Customer Service
  • These pages were already optimised by us and Ziggo in the summer of 2013. Being a follow-up project, it was relatively quick and easy to migrate the content.

  • Products
  • This part was not yet compatible with the new design. First the channel managers investigated all content. Then the content team adjusted the content for the new design. Thanks to an automated process it ran smoothly.

We published the content using a scrum wall. Thanks to the close collaboration with the channel managers and the agile approach all product pages were uploaded and published smoothly and efficiently.