Skip to content
Mergiva logoMergiva AI logo: two interlocking triangles with data spokes, and the words Mergiva AI

One controlled process for moving a regulated company’s data

Everything is organised around the deal, not around folders: in Mergiva, every file, decision and signature belongs to one deal, and each is recorded in a tamper-evident audit trail.

Book a pilot call

Wave 3 of the deal

Clinical archive

Integration stage
SharePoint OnlineAmazon S3
batch_record_BR-2231.pdfTMF_index_site-07.csv

Checked on arrival

1,268 / 1,320

  • protocol_amend_04.pdf
  • labeling_EU_v12.pdf
  • deviation_log_2025.xlsx
E-signedFirst signer
E-signedSecond signer
Illustration with sample data. Product screenshots coming soon.

Seven stages, one record for the whole deal.

Every stage writes to the same record, so nothing is lost between tools or teams.

  1. 1Connect

    Access details stored encrypted.

  2. 2Discover

    Every file listed and fingerprinted.

  3. 3Classify

    Pharma categories, sensitivity 1 to 5, personal data protected.

  4. 4Approve

    Two e-signatures from two different people.

  5. 5Transfer

    Resumes after any interruption.

  6. 6Verify

    Checked again on arrival.

  7. 7Evidence

    Audit trail and compliance report.

Explore the product.

One acquisition, stage by stage.

The seven stages repeat for every batch of files. Around them sits the deal itself, which decides what is allowed at each point.

  1. Before signing

    See the estate before you plan anything

    A deal starts in the Pre-deal stage, where the work is discovery: no wave can start yet. Register the seller’s systems, run a Data Estate Scan, and every file is recorded with its size, type, date and digital fingerprint.

    AI classification then places each file in your taxonomy and scores its sensitivity, and the Data Estate Report turns the scan into a PDF. One signature moves the deal into Diligence, and discovery continues.

  2. Between signing and closing

    The antitrust gate holds

    Entering Sign to close takes two signatures: the deal lead or corporate-development lead, and antitrust counsel. From here discovery continues, but nothing moves to the acquirer.

    This is enforced, not requested: the system checks the deal stage before every transfer and refuses if the stage does not allow it or cannot be confirmed.

  3. Day 1

    The deal closes, with two signatures

    Two signatures move the deal to Day 1: the deal lead or corporate-development lead, and the IMO lead. Clean-team access ends automatically, and each ending is recorded in the audit trail. Integration follows, and with it the first waves.

  4. Integration and the services agreement

    Waves carry the estate across

    Wave migrations begin in Integration and continue while the services agreement runs. Each wave is planned, signed by two different people, transferred, then checked on arrival.

    If a file does not match, the wave stops and a steward decides what happens next, with a written reason. A wave that completes is closed with its compliance report.

  5. Closing

    Archive, and keep the proof

    Closing takes two signatures: the IMO lead, and the CIO or an administrator. No new wave can start after that. The deal is then archived, and its audit trail can still be re-checked entry by entry.

Start with one deal.

A pilot starts with the two systems you need to connect, and ends with evidence you can hand to an inspector.

Book a pilot callHow a pilot works
  1. 1

    Name the pair

    Tell us the two systems you need to connect. We produce that pair’s evidence before the pilot starts.

  2. 2

    Scan the seller’s data

    We scan one source in your own cloud. You get a report of what it holds, sorted and rated for sensitivity.

  3. 3

    Plan validation together

    We work through the validation pack with your quality team, on your systems.

  4. 4

    Run the first wave

    Two approvals, a checked transfer and a compliance report you can hand to an inspector.

Or write to contact@mergiva-ai.com.