Migrating customers from bespoke contracts to standard terms

A software business that grew by signing whatever each early customer wanted ends up with a filing cabinet of different contracts, and the moment it wants one set of terms it discovers that a contract cannot be changed by sending an email. Existing customers are bound by what they signed until it expires or they agree otherwise; the migration has to be built around renewals, consents and variations, with consumer customers treated differently from business ones, and the new terms have to be worth moving to. I draft the standard terms and the migration mechanism for a fixed fee of £995, delivered in five working days.

Who this is for

SaaS businesses in England and Wales with a mix of negotiated contracts, old click-through terms and no terms at all across their customer base, who want to consolidate onto one current set of terms without losing customers or breaching the contracts they have.

What matters in migrating customers to standard terms

Why existing contracts cannot be changed by notice

A signed contract binds both parties on its terms until it ends, and a variation needs the customer's agreement and, unless made by deed, consideration, so a notice that the new terms apply from next month has no effect on a customer with a negotiated contract unless that contract itself allows the supplier to update its terms. The first task is to read each contract for a variation clause and an end date, and the migration plan should classify customers by which mechanism is available for each.

The renewal as the point of migration

Most bespoke contracts renew for further terms unless notice is given, and the renewal is the point at which the supplier can lawfully offer new terms: by giving notice that it will not renew on the existing terms and offering the standard terms in their place, within the notice period the contract sets. The standard terms should be drafted so that renewal under them is automatic in future, with a variation clause that lets the supplier update the terms on notice with a right to end the subscription if the change is material, so that the migration is the last one.

Consent mechanics and deeds of variation

For customers whose contracts do not expire soon, migration needs agreement: a short deed of variation or a new order form under the standard terms, signed by both parties, with the customer's consideration for the change stated (a price hold, a feature, a longer term) or the document executed as a deed under section 1 of the Law of Property (Miscellaneous Provisions) Act 1989 and section 44 of the Companies Act 2006. An 'accept to continue' click within the product can work for business customers if the terms they signed allow it; the migration documents should say which route applies to whom.

Consumer customers and fairness

A consumer's contract can be varied only where the existing terms allow it and the variation is fair under Schedule 2 to the Consumer Rights Act 2015, which lists as potentially unfair a term letting the trader alter the terms unilaterally without a valid reason stated in the contract; a consumer must be told of the change, given the reason, and allowed to cancel without penalty before it takes effect. Where the new terms are renewal terms, the subscription contract rules under Part 4 of the Digital Markets, Competition and Consumers Act 2024 apply to the notices, and the migration should be timed to a renewal with the reminder the rules require.

Data processing, security and the terms that must be current

Old contracts often contain data protection clauses written under the Data Protection Act 1998 or none at all, and the processor terms required by Article 28 of the UK GDPR apply regardless of what the contract says; the migration is the opportunity to put a compliant data processing schedule in place with every customer, and where a customer will not sign the standard terms, the data processing schedule should be offered on its own, because the supplier's own compliance depends on it. Security commitments, subprocessor lists and transfer mechanisms under Article 46 should be brought up to date at the same time.

The record, the stragglers and the cut-over

The business should keep a register of which terms apply to each customer, the date and mechanism of migration, and the signed variation or the notice and the renewal date it relied on, because the question of which terms applied will be asked in a dispute years later. Customers who refuse to migrate remain on their contracts until those expire, and the standard terms should be drafted so that the supplier can serve non-renewal notice at the right time. Interest on late payment under the Late Payment of Commercial Debts (Interest) Act 1998 and the other business provisions apply from the migration date.

What it costs

SaaS terms of service, £995. Your standard customer-facing terms. Five working days.

Buying online forms the engagement on payment. The scope is what the saas and technology contracts page describes, you accept the Terms of Service at checkout, and I email you within four working hours to get started. If you would rather ask something first, email me.

What you get

• A bespoke contract drafted for how your product is sold, delivered and supported
• Service levels you can meet, with remedies that are proportionate rather than aspirational
• A liability position that is defensible and will survive enterprise procurement
• IP and data provisions that fit together rather than contradicting each other
• A commercial note on where you will get pushback and what is worth conceding
• One round of amendments

What is not included

• Negotiating individual enterprise deals, which I quote separately
• Advice on the law of jurisdictions outside England and Wales
• Technical security certification or audit
• Regulatory advice for regulated sectors such as financial services or health

Questions I am often asked

Can we just email all customers that new terms apply from next month?

Only to customers whose existing terms allow the supplier to update them on notice, and only for changes that clause permits. Everyone else is bound by what they signed until renewal or a signed variation; the migration plan classifies each customer accordingly.

An enterprise customer refuses to move off its negotiated contract. What happens?

It stays on that contract until it expires or renews, and the supplier serves non-renewal notice at the right time and offers the standard terms. Meanwhile the data processing schedule should be agreed on its own if the old contract lacks one.

Is a click to accept in the product enough?

For business customers whose existing terms allow updates that way, or who have no written terms, usually. For customers with a signed negotiated contract, a signed variation or a new order form is the safer record.

Related guidance and services

• SaaS and technology contracts, £995, the service this page describes
• Contract review, £495
• Data protection agreements and privacy terms, £795
• Auto-renewal and cancellation terms for a subscription product
• SaaS terms of service for a B2B product

This page is general guidance for businesses in England and Wales, not advice on your own circumstances. Last reviewed: September 2026. Email geoffrey@caesar.co.uk.