When it’s OK to rename objects
Summary
Renaming standard Salesforce objects is acceptable when the new name resonates better with users, remains close to the original meaning, and does not require extensive field renaming or loss of standard functionality. For example, nonprofits may rename "Account" to "Household/Organization" or "Opportunity" to "Deal" to improve clarity. However, drastic renaming, like turning "Opportunity" into "Tickets" and renaming all related fields, is discouraged unless use cases are exclusively narrow. The key is balancing user understanding with preserving Salesforce's inherent object behavior.
Takeaways
- Rename objects only if the new name is clearer to users.
- Keep the new name close to the original object’s purpose.
- Avoid renaming standard fields extensively after renaming objects.
- Ensure standard Salesforce features remain usable after renaming.
- Be cautious when renaming objects for niche uses like ticket sales.
A while back, I wrote an email called you really don’t want to rename standard objects . Recently, a reader asked, “When is it OK to rename an object?” The short answer is, when The new name is better understood by the user It’s not completely different from the original name Almost none of the object’s fields need to be renamed You can still leverage standard functionality (like Account Hierarchy or Opportunity Products) For example, in the nonprofit industry, we deal with organizations and households. The word “account” is not as popular. So renaming “Account” to “Household/Organization” is OK (even though it’s a little long). Similarly, I’ve seen “Opportunity” renamed to “Deal”, “Gifts”, or “Donations”. What you don’t want to do is rename “Opportunity” to “Tickets”, and then rename all the standard fields to ticket-related fields. However, if all you will ever do is sell tickets and nothing else that could use Opportunity, then maybe. But a big maybe.