At any point in time, there is a college IT director trying to determine whether to upgrade, migrate away from, or stay the course with some software package that the faculty and students rely on to meet their instructional needs. A campus may have outgrown the basic CMS, and the Enterprise version is now needed to bring system performance back to an acceptable level. The CMS provider may have changed code base, requiring major staff retraining to follow the migration path. Costs could be up, service could be down, and new third party tools may not easily integrate. Yet even faced with all of these potential reasons to change, making the decision to do so is never easy. User communities hate change, hate training, and hate repurposing earlier content to work in a new environment.
By Stephen R. Acker, The Ohio State University, and Peter E. Murray, OhioLINK; republished here from the Campus Technology SmartClassroom Newsletter under rights retained by the authors.