Before renewing your Zendesk or Salesforce contract: negotiate data export and AI terms

Why is renewal the moment to fix data terms?#

Renewal is the moment to fix data terms because it is when a vendor most wants your signature. Mid-term, most SaaS contracts point to online terms the vendor can update, and your leverage is limited. At renewal, a negotiated order form or addendum can take precedence over those online terms.

Your helpdesk and CRM hold years of support conversations, account histories and sales activity, and both now ship AI features that read those records. The data terms in the renewal decide whether you can take that history with you when you leave, and who else can learn from it while you stay.

Start before the non-renewal notice window opens. The COO usually owns the calendar; legal, IT and the support and sales operations leads should each review the draft.

The renewal checklist#

The checklist covers the data and AI terms worth raising at every renewal. Not every vendor will agree to every item, so rank them by what would hurt most to lose.

How do you ask for a complete export right?#

A complete export right starts with a broad definition of your data. Ask that it include system-generated records such as field history, ticket events and audit logs, not only the content your team typed.

Then name the record types that matter for each system. For a helpdesk, that means public comments, internal notes, attachments, ticket events, satisfaction ratings and help center content. For a CRM, it means accounts, contacts, opportunities, activity history, field history, files and custom objects. Ask for exports in a commonly used machine-readable format, during the term and for a defined period after it, without buying a separate tool.

Plan details matter more than most buyers expect. Zendesk, for example, says its account export tools are not available on Team plans, that exports must be enabled by the account owner through Zendesk support, and that AI agent tickets cannot be exported. Ask the vendor to confirm in writing which of these limits apply to your tier and how the gaps will be covered.

Test before you negotiate. Run a full export on a sample period now, check what is missing, and bring the specific gaps to the table. A vendor answers a named gap more readily than a general worry.

How do you stop unilateral changes to data and AI terms?#

You stop unilateral changes with an order of precedence clause that puts your negotiated order form above the vendor's online terms. Then fix the data-use and AI provisions for the length of the term, so updates to the vendor's website cannot change them.

Where the vendor will not freeze terms, ask for advance notice of material changes and a right to terminate with a refund of prepaid fees if a change harms you. Ask that new AI features touching your data stay off until an administrator turns them on.

Public episodes show why this matters. Zoom revised its terms in 2023 after backlash, adding a sentence to Section 10.4 on August 7, 2023 saying it would not use audio, video or chat Customer Content to train its AI models without consent. Slack faced similar criticism in May 2024 over privacy principles that let customer data train its machine-learning models unless an organization opted out. In both cases, customers with negotiated terms had firmer ground than those relying on the website.

Which AI terms should a COO ask for?#

The AI terms worth asking for are the ones that decide who learns from your records. Keep them short and specific.

If the vendor's AI features run under a separate addendum, read it with the main agreement. AI terms are often added through a new document that applies only once you accept it, sometimes by clicking to enable a feature in the admin console.

• 1A plain statement of whether the vendor uses your data, prompts or outputs to train or improve models, with an opt-in or opt-out you control.
• 2A bar on the vendor licensing or sharing your data with third parties for AI training.
• 3Confirmation that outputs of the vendor's AI features are your data.
• 4A list of model providers that process your data, and where they process it.
• 5Retention limits for prompts and outputs.
• 6No restriction on your own use of exported data, including licensing it.

What should you keep on file after signing?#

After signing, keep a record that lets someone else understand the data terms without reopening the negotiation. Store the signed order form, any addenda and side letters, and dated copies of the online terms and AI terms they reference, because the vendor's website will change.

Add the evidence that sits outside the contract: the results of your trial export, screenshots of AI and data-sharing settings in each admin console, the named contacts for exit assistance, and the next non-renewal notice date. When a migration, dispute or licensing review comes up, that file answers the first questions at once, instead of starting a search through inboxes and admin consoles.

Illustrative: a payroll software company renews its helpdesk and CRM#

Illustrative: a fictional payroll software company has its helpdesk and CRM renewals in the same quarter. The COO maps both dates, asks IT to run a trial export of each, and finds that the helpdesk export omits attachments and internal notes on the current plan, while the CRM export leaves out field history.

At the helpdesk renewal, the company secures a full export right covering attachments and notes, plus post-termination access for a final pull. At the CRM renewal, it adds an order form clause that freezes data-use and AI terms for the term and opts out of vendor model training. Counsel also obtains written confirmation that exported data may be used for any lawful company purpose.

Later, when the company reviews its support history for a possible licensing program, the vendor terms are already documented and do not stand in the way.

How SourceX looks at your system vendor terms#

SourceX reads system vendor terms when a company reaches the Rights step of the SourceX five-step transaction, next to customer contracts and privacy notices, because a record you cannot export cleanly is a record you cannot license. The first fit check asks only which systems you use and on which plans.

If a company proceeds, the SourceX Evidence Packet records the licensing rights relied on for each source system, including relevant vendor terms. Data stays in the company's own storage until it approves delivery.