i'm working in another one of those now..as a framework start with analysis of those fields and scripts across the environment. trim the fat there make the client happy with the low hanging fruit being removed. then start to unpack the scripts by form and function. 9/10 environments, they are mimicking a native function or behavior. only look at deployed within the last 90 days to even think about keeping. anything older would require upkeep, meaning someone would be available to provide you context. when it's time to stand up the native features holler at me!

The easy ones are the Single Action Workflows™. Someone was trigger happy creating several WF that only hide some button, lock the transaction or set a field as mandatory. The validation ones are more tricky, lots of conditions to untangle. Think If department = A and subsidiary = B but User Role is not C, but the moon is full today, etc.

you must have some serious latency in that environment. are you starting from scratch or has there been previous endeavors to untangle?