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.
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.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
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.
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.
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, Notion, or Excel via SharePoint.
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.
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.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Decide what content deserves to move before you plan how to move it.
Objective A content inventory with a keep/rewrite/retire decision on every article and an agreed URL strategy.
Keep these open
-
Inventory all content in Quip
Count articles, categories, attachments, images and embedded media, and pull page views and last-updated dates for each article. Usage data is what makes the next decision defensible rather than political.
Data Profiler Get real record counts instead of estimating from memory -
Make a keep, rewrite or retire call on every article
Most knowledge bases are half stale. Migrating everything imports the staleness and doubles the work; use views and last-updated to triage, and get the owning team to confirm. This usually removes 30-50% of scope.
Migrating stale content is the most common knowledge-base migration mistake — it costs effort and actively degrades the new site.
-
Agree the URL and redirect strategy
Decide the Slack Canvases URL structure and whether you can serve 301 redirects from the old paths. Public help centres carry real search traffic and inbound links; losing it is a measurable commercial impact.
Without 301 redirects from old article URLs you lose accumulated search ranking and every external link and bookmark breaks.
-
Map the information architecture
Document the current category tree and design the target one, checking whether Slack Canvases supports your nesting depth. Deeply nested hierarchies frequently have to be flattened, which changes navigation for everyone.
-
Confirm permissions, audiences and localisation scope
Establish which content is public, internal or restricted, and how Slack Canvases models that. Then confirm how many locales you have and whether translation relationships between articles survive the move.
Quip → Slack Canvases specifics
- 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.
Don't move on until
- Full content inventory with page views and last-updated dates
- Keep / rewrite / retire decision recorded per article
- URL and redirect strategy agreed with whoever owns SEO
02 Data Audit Audit the markup, the links and the assets — that is where KB migrations break.
Objective A content export with markup, internal links and every embedded asset accounted for.
Keep these open
-
Export content and assess markup fidelity
Export articles in the richest format available and inspect what survived: tables, code blocks, callouts, nested lists, anchors and embedded video. Rich formatting is where fidelity is lost, and it is lost quietly.
HTML-to-Markdown conversion routinely mangles nested lists, tables and code blocks. Inspect the output rather than trusting the converter.
Data Profiler Profile the Quip export for nulls, outliers and type drift -
Inventory every internal link and cross-reference
Extract all internal links, anchor links and article cross-references. These break by default: the target URL structure differs, so every internal link needs rewriting as part of the load, not afterwards.
Internal links left pointing at old URLs turn the new knowledge base into a maze of 404s on day one.
-
Inventory images, attachments and embedded media
List every asset with its URL, size and type, and confirm each still resolves. Assets hosted on the old platform's CDN will 404 the moment you decommission it, so they must be rehosted, not referenced.
Images referenced from the source platform's CDN break when the old account closes. Download and rehost every asset.
-
Find and fix broken links and orphans
Crawl for existing broken internal and external links, and find articles no category links to. Fix them before migrating — a migration is a bad time to discover pre-existing rot.
-
Check for PII and internal information in public content
Scan for customer names, internal hostnames, credentials in code samples and screenshots containing real data. Republishing these on a public help centre is a disclosure, and screenshots are the usual culprit.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Normalise metadata
Standardise authors, tags, timestamps to UTC, and locale codes. Author mapping needs a decision for people who have left — attribution to a deleted user usually fails the import.
Quip → Slack Canvases specifics
- Total document count
- determines whether you need the in-product flow or an API-driven approach
- 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.
- 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.
- 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.
Don't move on until
- Content exported with markup fidelity assessed
- Every internal link and asset reference inventoried
- Broken links and missing assets fixed or logged
03 Field Mapping Map structure, metadata, permissions and — above all — URLs.
Objective A mapping covering article fields, taxonomy, permissions and a complete old-to-new URL map.
Keep these open
-
Map the article schema
Map title, body, excerpt, author, dates, status, tags, SEO metadata and any custom properties. Confirm which fields Slack Canvases lets you set on import versus which it computes — computed dates are a common surprise.
Schema Mapper Match Quip fields to Slack Canvases by uploading both schemas -
Map the taxonomy and hierarchy
Map categories, sections and tags to the target structure, resolving any nesting-depth limit explicitly. If you must flatten, decide how the lost level is preserved — usually as a tag or a title prefix.
JSON to CSV Converter Flatten nested API responses into a reviewable sheet -
Map permissions and audience segmentation
Map public, logged-in, and role-restricted visibility to Slack Canvases's model. Verify the mapping deliberately: internal content accidentally published publicly is the highest-severity failure in this whole category.
Permission mapping errors publish internal documentation to the open web. Verify visibility on every restricted article after load.
-
Build the complete old-to-new URL map
Produce a row per article mapping the old URL to the new one, then confirm exactly where the 301s will be served — Slack Canvases, a CDN, or your own web layer. Without this artifact the redirect step cannot be executed at all.
-
Define the markup conversion and link-rewrite rules
Specify how each markup construct converts and how internal links are rewritten using the URL map. Write it as a repeatable transform, not manual edits — you will run it more than once.
Data Format Converter Reshape the export into the format Slack Canvases's importer expects -
Plan localisation and freeze the spec
Confirm how translated articles link to their source language in Slack Canvases, then version and sign off the mapping spec.
Don't move on until
- Article schema and taxonomy mapped
- Permission and audience model mapped to target equivalents
- Complete URL map produced and redirect method confirmed
04 Test Migration Pilot the hardest articles, then read them.
Objective A pilot load whose formatting, links, assets and search all hold up under human review.
Keep these open
-
Configure Slack Canvases with the agreed structure
Create the category tree, permission groups, locales and branding before loading. Articles loaded before their categories exist land uncategorised and have to be moved by hand.
-
Pick the most difficult articles as the pilot
Choose 20-50 articles for difficulty: the longest, the most heavily formatted, ones with tables and code blocks, deep internal linking, many images, embedded video, restricted visibility, and non-Latin scripts. Easy articles prove nothing.
-
Run the conversion and load with link rewriting
Apply the markup conversion, rewrite internal links from the URL map, upload and re-reference assets, then load. Log every conversion warning rather than suppressing it.
-
Read every pilot article side by side
Open source and target together and compare rendering. This step is manual on purpose: no automated check catches a table that collapsed into a paragraph or a code block that lost its indentation.
-
Click every link and load every asset
Verify each internal link resolves, each image loads from the new host, each attachment downloads and each embed plays. Assets still served from the old CDN are the defect that surfaces only after decommissioning.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Test search and permissions
Search for known terms and confirm the right articles rank, then verify every restricted pilot article is invisible to an anonymous browser. Test permissions from a logged-out session, not an admin one.
Don't move on until
- Complex articles render correctly with formatting intact
- Every internal link and asset in the pilot resolves
- Search returns sensible results for the pilot content
05 Cutover Publish, redirect, and keep the search traffic.
Objective All in-scope content live in Slack Canvases with redirects serving and search engines informed.
Keep these open
-
Load the full content set ahead of the switch
Run the full conversion and load into Slack Canvases, unpublished or on a staging domain. Content migration differs from data migration here: you can stage the whole thing before anyone sees it.
-
Publish the runbook with the redirect step first-class
Sequence the freeze, final delta, publish, redirect activation, sitemap submission and link updates, with owners for each. Redirect activation is the step with lasting commercial consequences, so it gets explicit ownership.
-
Freeze editing and migrate the delta
Stop editing in Quip, then convert and load anything changed since the full load. Announce the freeze to every team that publishes — content teams are used to editing whenever they like.
-
Publish and verify permissions live
Publish the content set, then immediately verify restricted articles are not publicly reachable using an anonymous session. Do this before announcing the new site, not after.
Verify restricted content from a logged-out browser. An admin session will show you everything and tell you nothing.
Migration Validation Tool Confirm the final delta landed before you reopen -
Activate 301 redirects and submit the sitemap
Turn on the redirects from the URL map, then spot-check a sample of high-traffic old URLs and confirm each returns 301 to the right article. Submit the new sitemap and keep the old one reachable until search engines have recrawled.
Redirect chains and redirect loops both leak ranking. Verify each redirect resolves in a single hop.
-
Repoint in-product and support links
Update help links embedded in your product, in support macros, in email templates and in onboarding material. These are the links your existing customers actually use, and they are easy to forget.
Don't move on until
- All content loaded, categorised and correctly permissioned
- 301 redirects live and verified from a sample of old URLs
- Sitemap submitted and support links repointed
06 Validation Watch traffic, links and search rankings for weeks, not hours.
Objective Verified content completeness, healthy redirects, and search traffic recovered to baseline.
Keep these open
-
Reconcile content counts and assets
Compare article counts by category and status, plus asset counts, against source. Confirm every article in the keep list is present and every retired one genuinely is not.
Migration Validation Tool Reconcile Quip and Slack Canvases record-for-record -
Crawl the new site for broken links and assets
Run a full crawl for 404s, broken images and missing attachments, and fix everything it finds. Repeat the crawl after the fixes rather than assuming they worked.
-
Verify the redirects at scale
Test every mapped old URL for a single-hop 301 to the right destination. Chains and loops both leak ranking and are invisible unless you check the whole map, not a sample.
-
Monitor organic traffic and rankings for four to eight weeks
Track organic sessions, impressions and rankings for your top articles against baseline. A dip in the first two weeks is normal; one that has not recovered by week six is a redirect or indexing problem to investigate.
Do not decommission the old platform until search traffic has recovered — you may still need the old URLs to diagnose a ranking loss.
-
Verify search, permissions and feedback loops
Confirm on-site search returns good results for real queries, re-verify restricted content from a logged-out session, and check article feedback and analytics are collecting.
-
Sign off and decommission on a delay
Get acceptance against the Discovery criteria, keep Quip available read-only until traffic has recovered, take a final export, and only then close the account.
Don't move on until
- Article counts reconciled and no broken links remain
- Redirects returning 301 with no chains or loops
- Organic traffic recovered to within tolerance of baseline
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Feature Migration Path
| Quip field | Slack Canvases field | Notes |
|---|---|---|
| Document content (rich text, headings, lists, images) | In-product flow (when available) | Standard text converts directly. (salesforceben.com) |
| 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) |
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
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.