Salesforce Quip is being retired.
Start your migration now.

1. What's happening and why

On March 5, 2026, Salesforce officially announced that Quip — its collaborative document and spreadsheet suite — is entering end-of-life. All Quip products (Starter, Advanced, and Plus tiers) are being retired. Subscriptions will continue working until they expire, but no renewals will be accepted after March 1, 2027.

Quip was acquired by Salesforce in 2016 for approximately $750 million. Its co-creator, Bret Taylor (later Salesforce co-CEO), built Quip as a competitor to Google Docs that embedded structured data alongside freeform text. For nearly a decade, it served as Salesforce's answer to Microsoft Teams + SharePoint for collaborative work.

The strategic logic for the shutdown is clear: Salesforce has been moving collaboration into Slack (acquired in 2021 for $27.7 billion), and Quip technology now forms the backbone of Slack Canvas. Rather than maintain two overlapping collaboration layers, Salesforce is concentrating investment in Slack + Agentforce.

What this means for Quip customers:

• All Quip content — documents, spreadsheets, folders, Salesforce Live Apps — will eventually be permanently deleted after your subscription expires
• Salesforce is building migration tooling (in-product flow to convert Quip docs to Slack Canvases), but it won't cover everything
• No new Quip features or development will occur
• If you use Quip Live Apps (embedded Salesforce data in documents), those integrations will stop working

2. Timeline and shutdown phases

3. How to export your Quip data (step-by-step)

Export individual documents

1. Open any Quip document
2. Click the document title (or the ··· menu)
3. Select Export
4. Choose PDF (for formatted output) or HTML (for structured content that can be imported elsewhere)
5. Repeat for spreadsheets — spreadsheets can also be exported as XLSX (Excel)

Bulk export via Quip API

For teams with many documents, the Quip API is the only way to bulk export. You'll need admin access and basic scripting ability.

1. Generate a personal API token in Quip: go to your profile → Edit Settings → Personal API Access Token
2. Use the /1/threads/folders endpoint to list all threads in each folder
3. For each thread, use /1/threads/{thread_id}/export/pdf or /1/threads/{thread_id}/export/docx to download the document

# Example: list your private folder contents
curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://platform.quip.com/1/threads/folders/PRIVATE" | python3 -m json.tool

# Export a specific document as DOCX
curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://platform.quip.com/1/threads/THREAD_ID/export/docx" \
  -o my_document.docx

Iterate through all folder IDs returned to get a complete export. Store everything in a structured folder hierarchy that mirrors your Quip workspace.

Salesforce in-product migration tool (coming)

Salesforce has announced it will release an in-product migration flow to convert Quip documents directly into Slack Canvases. This will include user and admin tools for exporting content to third-party applications. This tool is not yet available as of March 2026. Watch Salesforce's release notes and your Quip admin panel for when it ships.

Quip Live Apps (Salesforce-embedded content)

Quip Live Apps — dynamic content blocks that pull live Salesforce data (pipeline views, opportunity lists, Kanban boards) — cannot be "exported" as data. They are views into your Salesforce org. Before Quip shuts down:

1. Document all active Live Apps by type (Salesforce Record List, Kanban, Calendar, etc.)
2. Screenshot the current state of each Live App for reference
3. Plan to recreate these views using Salesforce Reports & Dashboards, Slack's Salesforce integration, or your chosen replacement platform's CRM integration

4. What to save before it's gone

Complete Quip data inventory — check every item:

• All Quip documents (PDF, HTML, or DOCX export)
• All Quip spreadsheets (XLSX export)
• Embedded images and file attachments — download these separately from within each document
• Shared folder structures — document your folder hierarchy and permissions before it disappears
• Team workspaces and shared links — identify all external sharing links that reference Quip docs (these will break)
• Quip Live App configurations — screenshot and document each one
• Comment threads and annotations — comments on documents are NOT included in PDF/HTML exports; take screenshots if they contain important decisions or context
• Admin settings — list of all users, their permission levels, and team memberships
• API tokens and integrations — document any custom integrations or Zapier zaps that reference Quip

5. Alternative comparison

We evaluated the leading Quip alternatives on document collaboration capability, Salesforce integration depth, ease of migration, and pricing. Quip occupied a specific niche: collaborative docs + live CRM data. No single replacement covers that combination perfectly, so the right answer depends on your primary use case.

What we liked and didn't like about each

6. Head-to-head: Quip vs. each alternative

How does each alternative compare to Quip on the features that mattered most to Quip users?

Quip vs. Notion

Notion is the closest overall replacement. Like Quip, it merges freeform text with structured data in a single document surface. Notion's databases are more flexible than Quip's spreadsheets. The main gap: Notion has no native Salesforce live data embedding. If you relied heavily on Quip Live Apps to pull CRM records into documents, you'll need Zapier or a Notion integration to approximate that workflow.

Quip vs. Slack Canvas

Slack Canvas fills the Salesforce integration gap that Notion misses. Canvas supports embedded Salesforce record lists, opportunity details, and account data directly in a document-like surface within Slack. It's the only alternative where native Quip Live App behavior can be approximated without third-party tools. The trade-off: Canvas is still maturing, and it does not replace Quip's spreadsheet functionality at all.

Quip vs. Confluence

Confluence is a stronger knowledge management system than Quip for technical teams. For sales and operations teams that used Quip for CRM-adjacent work, Confluence is not a natural fit. It lacks Salesforce integration depth and doesn't have a database/spreadsheet equivalent.

Quip vs. Google Workspace

Google Docs + Sheets covers Quip's core functionality in a familiar environment. The gap is the integrated workspace feel — in Quip, everything lived in one document. In Google, your docs, sheets, and slides are separate files in Drive. For teams that valued Quip's all-in-one document surface, this fragmentation is a real adjustment.

Quip vs. Coda

Coda is the most philosophical successor to Quip. Both products bet on the "doc as an app" concept: dynamic content, live data pulls, and automation rules inside a document canvas. Coda's Packs provide a Salesforce integration that allows record lookups, filters, and syncs inside a Coda doc. The barrier is adoption: Coda has a steeper learning curve and smaller community than the other options.

7. Our recommendation by use case

8. Migration walkthrough (6-week plan)

A realistic migration plan for most Quip teams. Adjust timelines based on your document volume and integration complexity.

9. Frequently asked questions

Don't wait for the deadline rush

Quip's data deletion phases begin automatically when your subscription expires. Export your documents now, choose your replacement, and migrate on your own timeline — not Salesforce's.