A friend wrote:
I’m neck-deep in planning for a migration to Salesforce, which has exposed some fascinating differences in philosophy. Salesforce is, in principle, infinitely customizable, which leads to this dispute: leaving intact the system’s core data structure (based on B2B), or gutting Salesforce’s data structure to power the simplicity of future usage.
How should you approach structuring a new Salesforce instance? If, for example, your company doesn’t think in terms of leads, opportunities, and accounts, would you use those as the default objects or would you use something custom? On the one hand, a custom CRM architecture feels both simpler and better, but on the other hand you’d end up losing a fair amount of any CRM’s interoperability, extensability, and, likely, outside expertise.