VLE Guru

In my last post we had reached an impasse while migrating legacy content .  The tool claimed it had worked, but there was no evidence from the data that it had. In this post I share how I got on with Blackboard support and some other news from our SaaS Migration Project.

In this episode of the SaaS Migration Diaries, I share what happened when we tried running the Move Legacy Content to Content System migration tools for the first time on a development server.

After months of writing business cases, project plans, engaging with stakeholders, confirming budgets, and negotiating contracts we are on the road to SaaS. I thought it would be useful to blog along the way, hoping to both receive some help and advice from those already in the land of SaaS, and to help others who may take a similar path in the future. We have run our Blackboard environment locally for twenty years.  We are currently running a load balanced environment with 4 web nodes, 1 tasks node, an NFS server (~5 TB course content), and an Oracle Database (~1.5 TB in size).  With such a long use of Blackboard we have a lot of data and our environment had built up quite a tangled web of kludges and workarounds to ensure smooth operation for our 27,000+ strong user base. This first post is about migrating legacy content.