If you have a website migration, there is more to it than moving content from point A to point B. Some of what needs to be moved isn't content, the process continues after you get to point B, and even getting the migration complete will happen in stages.

1. Beyond Point B
Website migration isn’t just moving
content from point A to point B
@jdavidhobbs
Originally presented to J. Boye CMS Expert Group // 7 May 2012

2. Common View: Conveyor Belt
A B
@jdavidhobbs http://hobbsontech.com 2

3. Of course, also chance to toss content
@jdavidhobbs http://hobbsontech.com 3

4. But it’s not just about tools
@jdavidhobbs http://hobbsontech.com 4

5. Content Migration: Automation
http://bit.ly/migauto
@jdavidhobbs http://hobbsontech.com 5

6. Content Handling Process
http://bit.ly/contenthandling
@jdavidhobbs http://hobbsontech.com 6

7. And it’s not just about content
@jdavidhobbs http://hobbsontech.com 7

8. Website migration ≠ content migration
@jdavidhobbs http://hobbsontech.com 8

9. What other than content is in a
website migration?
A website migration is the transfer of content,
sites/sections, functionality, team, templates,
information architecture, and relationships from
one platform to another – Website Migration
Handbook v2
@jdavidhobbs http://hobbsontech.com 9

10. Why important
• Even for content migration, bad decisions in
other areas can make the content migration
harder.
• In the end, the whole website needs to be
transformed – if the content gets moved
perfectly but the surrounding structure isn’t.
• Sometimes a lot of new content needs to be
created (so not just about moving content).
@jdavidhobbs http://hobbsontech.com 10

11. Each website transformation is
different!
Find out where you
are on this distance
/ complexity graph.
http://migrationhandbook.com
/self-evaluation/
@jdavidhobbs http://hobbsontech.com 11

12. Quality is usually taken as given
@jdavidhobbs http://hobbsontech.com 12

13. Quality discussion should happen early
• When conceiving the project
• When estimating total effort level
• In as early testing as possible (as end-to-end
as possible)
• When defining QA process
• After pilot and each phase
@jdavidhobbs http://hobbsontech.com 13

14. Large transformations are not big bang
@jdavidhobbs http://hobbsontech.com 14

15. Why not big bang
• Set expectation for ongoing improvements
• Group similar sites
• Early real testing
@jdavidhobbs http://hobbsontech.com 15

16. Things often go downhill immediately
@jdavidhobbs http://hobbsontech.com 16

17. How to stop degrade
• Focus on the important requirements
• Design systems for long term success
• Product manage
• Phase
See “Better Engagement for Ongoing Website
Improvements” http://bit.ly/engagerep
@jdavidhobbs http://hobbsontech.com 17

18. All aspects should be planned
(less surprises)
@jdavidhobbs http://hobbsontech.com 18

19. What needs to be included in planning
• Depth
• Distance
• Weight
• Phases
See Deep Digital
Strategy: A Brief Intro
@jdavidhobbs http://hobbsontech.com 19

20. Thanks!
New offering: Five Steps Program
http://hobbsontech.com/five-steps-program
@jdavidhobbs http://hobbsontech.com 20