The migration tool you bought precisely because it did not care where your data lived is now owned by a company that sells somewhere for it to live. Nasuni acquired DryvIQ on August 27, 2026, terms undisclosed.
DryvIQ's engine classifies and moves content across more than 40 cloud and on-premises repositories; its connector list spans SharePoint, Box, Dropbox, Google Drive, Egnyte, Documentum, FileNet, Alfresco and network file shares. Nasuni sells one of the places that content can land. The announcement says DryvIQ "is available to use immediately, and Nasuni plans to deepen the integration with its file data platform over the coming months." Read that sentence again. It funds exactly one direction of travel, and it is the direction that ends at Nasuni.
What Nasuni Actually Bought
Nasuni bought a content engine with wider reach than its own platform has. DryvIQ scans over 550 file formats, detects more than 100 entity types, recognises over 1,000 business document types and covers 175+ languages, and it is used by more than 1,100 global organizations. Nasuni claims more than 1,300 enterprise customers.
Content classification is the process of opening a file, reading what is inside it, and labelling it — this contract contains payment card data, that folder is medical records, this share has 40TB nobody has touched since 2019. It is the unglamorous prerequisite for everything an enterprise wants to do with AI, because a retrieval system that cannot see a sensitivity label will happily serve the salary spreadsheet to whoever asks.
The company is older than the AI framing suggests. DryvIQ was SkySync until a 2022 rebrand, and it built its business on bulk file migration between platforms that had no interest in helping each other. That is precisely the asset in question. Nasuni CPO Nick Burling framed the deal around consolidation: customers "have been attempting to stitch together a solution across multiple vendors for years." True. But some of those customers stitched deliberately, because the stitching was the neutrality.
The Connector Only Ever Pointed One Way
The partnership that preceded this deal was explicitly one-directional, and that is the tell. On February 17, 2026, DryvIQ shipped a Nasuni connector that, in the companies' own words, let organizations "migrate content into Nasuni at enterprise speed and scale". Not out of. Into.
To Nasuni's credit, its own blog post that day was clear about the wider scope, describing DryvIQ as delivering "content intelligence, classification, migration orchestration, policy automation, and lifecycle governance… Not only for Nasuni, but across 40+ enterprise repositories."
That sentence is now the most valuable thing in your renewal file. As a partner's marketing copy it cost Nasuni nothing. As an owner's roadmap commitment it costs engineering headcount every quarter, spent maintaining API compatibility with Egnyte — a direct competitor in hybrid cloud file services — and with Box and SharePoint, where a customer's data is not generating Nasuni revenue.
To Nasuni's credit again, it did repeat the promise as an owner. The acquisition release opens on giving organizations visibility and control "not just within Nasuni, but across more than 40 cloud and on-premises repositories", restates that scope in its governance section, and quotes DryvIQ's side on classifying and activating data "wherever it lives." That is worth considerably more than silence would have been. It is also still an adjective: it names no connector, sets no deprecation notice period, and appears in the same release whose one forward-looking roadmap commitment points at Nasuni. Restating a scope and funding it are different budget lines, and only one of them is in writing. Pinning neutrality to a list and a date instead is what made Visa's purchase of BioCatch and d-Matrix's purchase of Wallaroo worth a contract review rather than a press release.
Microsoft Already Ran a Version of This
The closest precedent for a storage destination buying a migration tool sits on Microsoft's own documentation site. Microsoft acquired Mover in October 2019 — a service that, in Microsoft's words at the time, "supports migration from over a dozen cloud service providers – including Box, Dropbox, Egnyte, and Google Drive – into OneDrive and SharePoint."
Microsoft Learn now states flatly that "Mover is now retired for all Admin led migrations", that the Google Drive, Box, Dropbox and Egnyte paths were absorbed into Migration Manager, and that Mover was unavailable for individual use after October 31, 2024.
Note the honest limit of that analogy before leaning on it: Mover's destinations were already Microsoft-only when Microsoft bought it, so this is not a case of an any-to-any engine being narrowed by its new owner. DryvIQ is the thing Mover never was.
What the Mover case does show is what happens to the standalone product and to the breadth of paths it supported. The capability was not deleted. It was folded into a tool with exactly one destination, and the supported set got smaller on the way — the same page notes that "Migration Manager doesn't support the migration of Amazon S3 or Azure blob storage." Paths that fed Microsoft 365 survived and got better. The ones that did not were not carried across, because nobody at Microsoft was paid to carry them. That is not corporate malice. It is a budget meeting.
Nasuni is a smaller company with a narrower platform, so the pull is weaker. The starting point is what differs, and not in your favour: Nasuni has bought an engine that genuinely does run any-to-any today, which means there is more here to stop funding than Microsoft ever acquired.
The Case That This Is Fine
The strongest argument against alarm is Nasuni's own recent conduct, and it deserves a fair hearing. Nasuni acquired Resilio on March 4, 2026 and told customers they "can expect to continue to receive the same level of service and support." Resilio's customer FAQ went further: "There is no change in Resilio's production solutions or roadmap as a result of today's news" and "There are no immediate changes to contracts or support terms." Nearly six months later, resilio.com still sells Active Everywhere and still takes free trials. Nasuni has kept that promise so far.
There is also a real technical argument. Classification works better close to the storage layer, where it can see change events instead of re-crawling, and Nasuni had already been assembling that stack — edge performance from Resilio, permission-aware access from AI Activate. This was a partnership before it was a purchase. That is the healthiest way these deals start.
Now note the load-bearing word in the Resilio commitment that covers contracts: immediate. It is doing all the work, and Nasuni has published no equivalent customer FAQ for DryvIQ at all. Futurum's Alastair Cooke flags the two open questions plainly — there are no independent accuracy figures for the classification, and whether governance ships built-in or as a premium add-on determines who actually gets it. Neither is answered. When Klaviyo bought Agency, the wind-down date arrived faster than the customers' renewal cycle did.
The Neutral Migration Market Is Thinner Than You Think
If your fallback plan is "we will just buy another migration tool," price it before you rely on it, because most of the market is already owned by a destination. ShareGate publishes its rates — starting at $5,995, $9,995 and $17,995 a year for Essentials, Migrate Pro and Enterprise — and it will read from SharePoint, Google Workspace, Box and file shares, but every destination it supports is Microsoft SharePoint or Microsoft 365. Microsoft's own Migration Manager has the same shape. Genuinely any-to-any engines that will move a petabyte from Documentum to Box without an opinion about where it should end up are a short list, and DryvIQ was near the top of it.
The asset at risk is not the Nasuni connector, which will obviously be funded. It is documentation like DryvIQ's own SharePoint-to-Box migration guide — a full, supported path with user mapping, permission handling and version preservation, that ends nowhere near Nasuni and generates Nasuni no revenue.
For the classification half specifically, the substitutes are storage-independent by design: Varonis Atlas and Cyera both classify across repositories without selling you the repository. They are not drop-in replacements for a migration engine. They are a hedge for the governance workload if the packaging turns out to be unfavourable.
The Packaging Question Nobody Answered
No price was disclosed for the deal and no pricing model was disclosed for the capability, which matters more. A bundled-versus-add-on decision does not just change a line item — it changes whether classification is something you run across all 40 repositories or only across the ones sitting on Nasuni.
That decision lands during your renewal window, not after it. If you are signing a Nasuni renewal in the next two quarters, you will be quoted before the packaging is public, and the natural sales motion is to include classification for Nasuni-resident data and price the rest separately. That is a rational thing for them to do. It is also the thing you have leverage over exactly once. The same logic applied when DoiT bought Attribute and when Stripe bought OpenRouter: the neutrality question is cheap to answer before signature and impossible after.
What To Do
This Week:
- Inventory your DryvIQ jobs by direction. Split them into three buckets: into Nasuni, out of Nasuni, and neither-end-is-Nasuni. The third bucket is your exposure, and it is the number you take into every conversation below.
- Pull the DryvIQ contract and find two clauses — the assignment / change-of-control clause, and any notice period for connector or feature deprecation. If there is no deprecation notice period, you have no warning mechanism, which is the gap Descartes' purchase of Tai turned into a 60-day scramble.
- Export your classification output and policy definitions through the API to storage you control. Labels, rules, retention policies, permission-remediation rules. If that export is not possible today, that is your finding.
This Month:
- Ask Nasuni, in writing, to name the connectors it will fund and the minimum notice it will give before deprecating one. Not "we remain committed to openness" — a list, and a number of days. Quote their February 17 blog post back to them.
- Price one alternative properly for your largest non-Nasuni migration path, so you know what the switch costs before you need to make it.
- If you are mid-project between two non-Nasuni platforms, get written confirmation of support through your completion date, plus the professional-services terms if the connector is retired underneath you.
Before Renewal:
- Get classification packaging in writing — bundled or add-on, the unit of pricing, and the rate for repositories that are not Nasuni. Uncommitted pricing at renewal is a bill you have already agreed to.
- Refuse "no immediate changes" as an answer. It is technically true of every acquisition ever announced, including the ones that ended in a wind-down notice. Ask for a date instead.
The Bottom Line
This is the second company Nasuni has bought since Vista Equity Partners led a majority investment at a $1.2 billion valuation in July 2024, when the company served just over 850 customers. A platform assembling itself by acquisition is a normal, healthy pattern — and it is also a pattern that consistently converts general-purpose tools into features of the platform that bought them, because that is what makes the acquisition math work. We saw the same dynamic when AWS took board control of the DuckDB Foundation without buying a single line of code.
The lesson is not that Nasuni will break something. It is that neutrality was never a property of the software. It was a property of the owner's incentives, and those changed on August 27. Evaluate this the way you should evaluate any platform: score the exit, not the feature list.
A migration tool is only worth the routes it will still travel next year. Get that list in writing, before you renew.
Continue Reading
- Visa Bought BioCatch. Get Neutrality in Writing.
- Descartes Bought Tai. Your Only Lever Is 60 Days.
- Klaviyo Bought Agency. The Product Dies August 31.
- DoiT Bought Attribute. It Also Sends Your Cloud Bill.
- Stripe Bought OpenRouter. A Toggle Is Not a Contract.
- AWS Didn't Buy DuckDB. It Hired Its Board Majority.