@BrianChambers We did a phased out approach. Our University is made up (or was at the time) of 6 colleges. We picked 3 colleges and they moved from Moodle to Canvas in Fall semester, during this time both systems were provisioned and ultimately could be used. Faculty were allowed to move early but had to get special permission to not move and we had about 75% actually make the move in the Fall. The Spring we moved the other 3 colleges. The Moodle server was run for 1 more year but no classes or users were provisioned so people could access their data but not use it to instruct from. After that we set Moodle up with a different URL and essentially locked out the users. By request, someone could be given a unique URL to access their content or we would go in for them and pull the content (normally much easier and faster) and we allowed this for 1 year (this is year 2 after full Canvas adoption). After that point, we turned the Moodle server off. We have a data retention policy of 5 years for this type of data so the server could still be turned back on and our IT staff can access content. For the first 3 or so semesters that it was off we would get about 1 request a semester for data but then everyone moved on successfully.
We did lots of communication and even used wording to make it sound like it would be very difficult to get any data after that first year. We held trainings and open sessions to help people backup and move data to Canvas and created several sandboxes for people to store Moodle data in Canvas just in case they may need it.
Hope this helps!
Nick
