Post-M&A Integration for a Global Financial Organization

case study snippet

Services:

Industry:

Financial Services

Location:

Canada

Client since:

2015

Business Challenge

шсщт Difficulty integrating wealth management software systems

Difficulty integrating wealth management software systems

Our client had to extract all client and employee data from the acquired financial organization and place it on the client’s technology stack. Since the data on the acquired company side changes daily, an ongoing scheduled migration pipeline had to be applied. For clean integration and a seamless tech transition, they engaged the Sombra team to deal with the wealth management branch, as they also needed to merge the data on investment funds native to both financial organizations.

Share your business challenge

And we deliver on time and on budget

Meet an expert

Agreed on sharing responsibilities with the Client

The Sombra team suggested a dedicated development team for the Client. This engagement model implies that both parties are sharing responsibilities as follows:

Client

  • Establishes and manages priorities.
  • Defines and drives milestones for the project.
  • Increases or decreases the project scope during our cooperation.

Sombra

  • Manages the development team to achieve defined goals.
  • Keeps the Client informed about team progress through recurrent syncs.

Solution

Since the client had a tight deadline of three months for this particular integration, as well as other non-functional requirements in terms of security, scalability, and reliability, we’ve applied the following solutions:

  1. Given that the file processing took nearly 5 minutes and the existing tech stack based on Java and Spring, we decided to encapsulate business logic in Spring Cloud Task, which also provides out-of-box features like built-in monitoring, scalability, and error handling.
  2. To handle comprehensive task scheduling, we used the Quartz framework.
  3. An in-house SFTP solution met the security and regulation requirements for in and out file transfers.
  4. AWS S3 was added as a data and logs alternative destination to meet the availability and observability requirements.
  5. Several levels of testing proved the reliability of the solution:
    • Smoke testing
    • Regression testing
    • Integration testing
    • Boundary value data testing

Tech stack:

Dev: Java, Spring Boot, Spring Cloud Task, Quartz, MSSQL Server

QA: qTest, Postman

Discover the most promising technological trends that will dominate the market in the next decade

Read more

Business Value

Thanks to the efforts of our team, the Client has achieved 30% of expected synergies in 6 months after the closing ahead of the targeted number of 25%. On an annualized basis, run-rate savings will equal 55% of the stated target. Such a track record flourishes the Client’s growth and increases confidence during the following acquisitions.

Get the latest tech insights delivered to your inbox!

Stay ahead in the tech world—hit subscribe now.

    Thank You for Subscribing!