In the old days, moving to Drupal often meant converting static pages or templates to Drupal nodes. Today, it is rare that we get to build a site from scratch. Reality is that most major Drupal projects are now migrations from other content management systems.
Taking on such a migration is not a trivial decision for an organization. There is a great deal of complexity in the reasons for migrating, but the decision is often not understood well amongst the various stakeholders.
This session is not a workshop about why to choose Drupal. Rather, I will discuss what to expect after the decision is made and techniques for managing the change given the various reasons you may have for doing so.
This session is geared toward project managers and managers dealing with significant risk associated with migration from a legacy CMS platform to Drupal.
Questions answered by this session
How to set realistic expectations with stakeholders?
How to document an appropriate risk analysis and mitigation strategy in regards to a migration to Drupal?
You got "attitude" from legacy CMS users? Strategies on how to best deal with them.