Thanks Ken! Quite helpful.
In your reply you say: "Site migration to 2.2.10 did bring across users and courses ...".
By "site migration" do you mean upgrading your entire 1.9.10+ site directly to 2.2.10?
Or... installing a "clean" 2.2.10 site. And then restoring those 1.9.10 courses one at a time on the new 2.2.10 server?
(I have a hunch you mean the latter.)
Distinguishing between "upgrading" and "migrating" may be important.
Collin and Emma seem to be describing a two-stage "upgrade" process for moving courses (users, & user data) from 1.9.x into 2.4, by way of 2.2.x.
(Apologies if I got that wrong because we write and read in different dialects.)
I think you're recommending "site migration" as a preferred way to move intact Moodle 1.9.x courses (Incl. enrollments I student data) into Moodle 2.3/.4/.5.
Been there. Done that aleady... from 1.9.x>2.1.x. It worked! But only migrating "master" course copies; without students or their data aboard.
We haven't yet tried it with courses containing students and their data. Easy enough to try and find out. (Learning by Dewey-ing.)
Related question:
What's that "special" restore to move courses out of Legacy status?
Is it documented somewhere in MoodleDocs?
Those troublesome "legacy files" are a bridge we've already crossed. We export those after the 19>2.x migration and store everything in a file system repository that's made available to our facilitators. Not perfect. But working for us.
Thanks for sharing!
Dr. BobBl