What happens to your data when your SaaS vendor is acquired

The software a company runs on is usually made by another company, and software companies are bought and sold regularly. When it happens to a vendor you depend on, very little changes on the day the deal closes. Your login works, your records are where you left them, and the next invoice looks the same. The changes come later, at renewal or when the new owner decides what to do with what it bought, and by then your business has another year of data and habits inside the product.

Why your contract usually moves with the vendor

Start with the assignment clause in your agreement, which says whether the vendor can transfer the agreement to a buyer in a merger or a sale of the business without your consent. If it can, you become the new owner's customer on the terms you already signed, and those terms hold until they come up for renewal. From that point on, the new owner sets the price, decides how the product is packaged and decides whether it continues at all.

Changes that have followed public software acquisitions

The examples below are all public, and in each one the company announced its plans and gave customers notice.

Licensing and packaging can change. Broadcom completed its acquisition of VMware on November 22, 2023. On December 11, 2023, VMware by Broadcom announced the end of sale of perpetual licenses and of support renewals for perpetual offerings, moved its products to subscription licensing, and consolidated its product line into fewer offerings. Customers with perpetual licenses and active support contracts kept using them under those contracts, so for most customers the change arrived at their next renewal.

A product can be retired. Microsoft acquired 6Wunderkinder, the maker of the Wunderlist task app, in June 2015. In December 2019 it announced that Wunderlist would shut down on May 6, 2020, stopped new sign-ups, and pointed users to Microsoft To Do, which could import their lists. Users had several months of notice and a way to move their data. The product they had chosen still went away, about five years after the deal.

Your account can move to a different company. In June 2023 Google agreed to sell the domain registrations and customer accounts of Google Domains to Squarespace. The sale closed on September 7, 2023, and Google Domains customers became Squarespace customers. Squarespace says all domains had migrated to its platform by July 10, 2024. A business that had picked Google as its domain registrar ended up as the customer of a company it had never signed up with.

API access can change, which affects every tool connected to the product. Twitter changed ownership in late October 2022. In early February 2023 the company announced that from February 9 it would end free access to its API, both v2 and v1.1, and offer a paid tier. Any business tool that read from or posted to Twitter through the free API had to start paying for access or stop working.

In each case customers had warning, and in most of them they had a migration path. The decision itself still belonged to an owner the customer didn't choose.

What happens to the data itself

In the examples above, customer data either moved with the business or users were offered a way to import it somewhere else. The harder question is what you can do with them once the product changes. Your options depend on the export the vendor offers: what format it comes in, whether attachments, comments and history come with it, and how long you have to take it after you leave. A spreadsheet of contacts is a long way from a working system, because the pipeline stages, automations and reports your team built inside the product usually don't come with the export.

What owning your software changes about the risk

When a company owns its software, a deal somewhere else in the market has much less to act on. Clearloom's standard agreement says source code, database schemas and configurations belong to the client on payment. On termination the client receives the git repository, database snapshots and hosting credentials, and there is a 60-day exit transition. The client also chooses where the software runs: in its own cloud account on a provider such as Vercel or AWS, on its own servers, or hosted by Clearloom.

The same terms apply if the company affected is Clearloom. If we were acquired, or if a client simply decided to stop working with us, the client would still hold the code and the data, and a competent developer could pick up the repository and keep going. Owned software does still depend on some outside services, such as the cloud host it runs on, and those providers can change their terms too. Moving an application you own to a different host is a bounded engineering task, though, and you're the one who decides whether and when to do it.

What to check in the contracts you have now

1. Find the assignment clause and see whether the vendor can transfer your contract in a sale without your consent.
2. Ask for a sample export, and check whether it includes attachments, history and the custom fields your team added.
3. Write down the renewal date and the notice period, so a repricing can't arrive after your window to leave has closed.
4. List the other tools that connect to this one through its API, because those connections are affected directly when API terms change.

If you'd like a clear view of which vendors your business depends on and what each one costs, Clearloom offers a free SaaS audit at clearloom.ai/audit. It's a 15-minute call. You share your last three months of software invoices, and we send back a ranked list of what to cancel, what to consolidate and the projected savings. You keep the list whether you work with us or not.