t44u 2015, content migration

Content MigrationRemoving the heartache, delays and

expenseRaewyn McKenna – Business Analyst

Defining Digital Engagement for Higher Education

TERMINALFOUR Confidential – t44u 2015

• The reality of Content Migrations

•Where do most of the problems lie?

•Manual or automated migration?

• Pre-migration preparation tasks

• 4 Pro Tips

• Demo of the TERMINALFOUR Migration solution

• Questions

CMS Migration Webinar agenda


• Even in the best of circumstances they are a big head ache

• Unless you intimately know your content adds a high level of risk to your project timelines.

• 100% automated content migrations are very rarely possible

• Additional risk where:• No existing CMS or database tool powering web content

• Developed by many developers over many years

• Developed using many tools over many years

• Exceptions in the code or design?

The reality of Content Migrations


• Team frustration – content migration is a very boring & stressful project activity

• Feels like a relentless activity

• A lot of activity to get you to where you are right now (presuming the content doesn’t need to be re-written)

• Budget overruns & project delays

Worst case scenarios


•Migrating a “page based” CMS into a more powerful CMS

•Website appears consistent but isn’t (at HTML code level)

•Moving to a new responsive design: Tables, Images etc.

• Content quality – is it worth migrating?

• Insufficient resources available to quality control content

•When migrating from HTML: URLs versus Breadcrumbs versus Sitemap are widely different

Where do most of the problems lie?


Types of migrations

Manual

• The amount of content to be migrated <1500 pages• Is content well structured & marked-up correctly?• Complexity of the original web site

AutoDB

• Is the content within a documented database?• If a commercial system, does your software license allow you to give access to the

database to a third party?• Able to import meta data, but cannot resolve links or import media (e.g. images and files)

AutoWebsite

• Is it coming from another CMS?• Is the HTML source consistent?• Are you able to and have the skills to easy add extra tags?


1. Manual or Automated? Purge?2. Analyse the Data

3. Configure the Migration Tool4. Run the Migration5. Test / QA6. Manual updates

Typical process

Automated Migration Steps Summarised


Migration check list

STEP 1 : Manual of

automated?

Inventory all sites and content to be

migrated (any surprises?)

Content quality?

Media files

STEP 2 : Analysis the data

How to determine the Site Structure?

What is the structure of the content (pages)?

STEP 3 : Configure the Migration Tool

Map the elements from

the existing pages to the new

content types

Do you need to merge “content

types”?


Migration check list

STEP 4 : Running the

Migration

Phases or “big bang”? Test runs?

Any large media files?

“Hidden” sections?

STEP 5 : Test/QA

What resources are available to help test?

In a new design: Images, Tables etc.

Two types of manual review are required: Content &

Migration quality

Define your QA methodology early

STEP 6 : Manual Update

Some manual updates required in order to fix issues

& exceptions


• Get started on the Content Migration activities as early as possible in your project

• To get a head start, using your existing CMS, work on re-writing (and deleting) content

• Set realistic expectations as to the level of risk and effort involved

• Use the content migration activity to purge defunct content

4 Pro Tips

Demonstration of TERMINALFOUR HTML

Migration Feature


• TERMINALFOUR provides two content migration features:• Database import (called Content Syncer)

• HTML import

• Out-of-the-box feature (not “scripts”)

• Today’s focus, HTML Import:• Can import any mark-up provided it’s relatively consistent

• Downloads site from web address

• Sites can be migrated in phases (detects when links need to be updated in previously imported content)

Overview

Questions?

t44u 2015, content migration

Technology