--- title: "Migrate from Confluence to Quip | ClonePartner" description: "There is no native import path from Confluence to Quip. Quip retired its import tool in January 2024, and Salesforce has announced Quip's full retirement with s" source: Confluence target: Quip canonical: "https://clonepartner.com/migrate/confluence-to-quip/" --- # Confluence → Quip migration Seamless Confluence to Quip migration — all records moved with accuracy and care. ## Why teams migrate from Confluence to Quip There is no native import path from Confluence to Quip. Quip **retired its import tool** in January 2024, and Salesforce has announced Quip's full retirement with subscriptions ending **March 2027**. Confluence stores content in a **macro-rich XHTML storage format** with strict Space → Page Tree hierarchies. Quip uses **tag-like folders** and flat document threads with no macro system and a 1 MB content cap per request. The only viable path is the Quip Automation API with custom **503-aware retry logic**, programmatic macro translation, and a two-pass internal link rewriting workflow. ## Key migration challenges - **No Import Tool** — Quip retired all import and upload options in January 2024. The Automation API is the only programmatic way to create content. - **Macro Conversion** — Confluence macros must be rendered to static HTML, stripped, or replaced with human-readable placeholders. There is no macro system in Quip. - **HTTP 503 Rate Limits** — Quip returns HTTP 503 instead of 429 when rate-limited, causing standard retry libraries to misclassify the error and fail. - **Content Size Ceiling** — Quip caps documents at 1 MB per API request. Large Confluence pages must be chunked by section across multiple calls. - **Comment Migration** — Confluence inline comments lose positional anchoring and become flat conversation-pane messages in Quip. ## Entity mappings - **Pages** (Confluence) → **Document** (Quip) - **Blog Posts** (Confluence) → **Document** (Quip) - **Spaces** (Confluence) → **Folder** (Quip) - **Comments (Inline)** (Confluence) → **Annotations** (Quip) - **Comments (Footer)** (Confluence) → **Messages (Comments)** (Quip) - **Attachments** (Confluence) → **Blob (Attachment)** (Quip) - **Labels** (Confluence) → **NotAvailable (workaround: document body / folder structure)** (Quip) - **Page Templates** (Confluence) → **Import (Docx/Markdown)** (Quip) - **Space Permissions** (Confluence) → **Folder Members** (Quip) - **Content Restrictions** (Confluence) → **Thread Members** (Quip) - **Ancestors (Page Hierarchy)** (Confluence) → **Folder** (Quip) - **Tasks** (Confluence) → **Thread Content (HTML)** (Quip) - **Page Versions** (Confluence) → **NotAvailable (partial workaround possible)** (Quip) ## What breaks during migration - **Confluence Macros (TOC, Jira, Status)** [Breaks] — No Quip equivalent — must render as static HTML or strip - **Internal Links** [Breaks] — All Confluence URLs break without page-ID-to-thread-ID mapping - **Page Author / Timestamps** [Breaks] — Quip attributes creation to the API token holder — originals lost - **Layouts / Columns** [Breaks] — Multi-column Confluence layouts lose structure in Quip - **Page Version History** [Breaks] — Cannot be migrated — must archive Confluence for history - **Inline Comments** [Workaround] — Lose positional anchoring — become document-level messages - **Attachments / Images** [Workaround] — Require separate blob upload before referencing in HTML - **Blog Posts** [Workaround] — Become regular Quip documents — lose chronological context - **Labels / Tags** [Workaround] — Map to folder membership or metadata block — risk taxonomy explosion - **Page Body Content** [Direct] — Text, headings, tables, and lists convert cleanly to HTML ## 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: [Confluence to Quip Migration: API Limits, Methods & Data Mapping](https://clonepartner.com/blog/confluence-to-quip-migration-api-limits-methods-data-mapping/). ## Frequently asked questions ### Can you import Confluence pages into Quip? Not directly. Quip retired its Upload/Import option and Import API on January 19, 2024. The only way to programmatically create content in Quip is through the Automation API, which accepts HTML or Markdown content via the /1/threads/new-document endpoint. ### What are the Quip API rate limits for migration? The Quip Automation API defaults to roughly 50 requests per minute per user token and 600 requests per minute per company. It returns HTTP 503 (not 429) when rate-limited, which breaks standard retry logic. You must implement custom backoff using X-Ratelimit-Reset and X-Company-Retry-After headers. ### Is Quip being discontinued? Yes. Salesforce announced that all Quip products are being retired. Subscriptions cannot be renewed after March 1, 2027. After expiration, sites enter a 90-day read-only phase, then blocked logins, then data deletion. ### How long does a Confluence to Quip migration take? It depends on volume and content complexity. A 500-page space takes roughly 3–8 hours via API due to Quip's 600 requests/minute company limit. Workspaces with 20,000+ pages can take 1–3 days and typically require a rate-limit increase from Salesforce Support. ### What Confluence data is lost when migrating to Quip? Confluence macros (TOC, page tree, Jira links, status badges) have no Quip equivalent and must be rendered as static HTML or stripped. Inline comments lose positional anchoring. Original author attribution and timestamps are not preserved natively — Quip attributes creation to the API token holder. Store originals in a metadata block or manifest. ## Get a fixed-price quote [Talk to an engineer](https://cal.com/clonepartner/meet?duration=30&utm_source=xtoy&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click) about your Confluence → Quip migration.