Site Migration

Drupal

KU uses a Drupal-based content management system (CMS) to provide site administrators/editors with an easy to use and consistent backend user experience, which allows them in turn to produce consistent and high-quality end-user experiences across university sites.

Who is This For?

The community of KU CMS site administrators/editors is comprised of individuals from a wide variety of roles and areas of expertise – and from a wide range of experience and comfort working with websites and web content. This site migration process information was created to support site administrators/editors at all levels.

Some of this information will be review for some of you. But, no matter your experience level or area of expertise, we hope you will review the material and take on board any new concepts and strategies that you find helpful.

Looking at Your Content with Fresh Eyes

Because the KU CMS is moving from one version of Drupal to another, it is not possible to simply copy an existing site and recreate it in KU CMS – Sunflower. All KU CMS sites will need to be migrated manually.

Additionally, the way content is created and displayed in KU CMS – Sunflower will require you to thoroughly examine and rethink your current site and its content (e.g., writing, layout, organization).

We encourage you to see this as an opportunity to look at your website holistically and use the site migration process as a tool to improve and refine your site from the ground up.

Site Migration Plan

There is no one size fits all approach to site creation/migration. The information in the Site Migration Plan below - and in the left menu - is intended to be a starting point to help you create or refine a process that meets your KU CMS website project’s specific needs.

Site Migration Plan Steps

Next Up - Site Migration Timelines