IT integration after an acquisition
Two technology estates brought together after an acquisition — mapped, decided and sequenced, with assurance through the work.
Project type
Mergers and acquisitions — IT integration
Practice
IT strategy
Where it reached
- People
- Process
- Information
- Technology
Where they started
An acquisition left the combined business with two of everything: applications, infrastructure, contracts and data.
What we did
- Inventory. Mapped both estates — applications, infrastructure, contracts and data.
- Decisions. Decided which systems survived, which were retired and which were merged.
- Integration plan. Sequenced the integration: identity and email first, then the core systems.
- Assurance. Provided assurance as the integration was carried out.
What changed
A combined business moving onto one set of systems, with the retirements decided and the order of work set — rather than two estates running side by side indefinitely.
Want a result like this?
Bring the situation you are in. We will tell you where we would start, and whether it is worth doing now.