--- title: "Quip to Slack Canvas Migration | ClonePartner" description: "Quip to Slack Canvas: Canvas tables cap at 300 cells and carry no formulas, so spreadsheet threads need a separate destination such as Box, SharePoint or Drive." source: Quip target: Slack Canvas canonical: "https://clonepartner.com/migrate/quip-to-slack-canvas" --- # Quip → Slack Canvas migration Quip to Slack Canvas migration — every document converted in bulk and attached to the right channel, with spreadsheets routed somewhere that can hold them. ## Why teams migrate from Quip to Slack Canvas Salesforce ships a native Quip-to-Canvas converter, and Slack states plainly that **bulk document conversion is not supported**. It moves one document at a time, and each converted Quip document becomes read-only afterwards. It also creates every canvas as a **standalone** document rather than attaching it to a channel, so migrated content lands where nobody goes looking for it. A Slack channel holds exactly one channel canvas, so per-document channel canvases are not an option at volume. Canvas was built on the Quip codebase, which makes the gaps deliberate scope rather than a backlog. Spreadsheets, Live Apps and @date mentions have no equivalent, and tables cap at **300 cells** against a **1 MiB** markdown ceiling per canvas. ## Key migration challenges - **No Bulk Conversion** — Slack states that bulk document conversion is not supported, so the native flow converts one document at a time and leaves each Quip original read-only. - **Canvases Land Unattached** — The converter produces standalone canvases with no channel. Placing them needs canvases.access.set, which accepts at most 20 channels per call. - **No Spreadsheet Engine** — Canvas tables cap at 300 cells and carry no formulas, so spreadsheet threads need a separate destination such as Box, SharePoint or Drive. - **Rate Limit Choreography** — Quip bulk export caps at 36,000 documents per hour and signals throttling with HTTP 503 rather than 429, so ordinary retry logic misreads it as a server error. - **Live Apps Have No Target** — Kanban boards, calendars and Salesforce record embeds have no canvas equivalent, and Block Kit is unsupported inside canvases, so each one is rebuilt rather than moved. ## Entity mappings - **Document** (Quip) → **Canvas** (Slack Canvas) - **Spreadsheet** (Quip) → **Not Available** (Slack Canvas) - **Live Apps (Structured Data)** (Quip) → **Not Available** (Slack Canvas) - **@date Mention** (Quip) → **Not Available** (Slack Canvas) - **Slide** (Quip) → **Canvas** (Slack Canvas) - **Folder** (Quip) → **Channel** (Slack Canvas) - **Thread Content (HTML)** (Quip) → **Canvas Markdown** (Slack Canvas) - **Thread Members** (Quip) → **Canvas Access Grant** (Slack Canvas) - **Folder Members** (Quip) → **Channel Membership** (Slack Canvas) - **Messages (Comments)** (Quip) → **Thread Message** (Slack Canvas) - **Annotations** (Quip) → **Not Available** (Slack Canvas) - **Blob (Attachment)** (Quip) → **Uploaded File** (Slack Canvas) - **User** (Quip) → **User** (Slack Canvas) ## What breaks during migration - **Spreadsheets** [Breaks] — No spreadsheet engine in Canvas; formulas and cell formatting are lost and the content needs a file store instead - **Live Apps** [Breaks] — Kanban, Calendar and Salesforce Record embeds have no canvas equivalent and must be rebuilt as Workflow Builder flows - **Inline Annotations** [Breaks] — Anchored to Quip section IDs that do not survive export, and no API anchors a comment to a position in a canvas - **Channel Placement** [Breaks] — The native converter attaches nothing; without a mapping pass every canvas is orphaned from the team that owns it - **@date Mentions** [Workaround] — The inline date mention type was never ported to Canvas and degrades to plain text - **Attachments** [Workaround] — Must be re-uploaded and relinked; images need a Slack permalink or a public URL rather than an embedded binary - **Folder Hierarchy** [Workaround] — Canvas has no folders, so nesting collapses into channel mapping plus a naming convention ## What we migrate ### Migration Filter - **Time Range** — Migrate articles created or updated within a specific period - **Language & Locale** — Migrate specific language versions or translations only - **Category Selection** — Select specific sections, folders, or categories to migrate - **Publication Status** — Filter by published, draft, archived, or internal-only articles ### Data Types - **Tags & Metadata** — SEO settings, search labels, author attribution, and article tags - **Articles & Content** — Core help articles including HTML formatting and inline images - **Media & Attachments** — All downloadable files, PDFs, and media assets embedded in articles - **Categories & Hierarchy** — Full folder structure with sections, sub-sections, and parent categories ## Complete technical guide For a deep-dive into the technical process, data mapping, and step-by-step migration workflow, read our full guide: [Quip to Slack Canvases Migration: The Official Salesforce Path](https://clonepartner.com/blog/quip-to-slack-canvases-migration-the-official-salesforce-path/). ## Frequently asked questions ### Does the Quip to Slack Canvas converter support bulk migration? No. Slack states that bulk document conversion is not supported, so the native converter moves one document at a time, and each converted Quip document becomes read-only afterwards. Above a few hundred documents the only practical route is the Quip Automation and bulk export APIs feeding the Slack canvas APIs. ### What does not transfer from Quip to Slack Canvas? Spreadsheets, Live Apps and @date mentions. Canvas has no spreadsheet engine, so formulas and data grids are lost; Live Apps such as Kanban boards, calendars and Salesforce record embeds have no canvas equivalent; and the @date mention type was never ported. Copying and pasting does not recover any of them. ### Can migrated canvases be attached to a specific Slack channel? Not by the native converter, which leaves every canvas standalone and unattached. A channel holds exactly one channel canvas, so at volume the working pattern is a channel canvas as an index plus standalone canvases granted to that channel with canvases.access.set, which takes up to 20 channels per call. ### What happens to Quip spreadsheets during the migration? They need a different destination. Canvas tables cap at 300 cells and hold no formulas or cell formatting, so spreadsheet threads are exported as XLSX through the Quip export endpoint and loaded into a file store such as Box, SharePoint or Drive, with links back from the canvas that replaced the document. ### When does Quip shut down? Quip subscriptions cannot be renewed after March 1, 2027, and free user access ends March 31, 2027. Once a subscription expires the site is read-only for 90 days, logins are blocked for a further 30, and deletion then takes roughly 30 days. Nothing is migrated automatically. ## Get a fixed-price quote [Talk to an engineer](https://clonepartner.com/talk-to-us?duration=30&utm_source=xtoy&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click) about your Quip → Slack Canvas migration.