Migrating from Atlassian Confluence to BookStack represents a strategic shift from a costly, hierarchical enterprise wiki to a streamlined, open-source knowledge base. While Confluence charges tiered per-user pricing ranging from five to eleven dollars per month and locks your data inside Atlassian cloud infrastructure, BookStack is completely free, self-hosted, and open-source. Organizations typically make this transition to reduce recurring software expenditures, regain absolute ownership of their documentation data, and escape the growing complexity of the Atlassian ecosystem.
BookStack organizes content using a strict three-tier structural model consisting of Shelves, Books, Chapters, and Pages. This differs significantly from Confluence's more fluid space-and-page tree architecture. When planning your migration, you need to account for this structural translation, as well as how your team will adapt to BookStack's WYSIWYG and Markdown editing interfaces instead of the Confluence editor. Successfully executing this move requires careful data extraction, a clean self-hosted deployment, and a structured cutover plan to ensure zero disruption to your daily operations.
For a 50-person team that's a significant annual saving.
🗺️ Migration Steps
Before exporting, review your existing Confluence spaces to archive outdated pages and remove redundant attachments. Confluence accumulated technical debt over years of use often does not need to be carried over to your fresh BookStack instance. Reducing this footprint speeds up the migration process and ensures your new knowledge base starts clean.
Use Confluence's built-in space export feature to generate XML or HTML backups of your documentation. For cloud instances, you may need to rely on site exports or third-party exporter apps to capture all page hierarchies, comments, and embedded images properly. Ensure you securely download all exported archives to your local migration workstation.
Set up a production-ready BookStack instance on your own infrastructure using Docker or a traditional LAMP stack. Configure your environment variables, establish SSL certificates, and set up authentication integrations like LDAP or SAML if your organization requires centralized user management. Having a stable BookStack environment ready is essential before importing any content.
Design your BookStack information architecture by mapping each Confluence space to a BookStack Book or Shelf. Because BookStack enforces a strict hierarchy, translating Confluence parent-child page trees into BookStack Chapters and Pages requires deliberate planning. Document this mapping schema beforehand to maintain consistency during the import phase.
Import your prepared content into BookStack using custom migration scripts, the REST API, or manual recreation for smaller knowledge bases. Since there is no native one-click importer from Confluence to BookStack, most administrators write Python or PHP scripts to parse the Confluence HTML exports and push them directly into BookStack. Verify that page formatting and internal links are preserved during this translation.
Invite your team members to the new BookStack instance and conduct a brief orientation on its shelf-and-book navigation model. Run the Confluence and BookStack instances in parallel for a short validation window before setting Confluence to read-only mode. Once team leads sign off on the imported data, officially retire your Confluence subscription.
⚠️ Common Challenges & How to Avoid Them
Identify critical macros like Jira issue panels or draw.io diagrams prior to export and replace them with standard BookStack image embeds, code blocks, or native text tables.
Accept that historical versions will remain in your Confluence archives and migrate only the latest published revision of each page to keep the BookStack database lean.
Write server-level rewrite rules or use BookStack API scripting to update internal hyperlink paths during the import phase so document cross-references remain functional.
🔗 Get Started
❓ Frequently Asked Questions
No, BookStack does not provide a native automated Confluence importer. Administrators typically rely on Confluence HTML or XML exports combined with custom scripts interacting with the BookStack REST API to handle the transfer.
Confluence manages permissions heavily through user groups and space-level restrictions tied to Atlassian accounts. BookStack offers a more granular role-based access control system that lets you assign permissions down to individual shelves, books, chapters, and pages.
Yes, BookStack is open-source software licensed under the MIT license, meaning there are zero per-user licensing fees or artificial user caps. You only pay for the underlying server infrastructure required to host the application.
Want a full feature and pricing comparison before you switch?
Read the Full Confluence vs BookStack Comparison →