Boldo Logo

IT M&A: get due diligence out of the black box

In many deals, IT stays a blind spot: partial information, poorly understood dependencies, TSAs that are hard to scope and synergies that are still hypothetical. What was not mapped before signing gets paid for after. Boldo turns the available data into a documented IT scope, from due diligence to post-merger integration.

  • Risks discovered after closing

    Technical debt, vendor lock-in, obsolescence or non-compliance: these risks can drive up integration costs, reduce expected synergies or shift the deal's priorities.

  • TSAs that are hard to exit

    Without a precise inventory of the services, systems and responsibilities covered, exiting Transition Services Agreements becomes hard to plan and secure.

  • Synergies that are still hypothetical

    Compare portfolios, contracts and covered capabilities to assess overlaps and rationalisation opportunities on a documented scope.

From IT due diligence to integration, one shared working base

The data gathered before signing should not vanish into a report. It can become the foundation for the carve-out, the TSAs and post-merger integration.

  1. IT due diligence: structure the available information

    Take the inventories, contract matrices and extracts available in the data room, then complete them through interviews: applications, infrastructure, flows, contracts, data and teams.

    Document the risks, the source of each piece of information, its validation status and, where needed, its confidence level. The deal team can then tell established facts from assumptions that still need confirming.

  2. Signing: document the scope of the TSAs

    Identify the services the seller will keep operating, the beneficiary entities, the systems involved, the responsibilities, the costs and the deadlines.

    TSAs are negotiated from an explicit scope, tied to the applications and dependencies actually covered.

  3. Carve-out: define what needs to be separated

    Identify the applications, data, flows, contracts, access and teams that follow the divested entity. Pinpoint what needs to be transferred, duplicated, replaced, stopped or rebuilt.

    The IT landscape map provides a common base for preparing the separation.

  4. Post-merger integration: decide and execute

    Compare the application portfolios, the covered capabilities and the existing contracts. Document what needs to be kept, merged, migrated or decommissioned.

    The same knowledge then supports the migration projects and the tracking of the synergies decided.

Confidentiality
Screenshot of the Boldo interface displaying an application architecture diagram with grouped and connected applications

Access tailored to the deal's confidentiality

A deal involves participants who should not all access the same information: deal team, clean team, target management, external advisors or operational teams.

Roles and access domains make it possible to restrict who can view and edit data according to each participant's scope. They support the organisation defined by the deal team and its advisors.

  • Limit each participant to the information they need
  • Separate contexts into distinct organisations
  • Frame the contributions of internal and external teams
  • Keep a history of every change and its author

The consultants working on the deal can contribute to the same repository with tailored rights.

Turn uncertainty into visible information

In due diligence, not all data carries the same level of reliability. Some comes from a validated inventory, some from an interview, an assumption or an outdated document.

Boldo lets you add to each asset or relationship the properties your method requires: source, owner, verification date, validation status or confidence level.

Open questions no longer stay scattered across notes. They remain tied to the applications, contracts and dependencies they concern.

  • Tell established facts from assumptions
  • Trace the source of each piece of information
  • Assign the points still to confirm
  • Filter data by validation status
Confidence level
Boldo screenshot of a cyber risk analysis linking VPN, IAM Entra ID and Phished to threats affecting CRM Sales and Team Sales, with a Salesforce detail panel
TSA steering
Boldo screenshot of the application portfolio with TSA decision columns and mapped business capabilities

TSAs steered toward a documented exit

You can model each service covered by a TSA, then attach the entities involved, a deadline, a cost, an owner and the systems that depend on it.

Also document the target exit date, the prerequisites, the replacement system and the dependencies that still block the entity's autonomy.

  • Tie each service to the applications and data involved
  • Identify the provider entity and the beneficiary entity
  • Track the prerequisites needed for the exit
  • Spot the dependencies that extend the TSA
  • Share an up-to-date view with the integration committee

After closing, the same base can support integration steering by the CIO.

One repository for the deal's main workstreams

The same knowledge can be used according to the phase of the deal and the question at hand.

  • Due diligence01 / 04

    IT risks and assumptions

    Tie risks, available information and confidence levels to the assets concerned to surface the points to dig into before signing.

  • Carve-out02 / 04

    Separation scope

    Isolate the applications, flows, data, contracts and access to transfer, duplicate, stop or rebuild in order to make the entity autonomous.

  • TSA03 / 04

    Transition services

    Document the services maintained by the seller, the dependencies covered, the costs, the deadlines and the conditions required for their termination.

  • Integration04 / 04

    Portfolios and synergies

    Compare the assets of both entities to analyse overlaps, complementarities, required migrations and rationalisation opportunities.

Start from the information actually available

The data room rarely provides a complete, directly usable view of the IT landscape. Boldo lets you take the structured data, then complete it progressively during the deal.

  • Files

    CSV / XLSX import

    Take the available inventories, contract matrices or extracts, map the columns to properties and relationships, then preview the changes before validation.

  • Programmable

    REST API v1

    Build the synchronisations you need when certain sources must keep feeding the repository during the carve-out or the integration.

  • Contribution

    Interviews and workshops

    Complete the information through your exchanges with the target's management and teams. Every change stays logged and attributed to its author.

Separate contexts for each deal

Each organisation has its own metamodel, data, users and access rights. Boldo is hosted in France with Scaleway.

From 39 € per editor per month, with a free 14-day trial.

See pricing

Frequently asked questions about IT due diligence and carve-outs

Yes. Boldo can be used from due diligence onward to structure the available information, document the risks and prepare the integration or separation scenarios.

Roles and access domains make it possible to frame viewing and contribution according to the organisation defined for the deal.

Secure the IT side of your next deal

A due diligence to structure, a carve-out to prepare or TSAs to steer: see how to turn the available information into a documented IT scope.

Write to us

30 minutes focused on your deal and its IT stakes.

By submitting this form, you agree to our Privacy Policy.