A Comprehensive Approach to Inherited Salesforce Orgs
On a recent, fascinating conversation on the Ad Victoriam Salesforce Simplified podcast, our Technical Architect Jitin Chatlani shared his expertise on taking over an existing Salesforce® org. Drawing from his wealth of experience, Jitin outlined critical insights that every administrator should consider when stepping into a new Salesforce environment. Below, we’ve curated some valuable audio clips from that illuminating discussion.
First-Week Approach When Taking Over An Existing Salesforce Org
We kicked off our conversation with Jitin by asking for his recommended first-week approach when taking over an existing Salesforce org. He walked us through how he assesses and prioritizes what needs attention first.
Incomplete or Outdated Documentation
Documentation is often incomplete or outdated in inherited Salesforce orgs. We asked Jitin about key areas admins should focus on first, and what tools or methods he recommends for this process.
Technical Debt in Inherited Salesforce Orgs
At this point in our conversation, Jitin talked about how he evaluates which customizations or configurations should be kept, updated, or removed entirely.
Looking at Security in an Inherited Org
Security and sharing settings can be complex to untangle in an inherited Salesforce org for admins. We were curious about Jitin’s systematic approach to auditing and validating existing security configurations in an inherited org.
There was much more to our conversation with Jitin about inheriting a Salesforce org. Listen to the full Salesforce Simplified episode here.
Related Resources:
How to Keep Your Salesforce Org Secure and Up-To-Date
Set Up Your Salesforce Org for Integration with MuleSoft
Subscribe to the AdVic Salesforce Blog on Feedly:
