Working closely with our clients to meet their company business goals by effectively implementing system deliverables, we find Forensic Analysis to be the keystone, as a first step to the discovery process.
This is an ideal approach in getting to know our clients’ needs and obtaining insight into their Salesforce org, as well as understanding and efficiently mapping the future state.
We tackle Forensic Analysis as a team, comprised of experienced Salesforce developers and administrators, resulting in the assessment of current state using both, admin and dev tools and techniques.
The goal is to get to know the customer org really well, and to discover the obvious and uncover the unforeseen: issues with functionality, code, security gaps, etc. It is important to understand org architecture, main processes, and the extent of existing customization.
Below we describe Starpoint's approach to Salesforce Forensic Analysis and helpful tools and techniques that we employ.
The first step in our Forensic Analysis process is a general org overview. The objective is to explore the org as the users see it through the user interface and to uncover possible issues and inefficiencies.
Client Org - Classic or Lightning?
If Classic is the case, recommend switching to Lightning. No client should be left behind!
Client Users and Licences
Establish if the licensing needs of our client are adequately met and whether there is room for optimization with the unused or underused licenses and Salesforce capabilities.
Ask Client for a Demo Walkthrough
It is very helpful to actually see the various client workflows, performed by a number of business areas using Salesforce.
Other Helpful Findings
What are the packages installed? What apps do users use and how? Is there room for improvement in how users interact with Salesforce?
We strive for a deep understanding of our client business processes and find room for improvement and optimization, making the Salesforce workflow smoother and users more productive. During the forensic analysis process, we like to include looking at the org limits and data volume. If data volume in some objects is massive and underused, maybe it should be archived in an external system.
Technical Org Assessment
During technical org assessment, our team generally utilizes both, native Salesforce tools and external solutions to assess the org from the technical side. This allows us to get a very granular view into security, opportunity for technical optimization, release readiness, Lightning readiness, etc.
Some of the most useful tools are listed below:
Helpful tool to assess the security of the org according to best practices. Provides a list of technical vulnerabilities in the org and ways to fix them.
Noteworthy tool to review data volume, analyze field and record type usage, and to generally explore the org faster from the technical aspect.
If you overlooked the opportunity for optimization during the org review, Optimizer is here to help you out! A great native Salesforce tool that provides a technical PDF report outlining recommended actions and estimated development implementation timelines, making the org run as smoothly and efficiently as possible.
A helpful AppExchange paid tool that you can use to get a variety of reports about your org. The diversity of information you can get from these reports is staggering. It provides detailed description of permissions, roles, field usage, profiles and so much more, in a convenient form of Excel spreadsheets.
Lightning Transition Assistant
If the org is still in Classic, we will recommend transitioning to Lightning. This tool provides all the necessary action steps that facilitate a smooth transition, including estimated time and effort assessment. A developer effort may be needed to fix some of the issues outlined in the final report.
Native Salesforce tool that allows to explore objects in the org and the connections between them in an easy and visually friendly way.
What are the issues to be addressed and remedied prior to the next release? This tool provides a list of critical Salesforce updates and actions to take to ensure a smooth transition into a new release. Other tools and solutions may be used depending on a future project objective, time constraints and org architecture.
This is a task for a Salesforce developer, who will review the codebase and external tools, as well as provide feedback on ways in which the process may be optimized and improved.
Since most organizations frequently use many tools to address various system needs, those tools should be interconnected and integrated, so that information flows smoothly between the services and platforms, where needed. Salesforce is frequently integrated with other applications that the client organization utilizes, and it is important to review those integrations to get a thorough understanding of how the Salesforce org is connected to other software solutions.
Salesforce developer will look at the current state, review classes, triggers, processes and flows to assess the extent of customizations and code quality. Developer will primarily focus on those crucial parts of the codebase that directly impact effort and timelines for subsequent stages of the project.
Analysis Results Compilation
The final step is to assemble all results of our Forensic Analysis into a convenient and business coherent structure of an Excel spreadsheet. Clients will be able to easily review the document, ask questions and implement suggested Salesforce org enhancements. The detailed document is the definite proof that the Consulting partner has a deep understanding of the org and is ready to start the next phase of the project. It provides our client with a bird’s eye view of their org with detailed overview of its architecture and common processes.
Forensic Analysis is a solid start for a strong partnership between a client and Consulting partner, establishing mutual trust and deep understanding of current state analysis and future state recommendations.