Move an acquired data estate.Keep the proof.
For life-sciences M&A. Mergiva maps what the seller holds, moves it into your systems on the deal’s timeline, and gives your quality team proof that nothing was lost or changed. Two people approve every move, and every file is checked on arrival.
- Built for GxP
- Runs in your own cloud
- Every file checked on arrival
Works with the storage you already run. All 49 system-to-system combinations passed a live test on 26 September 2026.
- Amazon S3
- Azure Blob Storage
- Google Cloud Storage
- MinIO
- SFTP
- Local / NAS
- SharePoint Online
The data workstream sets the pace of the whole integration.
Deals close on time and still lose months after Day 1. In a regulated acquisition the data must arrive intact, stay behind the antitrust line until closing, and move before the seller’s support ends.
The deal’s clock
Running past the end of the seller’s support costs more. Every month the data workstream slips is a month of double running.
A hard deadline
After closing, the seller keeps the old systems running under a transitional services agreement, with a fixed end date, and extending it costs more. Every month the data workstream slips is a month of double running.
A regulated activity
Clinical, manufacturing and regulatory records stay valid only if their history travels with them. Lose it in the move and you face an inspection finding, not an IT ticket.
No system of record
The work is done with a patchwork of file movers, spreadsheets and consultants. When someone asks what moved, who approved it and whether it arrived intact, nothing can answer.
One record for the whole deal, from first scan to final proof.
Three steps. Every action lands in the same record, so nothing is lost between tools or teams.
Understand the estate
Know what the deal brings before anything moves.
- Connect the seller’s systems; access details are stored encrypted.
- List every file and take its digital fingerprint.
- Sort each file into your categories, such as clinical, manufacturing or personal data, and rate its sensitivity from 1 to 5.
Data Estate Scan
Source: SFTP| File | Fingerprint | Category | Sensitivity |
|---|---|---|---|
| CSR_0142_final.pdf | 9f3a…c1e7 | GxP-Clinical | 4 |
| patient_listing_v3.xlsx | 2be0…7d19 | Health data | 5 |
| batch_record_BR-2231.pdf | 4b08…d2aa | GxP-Manufacturing | 4 |
| HSR_filing_notes.docx | 61c4…09fe | Legal-Antitrust | 5 |
| FY25_forecast.xlsx | c3d7…5a20 | Financial | 3 |
| site_photos.zip | 8e19…b3c4 | Other | 1 |
Control every move
No wave starts without two signatures and the right deal stage.
- Nothing moves before the deal allows it.
- Two people approve every wave, each logging in again to sign.
- The person who set up a wave cannot approve it.
Deal stage
- Pre-deal
- Diligence
- Sign to close
- Day 1
- Integration
- TSA
- Closed
Antitrust gate. Before Integration, the system refuses to start a wave.
Wave 3 approval
Approved- First signerFresh login · meaning recorded
- Second signerFresh login · meaning recorded
The wave’s creator cannot be one of the two signers.
Move it, and prove it
Every file is checked on arrival, and the audit trail records the result.
- Large transfers resume where they stopped after any interruption.
- Every file is checked again once it arrives.
- Every step is written to a tamper-evident audit trail.
Audit trail
Intact- 80Wave approved7e2d…b41c
- 81Wave startedlinked ✓ · a90f…22e8
- 82File checkedlinked ✓ · 3f9a…c1e7
- 83Wave completedlinked ✓ · d415…7b02
Each entry is linked to the one before it, so any later change shows. Entries cannot be edited or deleted.
Ordinary migration tools copy files. Regulated deals need four more things.
Mergiva addresses all five, in one record per deal.
- Record integrity (GxP)
- Metadata, audit trail and chain of custody must survive the move, or the record loses its standing with regulators.
- Personal and health data
- Access is restricted and logged, and a breach is reportable. The data has to be classified before it is moved.
- Antitrust separation
- Before closing, the acquirer may not see competitively sensitive data. The system, not a policy, has to block the movement.
- Long-term retention
- Regulated records are kept for years, provably unaltered, with legal hold when litigation requires it.
- Copy the files
- Where ordinary tools stop. Mergiva copies the files too, checks each one at both ends, and covers the four needs above.
Built for everyone who signs off on a deal’s data.
A regulated deal has more than one owner. Each of them gets something specific.
M&A leaders
Keep the integration on the deal’s clock. Know what the seller holds before closing, stay on the right side of antitrust rules without relying on memos, and leave the services agreement on time with the proof in hand.
Integration management
Plan the data work in waves and see the status of each one. The system, not a checklist, stops data reaching you before Day 1.
Quality assurance
Every wave carries two electronic signatures, every file is checked on arrival, and the audit trail can be re-checked at any time. A ready-made validation pack gives your team a head start.
Privacy and legal
Personal and health data is flagged before it moves. Antitrust counsel must sign before the deal moves toward closing, and the system keeps data from you until integration begins.
IT and security
Installs in your own cloud, with no shared service and no standing access for us. Several independent safeguards keep each deal’s data apart, and AI requests can run through your own gateway.
Judge us on the evidence, not the demo.
Every claim on this site is backed by the product’s code and test runs. These are the ones buyers ask about first.
- 49/49 connector pairs passedLive systems, 26 September 2026. Each file read back from the destination and checked again.
- Two people approve every waveBuilt into the system, not left to process.
- Checked at both endsIf a file does not match, the wave stops and is flagged. It never reports success over an unchecked file.
Your cloud, your data.
One dedicated installation per customer, in your own cloud. We do not run a shared service and we have no standing access to your deal data.
- AI sorting runs under your own account, or through your own gateway.
- By default, a user can open a deal only while on its deal team.
- The system will not start with unsafe settings.
Your cloud account
Mergiva services
- Web app
- Discovery and classification
- Wave planner
- Transfers
- Audit trail and signatures
Yours, as today
- Database
- Sign-in service
- Storage
- Your network rules
Installed in one step.
Guides for the deal team.
Practical reading for integration, quality and legal teams.
Data integrity through an acquisition: what GxP asks of an M&A data move
How regulators’ data integrity principles (ALCOA+) apply when records change hands, and what evidence to keep along the way.Quality and compliance · 6 min readPlanning the TSA exit: a checklist for the data workstream
A practical sequence for the data workstream, from the first inventory to the evidence you keep after exit.Integration · 5 min readClean teams and the line before closing: keeping deal data separate
Why competitively sensitive data stays separate until closing, and why systems should enforce the line.Legal and antitrust · 5 min read
How is Mergiva validated?
Validation is always executed in your environment and signed by your people, so no vendor can do it for you. Mergiva is built for GxP, and we supply a validation pack (requirement maps, control list, test evidence and operating procedures) for your quality team. Then we execute the validation with you, on your infrastructure.
Does our data leave our cloud?
Only where you choose. Files go to the systems you connect, notices to your own e-mail and chat. For AI sorting the model sees a file’s name, path and type, plus a short excerpt for files on your own servers, with detected personal data removed first. You can send every AI request through your own gateway.
Which AI model does Mergiva use?
Claude Haiku 4.5 by default. Claude Sonnet 4.6 and Claude Opus 4.6 are also supported, and an administrator can choose the model for each AI feature. Behind your own gateway, you list the models it serves.
How do you prove a file arrived intact?
Each file’s fingerprint is taken when it is found and again after it arrives. A match is recorded in the audit trail. A mismatch fails the file, stops the wave and raises an exception for a steward. One known case: SharePoint updates PowerPoint files a few seconds after they arrive, so Mergiva checks them just before that and records SharePoint’s change.
How does a pilot start?
Name the two systems you need to connect, and we produce that pair’s evidence first. Then we scan one source in your own cloud, plan validation with your quality team, and run the first wave with two signatures and a compliance report.
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.
- 1
Name the pair
Tell us the two systems you need to connect. We produce that pair’s evidence before the pilot starts.
- 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
Plan validation together
We work through the validation pack with your quality team, on your systems.
- 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.