It would be useful to have an upgradeCheck command similar to one that exists for 2.4 to 2.6 upgrade just for documents. Having an automated way to perform the pre-requisite validations for an upgrade across major versions is a better end-user experience than going through the compatibility list to validate what will break. A few samples from compatibility list that can be incorporated into the upgradeCheck are:

• Auth schema pre-requisite
• Collection name validation
• Platform support
• Background index check
• dropDups checks for any of the index
• SSL setting changes
• Replica-set oplog format check