Your Software Vendor Was Acquired: What Changes in Your Contract?
By Anirudh Menon, Viaclause editor
Separate ownership news from contract transfers and service changes. Use a review record before signing a new order or accepting a proposed migration.
AI-generated editorial illustration by Viaclause. People and setting are fictional.
When your software vendor announces an acquisition, first establish what changes for your own agreement. Ask which legal entity will perform it, whether a transfer is proposed, and whether you are being asked to sign new terms. Keep those questions separate from changes to support, product availability or billing.
Connect this task to the responsibilities and handover record in the contract administration plan.
A headline about new ownership cannot answer all four. This guide gives US procurement, IT and legal teams a record for obtaining the missing information. It does not assess a particular acquisition or establish a right to cancel.
Check whose assignment rights the clause describes
Do not stop at a sentence saying the customer cannot assign without consent. Read the language governing the supplier too. In HubSpot's September 16, 2026 terms, section 12.9, the supplier's permitted assignments include specified affiliate and corporate-transaction situations.
Atlassian's posted agreement, effective October 1, 2026, section 20.3(c), separately permits Atlassian to assign rights and obligations without customer consent. That future-effective public example does not determine the terms of an existing agreement as of September 27. It illustrates why both sides of the clause need reading.
Neither example establishes a general rule for all acquisitions. Give counsel the actual transaction notice, your signed agreement and its amendments. Ask whether the identified event triggers assignment, change-of-control, notice, consent or other provisions under the applicable law.
If the transaction proposes a new contracting party, our assignment vs novation responsibility table separates transferred rights, assumed performance and release of the original supplier.
Keep two records: contractual change and service change
Use the following as a request list. Ask for a supporting document or written answer, identify the owner and give each unresolved question a follow-up date.
- Contract party: legal entity currently named in the agreement; entity proposed to perform it after the transaction; evidence identifying the change, if any.
- Transaction status: announced, completed or conditional, with a dated source. Do not replace a planned completion date with an actual one.
- Contract mechanism: proposed assignment, new agreement, amendment or confirmation of no change. Ask counsel which clauses govern that mechanism.
- Requested signature: document, requested deadline and each term that differs from the existing package. Record a request as a request, not an obligation already established.
- Service continuity: support contacts, commitments, product availability and any proposed migration or shutdown dates.
- Data and access: planned hosting, processing or access changes, the documents governing them, and the person responsible for review.
- Commercial administration: pricing, renewal dates, invoices and payment instructions requiring confirmation through your established vendor-verification process.
A confirmed contractual transfer does not fill in an unanswered support question. A reassuring roadmap presentation does not supply the text of a proposed amendment. Keep the two records linked, with separate evidence and decisions.
Compare the current position with the requested change
Hypothetical example: a vendor announces that its parent has changed. A week later, the account team sends a new order form and says the buyer should sign it to “simplify integration.” The proposed order also changes the renewal date and includes a different support package.
The buyer can list three separate items: ownership announcement, request for a new signature and proposed service change. It can then ask:
Which provision requires us to sign this document, if any? Please identify changes to our contracting entity, renewal date, support commitments, data terms and fees. What happens to our current service if we need time to review the proposal?
This is a proposed information request, not an instruction to refuse performance or delay a legal deadline. Counsel should review any stated response period. Procurement can meanwhile mark each changed term and identify the commercial owner who must approve it.
If the reply says the existing agreement continues unchanged, retain that response with its date and scope. It may answer one question while leaving migration timing or technical compatibility unresolved. Ask IT to test the proposed operational change rather than infer that unchanged contract wording means unchanged day-to-day work.
Prioritize the decision that could become irreversible
Make a dated list of proposed signatures, consent deadlines, migrations and access changes. Identify which dates are contractually established, which are vendor requests and which remain unverified. Ask counsel to resolve uncertainty before treating a date as optional or mandatory.
For a new order or amendment, use the document-conflict review. For a promised replacement capability, use the vendor-promise worksheet. If a migration or access cutoff is proposed, use the data-export test to prepare a practical continuity plan.
The immediate output should be a short decision record: confirmed changes, unanswered questions, required reviewers and the next date that matters. Do not turn an acquisition announcement into either a guaranteed escape route or an assumption that nothing needs checking.
Sources
- HubSpot Customer Terms of Service, modified September 16, 2026, section 12.9. A supplier-specific assignment example.
- Atlassian Customer Agreement, posted with an October 1, 2026 effective date, section 20.3. A future-effective supplier assignment example, checked September 27, 2026.