Your team has gone through the initial discovery analysis and you have selected your new web content management system. All is going well as you kick off the planning until someone on your team asks, “What about the content migration?”
You look to your agency and they just shake their heads, your guys from IT are staring back at you wide-eyed and your CMS vendor stutters back in response, “Uh..uh..uh well, that’s usually the customer’s responsibility.”
Obviously this is an exaggeration, but content migrations are often the dirty little secret that folks in the CMS world like to avoid. It’s hard, it’s messy and very few organizations do it well.
Truth be told, the content migration can often be the hardest part of implementing a new CMS. As a rule of thumb, you can estimate 20 to 60 minutes per page to make it happen. You can easily expect to cut that time in half if you use dedicated migration tools and reduce it much further still by working with a firm that specializes in web content migrations.
Here’s a list of things to consider if you need to price out your own web content migration project.
Develop a Detailed Content Inventory
A well planned content migration must begin with a content inventory. This isn’t a simple site map, or cursory glance at your file structure. This is a detailed listing of all of your site’s content, and the unique relationships that exist between the content. It identifies things such as the URLs, doctype (HTML, PDF, Image etc.), links to and from each piece of content, template identification & mapping, orphaned files, stale files (rarely accessed according to analytics), and potential meta data. Expect to spend several weeks on this if you are migrating a large web site.
Know the Systems Path Required to Migrate Content
Migrating content often requires logging into, and moving between several systems. This can include the source web server, the new CMS, the authoring tool of choice, the task tracking application, the VPN software and more. It all adds up and must be done for each piece of content.
Clean Your Content Prior to Migration
More often then not, legacy content must be cleaned before it can be imported into a new content management system. Frequently this can be automated, but even then a person is usually required to manually edit the content to make sure that the formatting is correct in the new system. This is one of the most time consuming steps in a migration.
Create Redirects to Avoid Breaking Bookmarks or Embedded Links
Often in a migration into a new content management system the URLs will change to reflect a new directory structure. When this occurs, any bookmarks to the old site that users might have, or any links embedded in online and offline advertisements will break. To resolve this, a 301 redirect will have to be created that points every old URL to the corresponding content asset in the new system.