Migrate from Tettra to xWiki: Self-Hosted Knowledge Base

Migrate from Tettra to xWiki: Self-Hosted Knowledge Base

Tettra has positioned itself as a streamlined knowledge management tool for teams that want quick answers and easy documentation. Its integration with Slack and clean interface make it appealing for teams starting their knowledge base journey. However, as organizations mature, Tettra's SaaS model and per-user pricing create escalating costs, while its closed platform limits customization and data control. Migrating to a self-hosted xWiki instance resolves these concerns by placing your knowledge base entirely under your control, with no recurring per-seat fees and unlimited extensibility.

Why Teams Outgrow Tettra

Tettra charges on a per-user basis, which means your knowledge management costs scale linearly with headcount. For a small team of ten, this may seem reasonable. But as your organization grows to fifty, a hundred, or several hundred employees who need access to internal documentation, the monthly bill becomes a significant line item. Worse, the per-user model often leads to artificial access restrictions, where teams limit who can view the knowledge base to control costs, undermining the very purpose of centralized documentation.

Beyond pricing, Tettra's feature set is intentionally limited. It focuses on simple page creation and Slack-driven question-and-answer workflows, which works well for lightweight use cases but falls short when teams need structured data, complex permission hierarchies, workflow automation, or custom applications built on top of their knowledge base. xWiki provides all of these capabilities out of the box, with a mature extension ecosystem that covers virtually every enterprise documentation need.

Exporting Content from Tettra via API

Tettra provides a REST API that allows you to programmatically retrieve your content. The export process involves authenticating with your API key and iterating through pages, categories, and associated metadata. Each page in Tettra is stored as Markdown content with metadata including the author, creation date, last modified date, and category assignments. Write a script that pulls every page through the API, preserving this metadata in a structured format such as JSON alongside the Markdown content.

Be thorough in your API extraction. Beyond standard pages, Tettra maintains information about page verification status, suggested content, and internal link relationships. Capturing this metadata during export ensures you can replicate important workflows in xWiki rather than losing institutional knowledge about content freshness and ownership. If your Tettra instance includes uploaded files or embedded images, download these assets separately and catalog them against the pages that reference them.

Converting Markdown to xWiki Syntax

Tettra stores content in Markdown format, which requires conversion to xWiki syntax for native rendering. While xWiki does support a Markdown renderer, migrating to native xWiki syntax ensures full compatibility with the platform's macro system, structured data features, and WYSIWYG editor. The conversion covers headings, links, emphasis, lists, code blocks, tables, and image references. Most of these transformations are straightforward and can be handled with a well-structured conversion script.

Pay particular attention to internal links between Tettra pages. These will reference Tettra's URL structure and need to be remapped to xWiki's page reference format. Build a lookup table that maps each Tettra page URL or slug to its target xWiki location, and use this table during the content conversion to rewrite all internal references correctly.

Category to Space Mapping

Tettra organizes content into categories, which serve as the primary grouping mechanism. In xWiki, the natural equivalent is spaces, which support nesting and carry their own permissions and settings. Map each Tettra category to an xWiki space, and consider whether your category structure would benefit from reorganization during the migration. Some teams find that Tettra's flat category model can be enhanced with xWiki's nested space hierarchy, creating a more intuitive and navigable structure for larger knowledge bases.

During the mapping process, create a spreadsheet or structured document that lists every Tettra category alongside its target xWiki space, any subcategory relationships, and the total page count for each category. This mapping document becomes the authoritative reference for your migration scripts and also serves as a validation checklist after import. Review it with stakeholders from each team to ensure the proposed structure reflects how people actually navigate and use the documentation, not just how it was historically organized in Tettra.

Replacing Integrations

One of Tettra's key selling points is its Slack integration, which allows team members to ask questions in Slack and receive answers from the knowledge base. xWiki supports Slack integration as well, through extensions that enable notifications, content search from Slack, and webhook-based workflows. Beyond Slack, xWiki integrates with a much broader set of tools and services through its extension manager and REST API, giving your team more flexibility in building connected workflows. Review every integration your team uses in Tettra and identify the corresponding xWiki extension or API-based solution before completing your migration.

Cost Comparison at Scale

The financial case for migration becomes compelling when you compare costs at various team sizes. The following table illustrates typical annual costs, assuming Tettra's scaling plan pricing against self-hosted xWiki on MassiveGRID infrastructure.

With self-hosted xWiki, your infrastructure cost remains relatively flat regardless of user count. You pay for the server resources to run the platform, not for each person who accesses it. This model delivers increasingly dramatic savings as your organization grows, while simultaneously giving you full control over your data, uptime, and feature set.

Data Ownership and Compliance Advantages

Beyond cost savings, the move from Tettra to self-hosted xWiki delivers a fundamental shift in data ownership. With Tettra, your knowledge base resides on the vendor's infrastructure, subject to their data processing agreements and geographic hosting decisions. For organizations operating under regulatory frameworks such as GDPR, HIPAA, or SOC 2, this third-party data residency can create compliance complications and audit burdens. Self-hosted xWiki on MassiveGRID infrastructure puts your data on servers you control, in data centers you select, with encryption and access policies defined entirely by your organization.

The migration itself also presents an opportunity to establish stronger content governance practices. As you import content into xWiki, implement the platform's workflow extensions to create structured review and approval processes that Tettra's lightweight model could not support. Assign content owners, configure verification schedules, and build dashboards that surface stale or unreviewed documentation. These governance capabilities transform your knowledge base from a passive content repository into an actively maintained organizational asset. For additional perspective on managing the transition from any SaaS knowledge platform, see our universal wiki migration guide.

If you are ready to move from Tettra's per-user pricing model to a self-hosted knowledge base with no seat limits, MassiveGRID's managed xWiki hosting provides the optimized infrastructure to make the transition seamless. Our team handles server provisioning, Java environment tuning, and database optimization so you can focus on your content migration. Reach out to our team to plan your migration timeline and infrastructure requirements.

Published by MassiveGRID, delivering reliable hosting infrastructure for self-hosted knowledge management platforms. Learn more about our xWiki hosting services designed for teams of every size.