---
title: "Quip to Slack Canvases Migration: The Official Salesforce Path"
slug: quip-to-slack-canvases-migration-the-official-salesforce-path
date: 2026-05-08
author: Raaj
categories: [Migration Guide, Quip]
excerpt: "Salesforce is retiring all Quip products by March 2027. Here's the official Quip to Slack canvases migration path, what survives, what breaks, and the API fallback."
tldr: "Quip subscriptions end March 2027 with a 210-day wind-down to data deletion. Salesforce's official path is Slack canvases, but spreadsheets, @date mentions, and Live Apps don't migrate cleanly."
canonical: https://clonepartner.com/blog/quip-to-slack-canvases-migration-the-official-salesforce-path/
---

# Quip to Slack Canvases Migration: The Official Salesforce Path


Salesforce is retiring all Quip products. Subscriptions cannot be renewed after March 1, 2027, and once your subscription expires, a strict three-phase wind-down begins: **90 days of read-only access**, then **90 days of blocked logins**, then **permanent data deletion** (~30 days). Your Quip data is **not** automatically migrated anywhere — if you don't act, it's gone. ([salesforceben.com](https://www.salesforceben.com/salesforce-announces-end-of-life-for-quip/))

Salesforce's official migration path is an **in-product flow for converting Quip documents into Slack canvases**, plus admin tools for exporting content. This flow is rolling out throughout 2026 and may not yet be available in your tenant. This guide covers what the official path looks like, what survives the migration, what breaks, and what to do if the in-product flow isn't available yet.

If your destination isn't Slack, see our dedicated guides for [Quip to Notion](https://clonepartner.com/blog/blog/quip-to-notion-migration-step-by-step-guide-api-limits/), [Quip to SharePoint](https://clonepartner.com/blog/blog/quip-to-sharepoint-migration-the-complete-technical-guide/), or [Quip to Coda](https://clonepartner.com/blog/blog/quip-to-coda-migration-api-limits-data-mapping-export-guide/). If someone is still proposing a move *into* Quip before the sunset, read our [Confluence to Quip migration guide](https://clonepartner.com/blog/blog/confluence-to-quip-migration-api-limits-methods-data-mapping/) with an exit plan already attached.

> [!CAUTION]
> **Quip End-of-Life (March 2027):** All Quip products — Starter, Advanced, and Plus — are being retired. After your subscription expires: Read Only (90 days) → Blocked Logins (90 days) → Data Deletion (~30 days). The official path is a transition program, not an automatic migration. Do not wait until read-only mode to begin.

## Why Salesforce Is Funneling Quip Users to Slack Canvases

This path is not arbitrary. Salesforce acquired Quip in 2016 for approximately $750 million, bringing collaborative documents into its ecosystem and co-founder Bret Taylor into the company. Then Salesforce acquired Slack in late 2020 for nearly $28 billion. The two acquisitions created a strategic overlap — Quip was a standalone collaboration suite, while Slack was becoming the primary work surface for Salesforce customers.

Slack Canvas, announced at Dreamforce 2022 and generally available in 2023, was the resolution. It is not merely "inspired by" Quip — it is **built on the Quip codebase**. Slack's Chief Product Officer Tamar Yehoshua stated directly: "Canvas is taking the collaborative components of Quip and integrating them natively into Slack." An ex-Quip engineer's [technical analysis](https://blog.persistent.info/2023/07/slack-canvas-quip.html) confirmed that the Slack Canvas editor still uses Quip's DOM structure, CSS class names, and the same Python backend — noting that "Quip's backend, which powers both Quip and canvas, is written in Python."

Because the underlying technology shares DNA, Salesforce positions Slack Canvas as the natural successor. The text rendering engine, live data embeds, and collaborative commenting structures are highly compatible. This shared architecture is why the official in-product migration flow can translate standard Quip documents into Slack canvases with reasonable fidelity.

But "built on the same codebase" does not mean "feature parity." Slack Canvas was designed for a different primary use case — surface-level contextual information attached to Slack channels — not deep, standalone document and spreadsheet management. That distinction becomes clear when you evaluate what actually migrates.

## The Official Migration Timeline: Wind-Down Phases

Salesforce classifies Quip as an **Order End Date** retirement — the wind-down starts when your own subscription term ends, not on one global shutdown day. ([help.salesforce.com](https://help.salesforce.com/s/articleView?id=000381744&language=en_US&type=1))

| Phase | Duration | What Happens | What You Can Still Do |
|-------|----------|--------------|----------------------|
| **Active** | Until subscription expiry | Full functionality | Everything — this is your migration window |
| **Read Only** | 90 days post-expiry | Site enters read-only mode | Log in and view content, no editing or collaboration |
| **Blocked Logins** | 90 days after read-only | Users cannot log in | Nothing — data exists but is inaccessible |
| **Data Deletion** | ~30 days after blocked logins | Permanent deletion begins | Nothing — data is being destroyed |

The 2027 retirement was not the first signal of contraction. Quip retired the Upload/Import option and the Import API endpoint on January 19, 2024, then retired the Windows desktop app and Android mobile app on June 6, 2024. ([quip.com](https://quip.com/release-notes)) Quip is already shrinking, not evolving.

> [!WARNING]
> **When to start:** Now. Even if the in-product flow isn't in your tenant yet, you should be inventorying your Quip content, identifying spreadsheet-heavy documents (they will not migrate cleanly), and testing the API export path. Waiting until read-only mode means you've already lost the ability to verify migrated content against the source.

If your subscription renews annually and you're approaching your last renewal window before March 2027, your active migration window may be shorter than you think.

## What Survives the Quip to Slack Canvas Migration

Not everything makes the trip. Here's what the official path handles and what it doesn't, based on Salesforce's announced capabilities and independent technical analysis.

### Features That Migrate

| Feature | Migration Path | Notes |
|---------|---------------|-------|
| **Document content** (rich text, headings, lists, images) | In-product flow (when available) | Standard text converts directly. ([salesforceben.com](https://www.salesforceben.com/salesforce-announces-end-of-life-for-quip/)) |
| **Comments** | Quip comments → Slack threads on canvas | Canvas comments inherit Slack's full threading — a genuine UX improvement. |
| **Embedded workflows** | Slack Workflow Builder | Existing Quip workflow behavior needs to be rebuilt in Workflow Builder. |
| **Salesforce CRM data** (Customer 360, Sales Cloud, Service Cloud) | Native Slack–Salesforce integration | Live connections maintained. Note: Slack's Salesforce data-in-canvas features require Business+ or Enterprise plans. ([slack.com](https://slack.com/help/articles/45520056210579-View-and-update-Salesforce-data-in-Slack)) |

### Features That Break or Have Gaps

| Feature | Status | Why |
|---------|--------|-----|
| **Quip spreadsheets** | ❌ No full parity | Slack Canvas does not have Quip's spreadsheet engine. Simple tables may render, but formulas, cell formatting, and data-heavy grids will not migrate cleanly. ([blog.persistent.info](https://blog.persistent.info/2023/07/slack-canvas-quip.html)) |
| **@date mentions** | ❌ Not ported | Quip's `@date` inline mention type has not been carried into Slack Canvas. ([blog.persistent.info](https://blog.persistent.info/2023/07/slack-canvas-quip.html)) |
| **Quip Live Apps** (Salesforce Record, Kanban, Calendar) | ⚠️ Replaced, not migrated | Live Apps don't transfer directly. Slack has its own Salesforce integration components, but they require reconfiguration. |
| **Copy/paste fidelity** | ⚠️ Partial | Copying content from Quip and pasting into Slack Canvas does not preserve features that haven't been ported. ([blog.persistent.info](https://blog.persistent.info/2023/07/slack-canvas-quip.html)) |
| **Quip-specific debugging tools** | ❌ Not available | Pre-acquisition internal debugging tools are hidden or removed in Canvas. ([blog.persistent.info](https://blog.persistent.info/2023/07/slack-canvas-quip.html)) |

An important distinction: there is a difference between **supported target capabilities** and **automatic migration**. Salesforce has described a document conversion path, but that is not the same as promising every Quip Live App, spreadsheet, mention, or edge-case embed will become a Slack equivalent. Treat anything beyond standard document content as a pilot test case, not an assumption.

> [!WARNING]
> **The Spreadsheet Gap:** If spreadsheets are a primary Quip use case for your team, do not plan on Slack Canvas as your destination. This gap is architectural, not a feature in a backlog. Route spreadsheet-heavy content to [Coda](https://clonepartner.com/blog/blog/quip-to-coda-migration-api-limits-data-mapping-export-guide/), [Notion](https://clonepartner.com/blog/blog/quip-to-notion-migration-step-by-step-guide-api-limits/), or Excel via [SharePoint](https://clonepartner.com/blog/blog/quip-to-sharepoint-migration-the-complete-technical-guide/).

## How to Use the Official Salesforce In-Product Migration Flow

Salesforce is rolling out an in-product flow for converting Quip documents into Slack canvases. This is the path of least resistance for orgs already on Slack — if it's available in your tenant.

**Important caveat:** This flow is rolling out in phases throughout 2026. It is not yet universally available. If you don't see it in your Quip admin console, you are not behind — you need the API fallback path covered in the next section. ([salesforceben.com](https://www.salesforceben.com/salesforce-announces-end-of-life-for-quip/))

### Step 1: Audit Your Quip Workspace

Before touching any migration tool, inventory what you have:

- **Total document count** — determines whether you need the in-product flow or an API-driven approach
- **Spreadsheet-heavy documents** — flag these for alternative handling
- **Documents with Live Apps** — Salesforce Record embeds, Kanban boards, and Calendar views need separate planning
- **Folder structure and permissions** — Slack Canvas uses a channel-based permission model; Quip uses folder-based sharing. Mapping this incorrectly can expose sensitive HR or financial data to unintended audiences.

### Step 2: Separate Documents from Spreadsheets

Only send document-heavy content into the Canvas path. Anything spreadsheet-driven goes to an exception queue for routing to Coda, Notion, or SharePoint. Making this split early prevents the most common post-migration rework.

### Step 3: Pilot on Representative Content

Start with 5–10 representative documents — not your cleanest ones. Pick documents that contain comments, images, embedded data, and varied formatting. Validate:

- Rich text formatting preserved (headings, bold, lists, embedded images)
- Comments mapped to correct users
- Links between documents still resolve (or are flagged for manual update)
- Salesforce records re-authenticated correctly

### Step 4: Execute at Scale

When the pilot passes validation:

1. Access the Quip-to-Slack migration tool from your admin settings
2. Select documents or folders to migrate
3. Map Quip users to Slack workspace members
4. Choose target Slack channels or standalone canvases
5. Run the migration and review the output

Because Salesforce explicitly states that data is not automatically migrated, relying on end-users to manually click "Convert to Canvas" on a document-by-document basis is a high-risk strategy. IT teams should manage this centrally.

### Step 5: Rebuild Missing Pieces

Replace Quip Live Apps with Workflow Builder flows or Salesforce data fields in Canvas. Move spreadsheets to their alternative destination. Freeze anything that can't be migrated into an archive-only export.

> [!TIP]
> **Dependency management tools** are part of Salesforce's rollout. These admin controls help you identify and reduce your users' reliance on Quip features that won't transfer to Slack. Use them before you run the migration — not after.

## The API Export Fallback: When the In-Product Flow Isn't Available

If the in-product flow isn't in your tenant yet — or if you need more control over the extraction — the **Quip Automation API** is your way out.

Quip does not have a native bulk export button. Individual documents can be exported one at a time via the UI (as DOCX, XLSX, or PDF), but at any scale beyond ~50 documents, this is not viable. Salesforce added admin APIs for bulk PDF export to support archiving and eDiscovery, but that is useful for records retention, not a structured workspace migration with target-side mapping. ([help.salesforce.com](https://help.salesforce.com/s/articleView?id=release-notes.bulk_document_archiving_with_admin_api.htm&language=en_US&release=234&type=5))

If you need bulk, repeatable migration, you are in script territory.

### Key API Endpoints

The Quip Automation API exposes thread-centric operations (Quip treats documents, spreadsheets, and chats as "threads"):

- **Document export:** `GET /1/threads/{thread_id}/export/docx`
- **Spreadsheet export:** `GET /1/threads/{thread_id}/export/xlsx`
- **Bulk async export:** `POST /1/threads/export/async` (submit batch, poll for results)
- **Comments:** `GET /1/messages/{thread_id}`
- **PDF export:** asynchronous, can take up to 10 minutes per large thread
- **Thread metadata:** `GET /1/threads/{thread_id}`

A minimal thread read:

```bash
curl -H "Authorization: Bearer $QUIP_TOKEN" "https://platform.quip.com/1/threads/$THREAD_ID"
```

From there, you still need folder traversal (starting at the root via `GET /folders/` and recursively crawling every sub-folder), transform logic, permissions mapping, and exception handling.

### Rate Limits

The Quip Automation API enforces default limits of **50 requests per minute per user** and **750 per hour per user**, with a company-wide cap of **600 requests per minute**. The Admin API (separate from the Automation API, needed for site-wide thread discovery) is rate limited to **100 requests per minute** and **1,500 requests per hour**. ([quip.com](https://quip.com/dev/automation/documentation))

> [!WARNING]
> **Rate-limit gotcha:** Quip returns **HTTP 503** for rate-limit events, not the standard 429. Most HTTP libraries will misclassify these as server errors and either retry immediately (making the problem worse) or surface them as failures. Your extraction script must explicitly handle 503 responses as rate-limit signals with exponential backoff, or you'll end up with incomplete data and no clear indicator of what was missed.

Remember: Quip retired both the Upload/Import menu option and the Import API endpoint on January 19, 2024. ([quip.com](https://quip.com/release-notes)) If you're exporting now, assume a one-way exit and design your pipeline accordingly.

For a complete walkthrough — including the `baqup` script, third-party export tools, and comment extraction strategies — see [How to Export Data from Quip: Methods, API Limits & Migration Prep](https://clonepartner.com/blog/blog/how-to-export-data-from-quip-methods-api-limits-migration-prep/).

Once you have your content extracted to HTML/DOCX/Markdown, you can import into Slack canvases via the Slack API's canvas endpoints, or redirect to an alternative destination.

## When to Choose an Alternative Destination

Slack Canvas is the *official* path, but it's not the right path for every org. Consider an alternative if:

- **Your team doesn't live in Slack.** If Slack isn't your primary communication platform, moving documents there creates a discoverability problem. Documents need to live where people already work.
- **Spreadsheets are a core Quip use case.** Slack Canvas has no spreadsheet parity. Teams using Quip for data-heavy operational documents need a platform with real table/spreadsheet support.
- **You need standalone document management.** Slack canvases are tied to the Slack workspace. If your use case requires documents shared with external partners, embedded in portals, or used outside Slack, a different target makes more sense.
- **You're in a regulated industry requiring document-level audit trails.** Slack has enterprise audit capabilities, but the granularity differs from dedicated document management platforms.

### When to Choose Coda

If your team relied on Quip's embedded spreadsheets, live data, and interactive documents, Coda is the closest architectural match. It handles structured data natively and offers a Quip importer. Migrating Quip spreadsheets into Coda requires careful mapping — Quip's flat grids must be translated into Coda's relational tables. See [Quip to Coda](https://clonepartner.com/blog/blog/quip-to-coda-migration-api-limits-data-mapping-export-guide/).

### When to Choose Notion

If your organization wants a flexible, block-based workspace with databases and wiki-style organization, and does not rely heavily on complex formulas, Notion is a strong option. Extracting Quip's HTML and translating it into Notion's block format requires API middleware. See [Quip to Notion](https://clonepartner.com/blog/blog/quip-to-notion-migration-step-by-step-guide-api-limits/).

### When to Choose SharePoint or Confluence

If your organization has strict IT governance, data residency requirements, or an existing Microsoft/Atlassian footprint, SharePoint or Confluence are the standard enterprise targets. Be warned: moving from Quip's fluid, thread-based architecture into SharePoint's rigid Site/Library/File structure is a difficult data mapping exercise. See [Quip to SharePoint](https://clonepartner.com/blog/blog/quip-to-sharepoint-migration-the-complete-technical-guide/).

Do not pick Slack Canvas just because Salesforce prefers it. If spreadsheets are primary, that is the fastest way to turn an official migration path into a post-migration rework project.

## Compliance and Audit Considerations

For regulated industries — financial services, healthcare, government — the migration path matters as much as the destination.

**Audit trail preservation:** The in-product flow preserves a Salesforce-controlled chain of custody for your content. If your compliance requirements mandate demonstrating *how* data was moved and *by whom*, the official flow has an advantage over custom API extraction where you own the audit logging. That said, the deep audit trail — granular history of who edited which paragraph on what date — may not survive the transition in a format acceptable to auditors.

**Data residency:** Verify that your Slack workspace's data residency settings align with your regulatory requirements before migrating. Quip data may currently reside in a different region than your Slack instance.

**Retention policies:** Slack's message and canvas retention policies are separate from Quip's. Configure Slack's retention settings to match your compliance obligations *before* migrating — otherwise, migrated content could be auto-deleted by Slack's default retention rules. Slack Enterprise plans provide Discovery API, Audit Logs API coverage, legal holds, and data residency controls for canvases. ([slack.com](https://slack.com/help/articles/15708101445011-How-data-management-features-apply-to-canvases-and-lists))

**eDiscovery:** Quip's Admin API supports event logging (`export-thread`, `print-document`, etc.) for compliance workflows. Post-migration, your eDiscovery tooling needs to shift to Slack's Discovery API or a third-party provider. Plan this transition alongside the content migration, not after.

If your compliance framework (SOC 2, HIPAA, SEC 17a-4) requires strict data retention:

- **Do not rely solely on the UI conversion.** Extract a cold-storage archive using the Quip Automation API — export all threads as PDF or HTML alongside a JSON payload containing full metadata and edit history.
- **Store immutably.** Place this archive in an immutable S3 bucket or a compliant SharePoint Document Library before the Quip tenant enters the Blocked Logins phase.
- **Act before deletion.** Once the tenant hits the data deletion phase, Salesforce will permanently purge the data. There is no recovery.

For orgs where compliance requirements make the migration particularly sensitive, [Quip to SharePoint](https://clonepartner.com/blog/blog/quip-to-sharepoint-migration-the-complete-technical-guide/) may be a better fit — SharePoint's compliance center, sensitivity labels, and retention policies are purpose-built for regulated document management.

## Execution and Next Steps

Salesforce has made its direction clear: Slack canvases are the official landing zone for Quip documents. The trap is assuming that official means automatic or complete. It does not.

The decision tree:

1. **Your org is on Slack and the in-product flow is available → Use it.** Lowest-friction path, Salesforce-supported, preserves the most metadata.
2. **Your org is on Slack but the in-product flow isn't in your tenant yet → Use the API export path.** Extract via the Quip Automation API, stage content locally, and import into Slack canvases. The wind-down clock runs whether or not the official tool has shipped to your tenant.
3. **Your org isn't primarily on Slack → Choose an alternative destination.** Notion, SharePoint, or Coda each handle different Quip use cases better than Slack Canvas.
4. **You have a large workspace (1,000+ documents), spreadsheet-heavy content, or compliance constraints → Get help.** API rate limits, the 503 rate-limit misclassification, incomplete comment extraction, and Live App dependencies make large-scale Quip migrations error-prone without production-grade tooling.

The March 2027 deadline feels distant, but enterprise migrations require months of planning, security reviews, and user training. The teams that will have the cleanest exit are the ones that separate documents from spreadsheets early, pilot the in-product flow on real content, and keep an API or archive plan in reserve.

> **Need a Quip exit plan before the March 2027 deadline?** We handle Quip extraction, mapping, and migration — including the spreadsheet gap, 503 rate-limit issues, and compliance archiving that the official tools don't cover. [See our Quip migration service →](https://clonepartner.com/blog/knowledge-base-migration/quip)
>
> [Talk to us](https://cal.com/clonepartner/meet?duration=30)

## Frequently asked questions

### When is Quip being retired by Salesforce?

Salesforce is retiring all Quip products (Starter, Advanced, and Plus). Subscriptions cannot be renewed after March 1, 2027. After your subscription expires, a three-phase wind-down begins: 90 days read-only, 90 days blocked logins, then approximately 30 days of permanent data deletion.

### Is Quip data automatically migrated to Slack Canvas?

No. Salesforce has explicitly stated that Quip data is not automatically migrated. You must use the in-product migration flow (rolling out throughout 2026), the Quip Automation API, or a third-party service to move your data before the wind-down phases begin.

### Do Quip spreadsheets migrate to Slack Canvas?

Not with full parity. Slack Canvas does not have Quip's spreadsheet engine. Simple tables may render, but formulas, cell formatting, and data-heavy grids will not migrate cleanly. If spreadsheets are a core use case, consider alternatives like Coda, Notion, or SharePoint.

### Is Slack Canvas built on Quip technology?

Yes. Slack Canvas was built directly on the Quip codebase. Slack's CPO confirmed that Canvas takes Quip's collaborative components and integrates them natively into Slack. An ex-Quip engineer's analysis confirmed the shared DOM structure, CSS classes, and Python backend.

### Can I bulk export all data from Quip?

There is no native bulk export button in Quip. Individual documents can be exported via the UI, but at scale you must use the Quip Automation API or admin bulk-PDF archiving APIs. Salesforce does not provide a self-serve workspace migration wizard.