Quip licence cost after the Salesforce acquisition

A guide to Quip licence cost used to be a guide to seats. It is now a guide to a run-off. Salesforce completed its acquisition of Quip in 2016, but the product is on its way out, and the licence decisions that matter are about timing and replacement, not about how many editors to buy. This guide covers the licence and the budgeting around it. The migration project itself is a services topic covered on the sibling pages linked at the end.

#What Salesforce has said

The clearest public statement we could read was a report of Salesforce's announcement, published on 4 March 2026 by Salesforce Ben: "Salesforce has announced that all Quip products are being retired, and any subscriptions cannot be renewed after March 1, 2027." The same report says Quip instances will remain fully functional until the end of the subscription term, that no immediate action is necessary, and that Salesforce recommends exploring how Slack and Agentforce can serve the same use cases.

We tried to read Salesforce's own Help article on the retirement and could not, because the page renders its content with scripts that a plain read cannot execute. Treat the dates below as reported rather than confirmed, and ask your account team to send you the Help article and your own account's dates in writing before you rely on any of them.

For the history, Salesforce's acquisitions page records it plainly: "August 26, 2016: Salesforce completed its acquisition of Quip." That sentence is about the purchase. It says nothing about a price, a seat or a renewal, and it should not be used to infer what your contract allows.

#Is there a published Quip price?

we looked for one and did not find one. When we opened Salesforce's Quip pricing address on 13 October 2026, it redirected to the Salesforce Slack pricing page, which is itself a useful signal about where Salesforce wants Quip customers to look. A search of Salesforce's older Quip pages returned notes that per-user products required an annual contract and that detailed pricing needed a conversation with a sales representative, with tier names but no figures.

So the honest answer to what a Quip seat costs is that the number lives in your order form. If you do not have it to hand, ask procurement for the document that lists the product, the number of users, the price per user, the term and the renewal date. Do not estimate a Quip price from other products, and do not accept a figure quoted from memory in a meeting.

#What happens at the end of a term

The same report describes three phases after a subscription expires: a read-only period of 90 days, a period during which logins are blocked, and then deletion of data over roughly 30 days. The article is not consistent about how long the blocked-login phase lasts, calling it 90 days in one place and a 30-day phase in another. That inconsistency is exactly why you should get the dates from Salesforce directly.

Whatever the exact figures, the planning rule is the same. Your documents are safe and editable until term end, read-only for a period after it, and then at risk. Anything you want to keep has to be exported or migrated while you can still work on it. The report also states plainly that Quip content will not be automatically moved. Nobody is going to do it for you.

#What you pay between now and the end

For most customers this is the cheap part, because you are already paying it. The licence cost between now and term end is whatever your order says, and there is little to negotiate unless the term end is close to the cut-off. Three questions are worth asking.

If your term ends before 1 March 2027, can you renew for a short period to cover the migration, and at what price? If your term ends after the cut-off, is there any early-termination or reduction option, or are you committed to the full term? And if Quip is co-termed with another Salesforce product, does the retirement change how the remaining lines are priced at their renewal?

Do not assume goodwill. Ask for any concession in writing, and assign someone to own the Quip contract until it expires, because an unowned subscription is how a retirement turns into a surprise invoice or a surprise data loss.

#Budgeting the replacement

The licence of the replacement is usually the smaller part of the cost, but it is the part you can price today. Salesforce has said an in-product flow is planned for converting Quip documents into Slack canvases, and it has described tools for exporting Quip content to other applications. If Slack is your destination, its published prices, which we read on 13 October 2026 at slack.com, are US$7.25 per user per month on Pro billed annually and US$15 on Business+ billed annually, with Enterprise+ by quote. Slack's own comparison table lists canvases among its features, and Slack bills for active members rather than a fixed seat count. Our Slack licence guide works through those numbers.

Slack is not the only destination. If your Quip documents are mostly long-form content with versioning and review, a document platform may fit better than a chat tool. If they are mostly account plans and meeting notes attached to deals, the right home may be Salesforce records themselves. Price each option on the same basis: licence per active user per year, the cost of migrating your content, the cost of retraining, and any integration you need to rebuild.

#Building your own timeline

Because the deadline is your own term end, the first job is to put three dates on one page: the end of your current Quip term, the reported renewal cut-off of 1 March 2027, and the date by which the replacement must be live for people to work in it. Work backwards from the second to the third. If the replacement must be live a month before term end so that nobody edits in two places, then export and migration must finish before that, user training before that, and the destination decision before all of it. A calendar built this way often shows that the decision is due much sooner than the term end suggests.

Add the read-only period as a safety margin, not as a plan. A read-only window lets you retrieve what you missed, but it does not let anyone work, so a team that discovers on the first day of read-only that its live account plans have not moved will be working from spreadsheets for a quarter.

#Sizing the replacement licence

Quip seats were presumably bought for the people who edit documents, and that may be a smaller or a larger group than the people who will need the replacement. Begin with activity: who edited, who only viewed, and who has not signed in for months. A seat you are retiring is a good moment to stop paying for a person who left a year ago.

Then price the destination on its own unit. For a chat-centred destination billed on active members, the active definition matters, and you should size on observed use. On Slack's published annual prices, a hundred active members cost US$8,700 a year on Pro at US$7.25 and US$18,000 a year on Business+ at US$15, before any discount. For a document platform with named seats, the number to price is the editor count plus a realistic viewer count. In every case, keep the figure for the licence apart from the figure for moving content, because they are paid to different parties, on different dates, for different reasons.

#What doing nothing costs

It is tempting to treat the retirement as a problem for later. The cost of that is easy to describe. If you ignore it, your subscription will expire or fail to renew, your instance will go read-only, and then it will be locked and eventually deleted. Documents you needed will have to be recovered from an export you did not take, or not at all. The licence saving from not renewing is real, but it is dwarfed by the cost of losing content that a sales or service process depends on.

The sensible position is a deliberate wind-down: a named owner, a decision on destination, an inventory of what stays, a scheduled migration and a final export retained under your own control, so that even a content decision that proves wrong can be corrected.

#Counting what must move

Before you can price migration, you need to know what you have. Count documents, spreadsheets, folders and chat threads, then separate the live from the dead. Most Quip estates contain a large share of documents nobody has opened in a year, and migrating them is a decision, not a default. A reasonable approach is to classify content as active, reference or archive, migrate the first, convert the second to a durable export, and leave the third in a retained export.

Pay particular attention to Quip's Salesforce-linked content: documents embedded in records, live apps and templates that sales or service teams use daily. These have dependencies, and moving the document without the link leaves a hole in a process. List the dependencies before you pick the destination, because the destination has to be able to do the same job.

#Who should own the decision

A retirement lands awkwardly because no single team feels it. Procurement owns the contract, the business owns the documents, IT owns the integrations and security owns the retention question. Pick one accountable person early, give them the order form, the list of document owners and the authority to make the destination call, and have them report on a fixed cadence. The cheapest migrations in this situation are rarely the ones with the best tooling. They are the ones where somebody was clearly in charge from the day the announcement was read.

#How to compare replacement offers

Whatever you shortlist, ask each vendor for the same set of answers: the price per user per year at your active user count, what the plan includes for content structure and permissions, what import tooling exists for Quip content, what the term and renewal rules are, and what data export you get if you leave later. The last point matters more than usual, because you are about to learn what a retired product costs to leave. Choose the next one with a clear exit.

Be sceptical of any offer that bundles migration into the licence price with no scope. A migration is work with a defined content volume, and a vague inclusion is a dispute waiting for a date.

#Where to go next

For the services side, see the Quip page. For the history, see what happened to Quip. For how a document meets a record, see integrating Quip with Salesforce, and for the decision to move, see should I migrate from Quip. The announcement report is at Salesforce Ben.