Acquisitions are tricky, and StackPath’s business requires a dynamic model that can quickly merge two organizations without lost time or burnt capital. In the event of an acquisition, StackPath values speed and efficiency in merging the acquired company into their own. StackPath acquired Highwinds in 2017 in one of their biggest acquisitions to date. Both organizations had Salesforce as a CRM, which they needed merged and integrated into existing processes without any data loss or outages. This was further complicated by the fact that the Highwinds instance of Salesforce was outdated with long deprecated practices that added a layer in complexity to merging the two instances. So, not only did StackPath need to migrate all of the structure, data, and users from the acquired company’s Salesforce org into their own org, but they also needed to update the entire Highwinds process to do so. A large amount of metadata, data, and files all needed to be moved both efficiently and accurately to ensure data integrity all while updating new processes into modern supported Salesforce tools.
Our process when merging Salesforce instances is straightforward: Measure twice (or three times) and cut once.
By thoroughly informing ourselves on the situation beforehand, and doing our homework to fully understand the possible complications in merging their outdated Salesforce instance with to-date practices, we were able to migrate the entire legacy Salesforce org into the new one without complications. This process involved multiple working sessions with stakeholders and users to isolate key requirements, building a roadmap to ensure a smooth transition from the old org to the new, executing, and testing.
Testing of the new Salesforce org resulted in zero errors or needed changes, and Highwinds users were able to make a seamless transition into the StackPath environment without any lost data.