CMS Implementations Deck

I told a story about this in "Migration” might be the most dangerous word in CMS

Short version: A client hired us to perform a migration. After the project started – in single chilling moment – it became apparent that they expected us to build their new website as part of “the migration.” That was not good day.

I promise you it will take longer and cost more than you expect.

I wrote an entire white paper around migration: The Web Migration Handbook (PDF).

My friend David Hobbs has written a whole book about migration (the name is very similar; David had it first, for the record): Website Migration Handbook

Also, we tell the story of a hypothetical migration in a chapter in The Web Project Guide.

The instant someone says that they want to do something with the website, start your inventory then. You do not need to know what the new CMS is going to be, because analyzing your content in your existing CMS is independent of where it goes. You know it’s going to go somewhere, right?

I found a tweet that really resonated around this topic:

Don’t spend 6 minutes doing something by hand when you can spend 6 hours failing to automate it.