---
title: "Guru to Slack Canvas Migration | ClonePartner"
description: "Guru to Slack Canvas: Guru's verificationState, verifier assignments, and interval-based review workflow have no equivalent metadata layer in Slack Canvas…"
source: Guru
target: Slack Canvas
canonical: "https://clonepartner.com/migrate/guru-to-slack-canvas"
---

# Guru → Slack Canvas migration

Guru to Slack Canvas migration — documents moved in bulk and attached to the channels your team already works in.

## Why teams migrate from Guru to Slack Canvas

Migrating from Guru to Slack Canvas requires a fully custom, multi-stage pipeline because no native migration path exists between the two platforms. The most significant structural incompatibility is Guru's trust model: every Guru Card carries a verificationState, assigned verifier, verification interval, and staleness signals, none of which have any equivalent metadata field in Slack Canvas, which is a simple Markdown document surface. Guru's **Collection → Folder → Card** hierarchy also does not map cleanly to Slack's model, where a channel supports exactly one channel canvas, forcing cards to become standalone canvases linked from an index page. Custom engineering is required to extract Guru's HTML card content, convert it to Slack's restricted Markdown subset, re-host all media assets on Slack infrastructure, reconstruct permission boundaries using canvases.access.set, and respect Slack API structural limits including the 1 MiB document size cap, h3 heading ceiling, and 300-cell table limit.

## Key migration challenges

- **Trust State Has No Destination** — Guru's <code>verificationState</code>, verifier assignments, and interval-based review workflow have no equivalent metadata layer in Slack Canvas, requiring teams to either abandon governance entirely or implement fragile manual conventions.
- **Hierarchy-to-Channel Model Mismatch** — Guru's multi-level Collection → Folder → Card hierarchy cannot map directly to Slack's channel model because each channel supports exactly one channel canvas, preventing any folder-per-channel approach that contains multiple cards.
- **HTML-to-Markdown Content Conversion** — Guru stores card content as HTML, but Slack Canvas only accepts a restricted Markdown subset with headings capped at h3, requiring a custom conversion pipeline that must handle semantic loss for unsupported HTML elements.
- **Asset Re-hosting and Performance Overhead** — All images and embedded media referenced in Guru cards must be downloaded and re-uploaded to Slack's infrastructure before canvas creation, adding latency and complexity proportional to the size of the asset library.
- **Permission Boundary Reconstruction** — Guru's <code>shareStatus</code> values (<code>TEAM</code>, <code>COLLECTION</code>, <code>PRIVATE</code>) must be manually re-mapped using <code>canvases.access.set</code> with pre-provisioned Slack user groups, and any omission risks exposing previously restricted content to the entire workspace.
- **Slack API Structural and Rate Limits** — Slack Canvas enforces a 1 MiB per <code>document_content</code> object limit, a 300-cell table cap, and a single channel canvas per channel constraint, while Guru's API caps extraction at 50 results per page and returns HTTP 429 responses under sustained request bursts.

## Entity mappings

- **Card** (Guru) → **Standalone Canvas** (Slack Canvas)
- **Card Version** (Guru) → **Canvas Content (Markdown)** (Slack Canvas)
- **Card Comment** (Guru) → **Canvas Content (Appended Section) / Slack Channel Message** (Slack Canvas)
- **Card Attachment** (Guru) → **File Attachment** (Slack Canvas)
- **Board** (Guru) → **Channel Canvas** (Slack Canvas)
- **Collection** (Guru) → **Channel** (Slack Canvas)
- **Folder** (Guru) → **Slack Canvas (Nested Structure / Channel Organization)** (Slack Canvas)
- **Tag** (Guru) → **NotAvailable (Workarounds Only)** (Slack Canvas)
- **Team Member** (Guru) → **Canvas Access Grant** (Slack Canvas)
- **Group** (Guru) → **Canvas Access Grant** (Slack Canvas)
- **User** (Guru) → **Canvas Access Grant** (Slack Canvas)
- **Verification** (Guru) → **NotAvailable (Partial Workaround Possible)** (Slack Canvas)
- **Custom Field** (Guru) → **Table** (Slack Canvas)
- **Card Relation** (Guru) → **Canvas Content (Markdown)** (Slack Canvas)

## What breaks during migration

- **Verification Metadata** [Breaks] — Fields including <code>verificationState</code>, <code>verifier</code>, <code>verificationInterval</code>, and <code>lastVerified</code> have no target field in Slack Canvas and will be permanently lost unless manually embedded as a prose header block in each migrated canvas.
- **Card Content (HTML)** [Workaround] — Card HTML must be converted to Slack's restricted Markdown subset, and any HTML elements unsupported by Canvas will be lost or degraded during conversion, requiring review of the output for semantic accuracy.
- **Folder and Collection Hierarchy** [Workaround] — The three-level Collection → Folder → Card structure must be flattened and re-expressed as standalone canvases linked from an index channel canvas, losing native positional hierarchy and nested navigation.
- **Images and Embedded Media** [Workaround] — All media assets must be re-hosted on Slack's infrastructure before canvases are created, and any assets that fail to upload will result in broken references in the migrated canvas content.
- **Access Permissions (shareStatus)** [Breaks] — Guru's <code>COLLECTION</code>-scoped cards require pre-provisioned Slack user groups and explicit <code>canvases.access.set</code> calls; skipping this step silently exposes restricted content to the entire Slack workspace.
- **Tags and Custom Fields** [Workaround] — Guru tags and custom fields have no structured field model in Slack Canvas and must be flattened into prose or index rows at the top of each standalone canvas, losing machine-readability and filterability.
- **Private Cards** [Direct] — Cards with <code>shareStatus: PRIVATE</code> can be migrated as unshared standalone canvases visible only to the creating user, which is a reasonable approximation of the original draft state.
- **Card Titles and Metadata** [Direct] — Card titles map directly to canvas titles and the core identifier fields are preserved during extraction from the Guru API's card object.
- **Large Canvases Approaching Size Limit** [Breaks] — Guru cards or folders whose combined content approaches or exceeds Slack's 1 MiB <code>document_content</code> limit will fail on creation and must be split into multiple canvases before import, requiring pre-migration size analysis.
- **Extraction Completeness via Pagination** [Workaround] — Guru's API caps results at 50 per request and uses cursor-based <code>Link</code> header pagination, so any extraction script that does not correctly follow all <code>rel=next-page</code> cursors will silently produce an incomplete card set.

## 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: [Guru to Slack Canvas Migration: API Limits & Trust State](https://clonepartner.com/blog/guru-to-slack-canvas-migration-api-limits-trust-state/).

## Frequently asked questions

### Can Slack Canvas replace Guru's verification workflow?

No. Slack Canvas has no verification status, no assigned verifier, no review interval, and no trust indicator. You can approximate review cadence with Slack reminders or Workflow Builder triggers, but there is no built-in mechanism to mark a canvas as verified or flag it as stale.

### How many channel canvases can a Slack channel have?

Exactly one. Calling conversations.canvases.create a second time on the same channel returns a channel_canvas_already_exists error. Additional content must go into standalone canvases created via canvases.create and shared or tabbed to the channel.

### What Guru card data is lost when migrating to Slack Canvas?

Verification state, verifier assignments, verification interval, trust indicators, card version history, favorites, and view counts are lost entirely. Tags and custom fields can only be preserved as plain text in the canvas body or an index table — not as structured, filterable metadata.

### Does the Guru API return card content as HTML or Markdown?

HTML. The card content field contains rendered HTML. You must convert this to the Canvas-supported Markdown subset, which limits headings to h1–h3, caps tables at 300 cells, and does not support iframes, Block Kit, or inline CSS.

### How do you handle Guru images when migrating to Slack Canvas?

Download each image from the Guru CDN (content.api.getguru.com) using an authenticated GET request, upload it to Slack via files.getUploadURLExternal and files.completeUploadExternal, then reference the Slack-hosted file in the canvas Markdown. Do not write canvases with Guru CDN URLs — they break when Guru access is revoked.

## 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 Guru → Slack Canvas migration.