Platform players like Amazon have proved that operating an ecosystem of products and services (developed in-house and aggregated from partners) gives strong leverage for rapid expansion. So many smaller players are also looking for ways to grow through strategic partnership deals and acquisitions. <\/p>\n\n\n\n
Yet, signing the buying deal is just part of the M&A process. The real work begins afterward. You then need to achieve synergy between your business and its new arm in terms of operational alignment, service\/product portfolio standardization, and IT integration. <\/p>\n\n\n\n
Since many businesses are digital in their core, more times than not a significant bulk of effort goes into technology merger integration.<\/p>\n\n\n\n
- Why IT Plays a Focal Role in Post-Merger Integration (PMI)<\/a><\/li>
- How to Approach IT Integration in M&A: 6 Best Practices<\/a>
- 1. Perform Pre-Integration Planning<\/a><\/li>
- 2. Plan the Scope for a Test Run <\/a><\/li>
- 3. Migrate and Assess <\/a><\/li>
- 4. Train Your Teams<\/a><\/li>
- 5. Document the Best Practices <\/a><\/li>
- 6. Verify Compliance and Security <\/a><\/li><\/ul><\/li>
- To Conclude <\/a><\/li><\/ul><\/div><\/div>\n\n\n\n
Why IT Plays a Focal Role in Post-Merger Integration (PMI)<\/h2>\n\n\n\n
According to Bain & Co<\/a>, over 50% of business synergies are technology-enabled, meaning the acquire seeks to profit from the technology the acquired company has developed. Data from Accenture<\/a> mirrors this sentiment: among the recent high-value transactions, 80% of companies placed a significant emphasis on technology.<\/p>\n\n\n\n
However, many leaders tend to underestimate the importance of IT integration in mergers and acquisitions. <\/p>\n\n\n\n
Only 56% of decision-makers took IT issues into consideration during the due diligence phase. <\/p>Deloitte<\/a><\/cite><\/blockquote>\n\n\n\n
This is a major oversight because the costs and complexities of IT integration in M&A can stall operational plans and dramatically increase the timeline of the project. <\/p>\n\n\n\n
For example, a bank acquiring a payment company may overlook the fact that their legacy core systems are not technologically compatible with modular, microservices architecture<\/a>, used by the acquired payment app. Post-M&A, this would leave the IT team under pressure to re-architect the existing systems, build new data integration, and otherwise technologically reconcile the two different products. Also, if you lack in-house expertise for such projects, this would create further chaos and delays. <\/p>\n\n\n\n
In some cases, you can opt for \u201cquick patches\u201d to harmonize disparate technical systems. But the underlying integration problems won\u2019t fully disappear and accumulate as technical debt <\/a>instead. <\/p>\n\n\n\n
As Ba<\/a>in cautions, the lack of preliminary planning for process, systems, and data integrations magnifies the post-merger integration costs. <\/p>\n\n\n\n
![\"Costs](\"https:\/\/www.edvantis.com\/wp-content\/uploads\/2022\/02\/Worst-performances-experience.svg\")
<\/figure>\n\n\n\nSource: <\/em>Bain \u2014 Mastering Process and Systems Integration After a Merger<\/em><\/a><\/p>\n\n\n\n
Therefore, the earlier you involve the IT teams in the M&A process \u2014 the sooner you\u2019ll complete subsequent transformations and start profiting from the acquired solutions. <\/p>\n\n\n\n
How to Approach IT Integration in M&A: 6 Best Practices<\/h2>\n\n\n\n
M&A is a step-by-step activity. At every stage of the deal, you need to complete a set of tasks to move on to the next stage. The same systematic thinking should be applied towards IT integrations. <\/p>\n\n\n\n
The main jobs-to-be-done at for successful technology merger integration include: <\/p>\n\n\n\n
- Technical systems merger and integration issues resolution <\/li>
- Data integrations and data migration (where necessary) <\/li>
- IT processes homogenization and optimization (to reduce overlaps) <\/li>
- Technical portfolio rationalization \u2014 to remove redundant apps\/vendors <\/li>
- Processes and tools harmonization to improve team collaboration <\/li>
- Identification of the next steps for improvement <\/li><\/ol>\n\n\n\n
Finally, you have to pull off the above post-acquisition integration plan without disrupting your core operations. That\u2019s a major task, especially if your in-house IT teams already have their hands full with other operational priorities or lack knowledge of the newly-acquired systems. <\/p>\n\n\n\n
In such cases, many leaders choose to partner with external integration consultants \u2014 a team that could step in to cross off the above tasks and develop a repeatable model for post-M&A integrations. That\u2019s what we often do at Edvantis<\/a>. <\/p>\n\n\n\n
To better show how it\u2019s worth approaching, we\u2019ll use a sample project of integrating work environments for two teams as a point of reference, executed with our post-acquisition integration framework. <\/p>\n\n\n\n
1. Perform Pre-Integration Planning<\/h3>\n\n\n\n
IT people can help you estimate the scope (and associated costs and timelines) of work required to fully integrate your systems with those of a target company. Specifically, they can:<\/p>\n\n\n\n
- Advice on the likely post-acquisition integration issues that can spike costs and open up certain risks. <\/li>
- Suggest application consolidation and changes in IT procurement for both organizations to streamline operations. <\/li>
- Propose different IT integration approaches \u2014 co-existence, absorption, or a hybrid version of operating two IT landscapes. <\/li><\/ul>\n\n\n\n
All of the above should happen at the pre-planning stage \u2014 a \u201cheadspace\u201d when you strategize how the joint IT landscape should look and function. <\/p>\n\n\n\n
At this stage, we recommend to: <\/p>\n\n\n\n
- Conduct an inventory of tech systems at both ends. <\/strong>Map overlaps and gaps\/differences between your technology assets and processes. Identify candidates for consolidation. <\/li>
- Define system dependencies and limitations. <\/strong>For example, if one of your systems requires 99%\/month uptime by contract, think about how you\u2019ll maintain this SLA during the integration phase. <\/li>
- Analyze different migration and integration options. <\/strong><\/strong>Your goal is to determine what costs are associated with different approaches. For example, whether you should perform full-scale data migration from the target company systems or just build API-based integrations to enable data exchanges. <\/li>
- Develop reference project architecture<\/strong>. <\/strong>Verify that all prerequisites for integration in terms of feasibility are met. Create references for new systems, workflows, and data repositories. <\/li><\/ul>\n\n\n\n
At the end of this stage, you should have the following outputs: <\/p>\n\n\n\n
- Overview of source and target systems with supporting documentation <\/li>
- List of technical limitations, risks, and caveats<\/li>
- Stakeholder management plan for execution <\/li>
- The first test migration candidate <\/li>
- Full-data migration and\/or Delta migration plans <\/li>
- Full integration\/migration roadmap with key milestones <\/li><\/ul>\n\n\n\n
2. Plan the Scope for a Test Run <\/h3>\n\n\n\n
Technology merger integration is rarely done in one go because of the risks to business continuity. It\u2019s more of an iterative process where you progressively migrate and align different elements of the IT portfolios. <\/p>\n\n\n\n
Therefore, we suggest starting with a \u201ctest candidate\u201d first \u2014 a system that will serve as a reference for all subsequent candidates. This allows you to create an effective and repeatable model for carrying out post-M&A migrations with a high degree of confidence.<\/p>\n\n\n\n
For the purpose of this post, we came up with a quick study. Let\u2019s say a company just acquired a new tech subsidiary and wants to rapidly integrate the target company\u2019s IT teams into their work environment. <\/p>\n\n\n\n
To do that, the company needs to: <\/p>\n\n\n\n
- Migrate and consolidate work environments such as JIRA, Confluence, IDEs. <\/li>
- Migrate and consolidate data from other business apps such as Track, JIRA Server, Notion, Azure DevOps. <\/li><\/ul>\n\n\n\n
All of the above should happen without interruptions to the parent company workflows. One way to do so is to use the \u201cfollow the sun model\u201d. <\/em>In this case, your IT integration services provider can perform migration (with planned downtimes) during off-work hours without interfering with the core team(s) work. <\/p>\n\n\n\n
Then the IT integration process will go like this: <\/p>\n\n\n\n
- Test run<\/strong>: We create test target instances and set up the new environments. Define the main outputs and validate the data outputs against the objective. Then migrate data and merge workflows, task branches, etc. <\/li>
- Transition period plan: <\/strong><\/strong>At the same time, we also set up a backup plan to ensure easy roll-back in case of any issues. We test all the new environments and collect feedback from the teams. <\/li>
- Post-migration period plan: <\/strong><\/strong>We create a timeline for performing QA work<\/a> and user acceptance testing (UAT). Then suggest the follow-up steps for shutting down the mitigated source system(s) at the target company. <\/li><\/ul>\n\n\n\n
3. Migrate and Assess <\/h3>\n\n\n\n
In the course of any sort of data migration and integration you should look for: <\/p>\n\n\n\n
- Data inconsistencies <\/li>
- Blockers and gaps in business logics <\/li>
- Functionality and workflow overlaps (if you are integrating two different systems)<\/li>
- Opportunities for business processes consolidation <\/li>
- Good-to-have customizations and extensions your teams may need <\/li><\/ul>\n\n\n\n
Remember: once the short-term integration work is complete you can direct your IT teams to work on core business projects, while the integration consultants continue migrating the other candidates and work on extra customizations and maintenance tasks. <\/p>\n\n\n\n
4. Train Your Teams<\/h3>\n\n\n\n
In many cases, the target company may have had different processes than you did. This means that not everyone will be up-to-speed on the standard workflows you have now implemented.<\/p>\n\n\n\n
Going back to our example, the target company relied on a different software development life cycle (SDLC)<\/a> and wasn\u2019t using Scrum as heavily as the parent company. As part of our integration services we helped them with team training and onboarding:<\/p>\n\n\n\n
- Developed supporting documentation and how-tos in Confluence <\/li>
- Consulted on Scrum process implementation and delivered training <\/li>
- Added extra reporting functionality and helped configure data processing for reporting <\/li><\/ul>\n\n\n\n
These extra steps smoothened the transition process and reduced the dependency on in-house IT teams, whose efforts were focused on the core work. <\/p>\n\n\n\n
5. Document the Best Practices <\/h3>\n\n\n\n
Repeatability is the main ingredient of successful IT integration in M&A. Document your approach to reduce the implementation timeline for the next migration candidates and subsequent M&A deals.<\/p>\n\n\n\n
The benefits of creating detailed IT integration documentation include: <\/p>\n\n\n\n
- Subsequent ease of PMI <\/li>
- Cost containment <\/li>
- Business continuity <\/li>
- Minimum management involvement required<\/li>
- Easy monitoring<\/li><\/ul>\n\n\n\n
As a technology PMI partner for one company, we\u2019ve managed to complete five large-scale migration and integration projects over the past years by having comprehensive checklists and documentation.<\/p>\n\n\n\n
6. Verify Compliance and Security <\/h3>\n\n\n\n
Most post-merger integrations involve the migration of critical data assets from the target company to the acquirers. This can result in cybersecurity vulnerabilities and compliance gaps if left unmonitored. The last thing any company wants is to gain publicity for their data breach just after a successful M&A deal. <\/p>\n\n\n\n
Hence, during the QA and UAT stages, we always recommend doing a meticulous compliance and security audit. The goal here is to ensure that all newly consolidated systems tick all the compliance boxes relevant to your industry. Then evaluate the most critical systems and newly-built data integrations from the security perspective. <\/p>\n\n\n\n
To Conclude <\/h2>\n\n\n\n
As the old adage goes: \u201cPlan your work and work your plan.\u201d<\/em> IT integration in mergers and acquisitions requires fastidious preparation at the pre-execution stage. You should have a clear understanding of how you plan to homogenize the different tech elements across the two companies and secure the talent you need to perform the transformations. <\/p>\n\n\n\n
If you lack the capacity to perform the integrations, while also performing your core business, consider an IT outsourcing partnership<\/a>. Quality IT talent is hard to find, while PMI often requires a wide range of skills, you may struggle to hire for.<\/p>\n\n\n\n
- Transition period plan: <\/strong><\/strong>At the same time, we also set up a backup plan to ensure easy roll-back in case of any issues. We test all the new environments and collect feedback from the teams. <\/li>
- Test run<\/strong>: We create test target instances and set up the new environments. Define the main outputs and validate the data outputs against the objective. Then migrate data and merge workflows, task branches, etc. <\/li>
- Define system dependencies and limitations. <\/strong>For example, if one of your systems requires 99%\/month uptime by contract, think about how you\u2019ll maintain this SLA during the integration phase. <\/li>
- Conduct an inventory of tech systems at both ends. <\/strong>Map overlaps and gaps\/differences between your technology assets and processes. Identify candidates for consolidation. <\/li>
- 2. Plan the Scope for a Test Run <\/a><\/li>
- How to Approach IT Integration in M&A: 6 Best Practices<\/a>