---
title: "Document360 to Slack Canvas Migration | ClonePartner"
description: "Document360 to Slack Canvas: Document360 variables and snippets appear as unresolved merge code tokens (e.g., {{variable_name}}) when retrieved via the API…"
source: Document360
target: Slack Canvas
canonical: "https://clonepartner.com/migrate/document360-to-slack-canvas"
---

# Document360 → Slack Canvas migration

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

## Why teams migrate from Document360 to Slack Canvas

There is no native migration path from Document360 to Slack Canvas. The two platforms operate on fundamentally different data models: Document360 is a structured, often public-facing knowledge base with hierarchical categories (up to six levels deep), reader SSO, custom domains, and SEO capabilities, while Slack Canvas is internal collaboration content gated entirely by workspace membership and channel-level permissions. The migration requires custom scripting against both APIs, with significant pre-processing to resolve content reuse elements — variables, snippets, and glossary terms — that are excluded from Document360's ZIP export and appear as unresolved tokens via the API. Additionally, the six-level Document360 category hierarchy must be manually flattened or split across Slack channels and canvas tabs, as Slack Canvas supports only h1 through h3 heading levels.

## Key migration challenges

- **Content Reuse Token Resolution** — Document360 variables and snippets appear as unresolved merge code tokens (e.g., {{variable_name}}) when retrieved via the API, requiring a migration script to pre-fetch all variables and snippet content, then perform find-and-replace substitution across all article bodies before conversion to canvas markdown.
- **Category Hierarchy Flattening** — Document360 supports up to six nested subcategory levels, but Slack Canvas only renders h1 through h3 headings, requiring every knowledge base branch deeper than three levels to be either collapsed into bold text and nested lists or split across multiple canvases and channel tabs.
- **Reader Access Model Mismatch** — Document360 supports granular per-category reader groups enforced via SAML, OpenID, or JWT SSO, while Slack Canvas access is controlled exclusively through workspace membership and channel-level sharing, meaning external customers, partners, and anonymous visitors lose access entirely.
- **Public URL and SEO Retirement** — All public Document360 article URLs and associated SEO metadata — meta titles, descriptions, and redirect rules — become permanently invalid when content moves to Slack, since canvases are hosted at slack.com URLs and are not indexed by search engines.
- **Slack Plan Tier Dependency** — Programmatic creation of standalone canvases and their attachment to channels as tabs requires a paid Slack plan (Pro, Business+, or Enterprise Grid), making migration architecture design dependent on the organization's Slack subscription tier before scripting begins.
- **Glossary Auto-Highlighting Loss** — Document360's glossary feature automatically highlights the first occurrence of defined terms in published articles with hover-over definitions, a capability with no equivalent in Slack Canvas, requiring a deliberate decision to either drop inline definitions, create a standalone glossary canvas, or script parenthetical definitions into canvas content.

## Entity mappings

- **Article** (Document360) → **Standalone Canvas** (Slack Canvas)
- **ArticleContent** (Document360) → **Canvas Content (Markdown)** (Slack Canvas)
- **Category** (Document360) → **Channel Canvas** (Slack Canvas)
- **Project** (Document360) → **Channel** (Slack Canvas)
- **Tag** (Document360) → **NotAvailable** (Slack Canvas)
- **TeamAccount** (Document360) → **Canvas Access Grant** (Slack Canvas)
- **Reader** (Document360) → **Canvas Access Grant** (Slack Canvas)
- **ReaderGroup** (Document360) → **Canvas Access Grant** (Slack Canvas)
- **ContentSnippet** (Document360) → **Canvas Content (Markdown)** (Slack Canvas)
- **Glossary** (Document360) → **Table** (Slack Canvas)
- **CustomPage** (Document360) → **Standalone Canvas** (Slack Canvas)
- **Drive** (Document360) → **File Attachment** (Slack Canvas)
- **Translation** (Document360) → **NotAvailable (Partial Workaround Possible)** (Slack Canvas)
- **Analytics** (Document360) → **NotAvailable** (Slack Canvas)
- **Redirect** (Document360) → **NotAvailable** (Slack Canvas)

## What breaks during migration

- **Published Articles** [Workaround] — Published articles can be extracted via the Document360 API but require status filtering to exclude drafts and unpublished content, plus HTML-to-markdown conversion before ingestion into Slack Canvas.
- **Draft Articles** [Breaks] — The Document360 article list endpoint returns drafts by default alongside published content, and failing to explicitly filter by status risks migrating incomplete or unapproved content into Slack workspaces.
- **Content Variables** [Breaks] — Variable merge codes are excluded from ZIP exports and appear as unresolved literal tokens via the API, requiring a pre-migration script to fetch all variables and perform substitution before any content is written to Slack Canvas.
- **Snippets (Reusable Blocks)** [Breaks] — Snippets must be fully expanded inline during extraction since Slack Canvas has no equivalent reusable block concept, permanently breaking the single-source-of-truth relationship and requiring manual updates to every canvas that originally contained a given snippet.
- **Glossary Terms** [Workaround] — Glossary auto-highlighting silently degrades to plain text in Slack Canvas with no error or warning, and the full glossary must be pre-exported via API before Document360 is decommissioned to avoid permanent data loss.
- **Category Hierarchy and Article Order** [Breaks] — Document360's up-to-six-level category tree has no structural equivalent in Slack Canvas, and the API-returned order field must be manually preserved through heading sequence and canvas tab naming conventions since Slack Canvas has no native ordering concept.
- **Reader Groups and Permissions** [Breaks] — Document360's per-category reader group access controls cannot be replicated in Slack Canvas, and the closest operational equivalent — private channels — requires a deliberate remapping of every reader group before migration to avoid unintended access exposure.
- **Media Files and Images** [Workaround] — Media files are included in Document360's ZIP export and referenced by URL in article HTML, but those URLs must be re-hosted or re-uploaded since Document360-hosted media will become inaccessible after the platform is decommissioned.
- **Article Redirect Rules** [Breaks] — Document360 redirect rules (ends-with, replace-with) have no equivalent in Slack and all associated public URLs will return errors after migration, requiring an external redirect strategy such as server-side 301 redirects or a landing page before the Document360 domain is retired.
- **Multilingual Content** [Workaround] — Slack Canvas has no built-in language selector comparable to Document360's multilingual knowledge base support, requiring each language variant to be maintained as a separate canvas or clearly labeled sibling canvas with no native switching mechanism for readers.

## 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: [Document360 to Slack Canvas Migration: The Audience Shift Guide](https://clonepartner.com/blog/document360-to-slack-canvas-migration-the-audience-shift-guide/).

## Frequently asked questions

### Can I migrate a public Document360 knowledge base to Slack Canvas without losing external access?

No. Slack Canvas is gated by workspace membership. Any reader without a Slack account in your workspace — external customers, partners, anonymous visitors — loses access entirely. There is no public URL or reader SSO equivalent in Slack Canvas.

### What happens to Document360 variables and snippets during migration?

Variables and snippets are excluded from Document360's ZIP export and may appear as unresolved tokens in API-fetched article bodies. You must pre-fetch all variables and snippets via the API, then find-and-replace every merge code and expand snippet references inline before converting content to canvas markdown.

### Does Slack Canvas support the same heading levels as Document360?

No. Slack Canvas supports h1 through h3 only. Document360 categories can nest up to six levels deep. You need to flatten the hierarchy — either collapsing levels 4–6 into bold text or lists, or splitting content across multiple channels and canvas tabs.

### What is the Document360 API rate limit for migration?

Professional and Business plans allow 60 requests per minute per API token. Enterprise plans allow 100 requests per minute. Tokens are project-scoped, so multi-project migrations require separate tokens with independent rate-limit budgets. The bulk export API is capped at 2 calls per day.

### What happens to Document360 redirect rules after cancellation?

Document360 redirect rules live inside the platform. Once you cancel your subscription, the custom domain and all redirect rules stop working. You need to set up redirects at the DNS or proxy level before decommissioning Document360 if you want to avoid 404s on previously indexed URLs.

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