M&A Series: Risk Assessment and Mitigation Strategies
Summary
When integrating acquired company systems in Salesforce CPQ, it's crucial to address your own technical debt through manageable cleanup projects that align with the acquired processes. Streamlining data fields and workflows before migration prevents data conflicts and eases integration. Effective change management is equally important, requiring clear communication and thorough training for both new and existing users to ensure understanding of migrated data and updated processes, which helps maintain continuity and reduce employee churn.
Takeaways
- Address technical debt with small, focused cleanup projects before migration.
- Align cleanup efforts with best practices from the acquired company's processes.
- Perform data and process cleanup prior to system implementation to reduce overhead.
- Provide clear communication and training on new and migrated processes.
- Include all users in change management to maintain work continuity and reduce churn.
All right, so at this point in the process, you have come to understand the ins and outs of what systems, processes, and data you will be porting over. Now, there are two more things left to consider: Technical Debt in your own system and the impacts this will have on the migration Change Management and all of the fun that comes with that phrase Let’s start with tech debt. If you have been around my site for a while, you know I have had to do a few tech debt projects in my career. I think they are fun, but most people find them costly and time-consuming. They are generally one of the most complicated projects to put an ROI to, and thus, many companies like to postpone and postpone until literally at the point of breakage. However, acquiring a company, particularly one with good data and infrastructure, can be a point to reflect and decide to embark on your own tech debt journey.