I read the article and then thought "Hey, I just worked on a project just like that." So here are some of my thoughts in response to James' white paper.
1. Planning: You can never do enough of this. And part of the planning phase needs to include Stakeholder agreement and support. Tell the VPs and Directors of departments you need X number of content managers for X amount of time, BEFORE you start the project. It sets expectations on the resources needed for the project. Create a Content Owner Agreement, stating if this department wishes to have a presence on the intranet this is what they are required to do.
2. Automated Migration: The Automated migration sounds great but can be completely disastrous if you have not completed proper pilot for the migration. Do not choose a small site in which to run the pilot. And if you have more than one source of content. Most big companies that do not have good intranets. Content can be found on both the CMS and front page homegrown sites making the automation process impossible. So you may have to come up with a few strategies for each type of content.
Content Migration can be a life safer for some companies, finally have one place to find information, saving time doing endless searches and having your new CMS system work better with your existing tools. But you need to be prepared before taking on a project of this magnitude. Plan Carefully.