Legacy MVC metadata cleanup?

Question

What do best practices say about cleaning up legacy custom metadata? 
 I noticed the OOTHB core of my Sugar v14 upgrade (in TST) still has a metadata folder under each module. 
 I still have code in custom/modules/*/metadata/. for just about every module I customized anything on in my days on Sugar v6.x, and I am seriously tempted to just delete every one of those metadata directories under custom since I believe that every module has long since been moved to sidecar. 
 My philosophy is: the less legacy code I carry around the better... 
 Any caveats or counter-indications? 
 Thank you! FrancescaS

Francesca Shiekh · Accepted Answer

Hi Francesca Shiekh , Happy new year!! 
 I was discussing this with engineering and got few suggestions for you: 
 
 Much of what is in that folder is BWC-related, and not relevant to Sidecar modules. However not all of it is. 
 
 As one example, dependencydef.php applies to Sidecar as well, and deleting that will affect SugarLogic rules for the module: https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_13.3/a[&hellip;]tecture/sugar_logic/dependency_actions/setpanelvisibility/

You can move those metadata folders out of sugar working directory. and do QRR, and test out, then wait couple of months before permanently delete those folders. 
 Sugar has moved away from BWC over the years but few things are still there as legacy code
 
 For example, few pieces of administration panel or rarely used views 
 If you use those "rarely used views", you'd want to keep that particular folder for that module

Note: Make sure you backup you Sugar folder before you delete anything and QRR just in case you'd need to revert them.