A clone of production is only as good/useful depending upon how one plans to use the clone. Strongly suggest setting the cloned site to 'nomail ever' just in case notifications/forums or something/anything involving email to users won't be sent inadvertently (confuses students/teachers).
Eventually, user accounts might expire in the clone, usage is not as much so data depicting events, etc. old etc.
So when it becomes not so useful, one will be cloning again.
So ... suggest cloning again ... this time with a unique/matching moodledata for the clone site. Good practice as if one tinkers a lot with plugins/etc the clone might become useless.
However, since it is a clone ... and a tinker toy ... the 'easiest fix' for the clone might be to simply clone the production moodledata directory to something unique for the clone to use (changing the clone config.php file to point to the new) - even though it might not match everything in it's moodledata/filedir/
That in itself will serve a purpose in that you will see what happens if migrating site and one didn't migrate moodledata ...
My 2 cents of course!
'SoS', Ken