Quip to Confluence Migration Guide: Everything You Need to Know (2026)
tl;dr: Quip closes permanently on 31 March 2027, with no new renewals accepted after 1 March 2027. Confluence has no native Quip importer, so getting content across cleanly takes either manual document-by-document work or a purpose-built app. This guide covers the deadline, what actually happens to your data, every DIY method available, what breaks in each one, and how to plan the move properly.
The Quip Retirement Timeline
Salesforce confirmed it's retiring all Quip products. The dates that actually matter:
1 March 2027 – last date Quip subscriptions can be renewed
31 March 2027 – all Quip sites on monthly contracts close permanently, including free accounts
Salesforce-invoiced customers and self-serve (credit card) customers can keep using Quip until the end of their current contract or subscription term, whichever comes first
Quip has also been quietly losing functionality for a while: bulk import tools were retired in January 2024, desktop and mobile apps in June 2024, and new custom Live Apps stopped being allowed from March 2025. The platform you're migrating from today is already a reduced version of what it was – another reason not to leave this until the last possible month.
Why Teams Are Landing on Confluence
If your technical teams already live in Confluence and Quip was mainly used by sales or ops for documents, the pattern is common: two teams, two tools, one deadline forcing the question of where things actually belong. Consolidating onto Confluence means one less platform to license, secure, and administer.
What Confluence actually supports for import
This is the part most migration advice skips over. Confluence – Cloud or Data Center – has no built-in Quip importer, and no built-in importer for any external wiki-style platform. Atlassian's own documentation is direct about this: importing content from outside Confluence requires either a manual conversion process or a custom-built solution using the REST API.
Here's what Confluence Cloud's native import actually handles:
Word documents (.docx) – imported individually or in a batch, each becoming its own Confluence page. Only .docx is supported – not older .doc files
Google Docs and OneDrive files – similar one-way import; once it's in Confluence, the connection to the original file is severed, so future edits in Google Docs or OneDrive won't sync across
HTML – uploaded as a zip file. The top-level folder name becomes the Confluence space name, and each HTML file becomes its own page. Any images or media need to live in a folder with the exact same name as the page they belong to, or the import won't find them
Plain text with basic formatting – can be pasted directly into the editor
What doesn't survive cleanly, regardless of method: multi-column layouts, custom fonts, and complex tables generally flatten into standard Confluence formatting. Images might look ok but are actually imported as links to Quip, which means that the data hasn't moved (when Quip goes, so do the images).
Your DIY options for migrating Quip to Confluence
Option 1 – manual copy-paste. Works fine for a handful of simple documents. Falls apart quickly at scale: formatting breaks, attachments have to be re-uploaded one by one, and there's no way to preserve folder structure automatically. If you've only got a dozen or so documents, this is genuinely the fastest option – don't overthink it.
Option 2 – export as Markdown, convert, then import. Quip documents can be exported as Markdown. From there, Salesforce's own open-source Metro tool can help push Markdown content into Confluence. This works, but it's a technical, command-line process, and you'll need to handle image and attachment uploads separately – there's no built-in Markdown importer in Confluence itself.
If you're scripting this yourself against Quip's API rather than exporting by hand, Quip's own Admin API documentation sets a default rate limit of 100 requests per minute and 1,500 per hour – worth planning around if you're pulling a large workspace programmatically rather than exporting a handful of documents manually.
Option 3 – export to Word, then use Confluence's native Word import. If your Quip documents are mostly text with straightforward formatting, converting to .docx and using Confluence's native import is the most reliable no-code path. It's slow at any real scale, since each document goes through the flow individually, but it's the option most likely to preserve formatting cleanly without extra tooling.
Option 4 – HTML export and bulk import. Best for larger document sets, but requires getting your folder and file naming exactly right before you upload – Confluence expects a specific structure, and if the media folders don't match the HTML filenames precisely, images will be missing on the other side.
Planning Your Migration Timeline
Whichever method you choose, don't treat 31 March 2027 as your working deadline – treat your own renewal date as the real one. A reasonable planning window:
Audit first. How many documents, how many with embedded spreadsheets or Live Apps, who owns what.
Pilot on a small batch. Migrate 20–30 representative documents using your chosen method before committing to the whole workspace. This is where you'll discover whether your formatting survives the way you expect.
Migrate in stages, not all at once, especially if multiple teams are involved.
Run parallel access for a short period so people can double-check nothing important got left behind before Quip access ends.
Frequently Asked Questions
When does Quip shut down? (Quip end-of-life and retirement date)
Salesforce confirmed Quip's retirement: no new Quip renewals are accepted after 1 March 2027, and monthly Quip sites – including free accounts – close permanently on 31 March 2027.
What happens to my Quip content after March 2027?
Once your site closes – either at your own contract or subscription end date, or 31 March 2027 at the latest for free accounts – your Quip content becomes inaccessible. Nothing is automatically migrated anywhere else on your behalf, so anything you haven't moved out before then is effectively gone.
Does Confluence have a native Quip importer?
No. Neither Confluence Cloud nor Confluence Data Center has a built-in Quip importer, and Atlassian doesn't provide one for any external wiki-style platform. You'll need one of the manual conversion methods above, or a purpose-built Marketplace app.
What does the Quip Integration for Confluence app import?
It imports Quip documents into Confluence as native pages, with formatting, attachments, and images intact, and lets you embed live Quip content into a Confluence page via a macro or search Quip from inside Confluence directly.
What doesn't migrate from Quip to Confluence?
Multi-column layouts, custom fonts, and complex or embedded tables typically flatten into standard Confluence formatting regardless of which import method you use. Images in unsupported formats are replaced with placeholder text rather than failing silently.
Does this work with Confluence Cloud or Data Center?
Both hosting options can receive migrated Quip content, though the specific import tools and steps differ slightly between Cloud and Data Center.
How long does a Quip-to-Confluence migration take?
It depends almost entirely on document count and how much you need to preserve. A handful of documents is a manual afternoon's work. Dozens to hundreds of documents, with attachments and folder structure to preserve, is where manual methods stretch into days or weeks – which is the point at which a purpose-built app earns its cost back in time alone.
The Faster Path
Everything above is genuinely doable yourself, and for a handful of documents, it's the right call. But once you're dealing with dozens or hundreds of documents – with attachments, images, and folder structures that need to survive the move intact – the manual methods above get slow and error-prone fast.
Quip Integration for Confluence was built specifically for this one migration path. It imports Quip documents into Confluence as native pages – formatting, attachments, and images intact – and supports both Confluence Cloud and Data Center.
If you'd rather not spend a weekend wrangling HTML folder structures before your renewal date hits, see how it works.
Comments