How to Migrate Content to a New CMS (Content Management System)

The withdrawal of a content management system as well as moving to a new platform or CMS always require the (sometimes difficult) content migration process.

Content migration is the process of moving existing Web content to a new platform. The migration of content of each website is unique, depending on the amount of content that you take with you when you are sent from one platform to another, and a handful of other factors.1

1. Content Migration Tools

Each content migration process will most likely need both software / automated scripts and the manpower to do the job. common content migration tools are described below.

2. A project manager

A dedicated project manager makes all the difference to facilitate a smooth transition to a new CMS. A project manager will lead the work on track by breaking the entire content migration process into smaller phases and assign roles and responsibilities. They will also promote communication between all team members, including content publishers, content managers and IT.

3. Project Monitoring

Project monitoring is the process of mapping aspects and content migration phases. Examples include the registration of the inventory of your content and all stages of the migration of manual workflows (including editing and reviewing web pages). The tables of Excel are your best friend when it comes to screening project.

4. Automated Tools

You can buy software or create custom scripts that can take existing content from your CMS legacy and move it again. These content migration tools are ideal for large databases, documents and media libraries, etc.

5. Getting Started: Assessing your content

To facilitate content migration process, a solid foundation is to be laid. Everything starts with an understanding of your content and how it is processed.

6. Inventory

Take inventory of your content means understanding how content is managed by your CMS platform inheritance. This includes metadata, web page links, file types, etc. Before beginning any migration, it is recommended to create lists for each type of content on your site. Each list must include where / how it is stored and managed in your current configuration, and how it will be treated during the migration to the new platform.

The creation of each list can be done automatically, using software or developing a custom script.

7. Create a content strategy

This is where manual labor comes in. The next step is to take inventory of content and the creation of a strategy to move to your new platform.

This step includes to comb through and evaluating the content and the decision of what to take with you and what to leave behind. If the content is not required, it can be removed and excluded from the migration process.

Another aspect of your content strategy should describe how much cleaning and revision is required for migration. If the content of the technical requirements, such as custom coding, this should be hammered during this phase.

Moreover, this is the moment when you must decide whether the content migration will be performed in an automated process or manually.

Tip : the move towards a new CMS platform can affect your content and how it is handled and brought to your new site. For this step, the best idea is to familiarize yourself with your new CMS and understand how the platform handles everything, including aspects such as page titles, authors, etc.

8. Develop your metadata

The categorization and tagging of content becomes an important organizing tool during content migration process. You have to use a spreadsheet to track how the content relates to the other, through the various sections of the site and other variables using tags and categories.

The primary objective of mapping metadata is to make all of your content easy to search, sort and filter in the back-end and front-end.

9. Migration

After taking inventory of your content, creating a content strategy, as well as mapping metadata, it is time to migrate. If you choose the automatic option is a matter of script development, content migration, cleaning and then test everything.

For those who choose the manual migration, a workflow should be in place that breaks all the necessary steps to make a piece of existing content and turn it into a new piece of content on your new platform. The workflow must include measures such as metadata capture, page titles, etc.

Finally, we arrived at the stage of testing / examination of the contents of the migration process.It is important to ensure that your content looks good and is displayed correctly in all browsers and on the desktop, mobile and tablet.


Leave a Reply

Your email address will not be published. Required fields are marked *