Notion cost vs self-hosted Docmost and XWiki: where the money goes
Self-hosting moves your cost from a per-member Notion subscription to infrastructure, staff time and any paid features you choose to add, and the result depends on how many people use the wiki and which features they need. No supplied figure gives a self-hosted total, so you will need to build the model yourself before comparing it with your renewal quote. Start with the recurring components: compute and storage for the application and its database, backup storage, TLS certificates, monitoring, and the hours an administrator spends on upgrades, restores and access changes. The one-time components are the migration, initial configuration and any integration work with your identity provider. Ask Notion to confirm in writing which plan and seat count your renewal covers, and which features (such as SAML SSO from Business or SCIM on Enterprise) are priced into it.
Licensing sets the floor for the software cost. Docmost is licensed under AGPL-3.0 and XWiki under LGPL-2.1, so running either one does not require a license fee. The cost decisions sit in the paid layers. Docmost's Confluence, DOCX and PDF importers are paid-edition features, so if your migration depends on Word or PDF import, price that edition before you commit. XWiki Pro and its support subscriptions are priced by user band: Starter covers up to 25 users and is available on XWiki Cloud only, Basic covers up to 1,000 users, Business up to 10,000 and Enterprise is unlimited. XWiki SAS states that cloud and on-premises pricing is the same. Its published consulting rate of 1200 EUR per day requires a Business or Enterprise support plan, and its Confluence Migrator Pro is priced from 2000 EUR, so that line belongs in the model only if you move content out of Confluence.
Turn these facts into a worksheet with your own numbers: current named users, expected growth, the band each platform would land in, the features you must have, and the administrator hours you can realistically commit. Ask each vendor for a quote that states the user band, the edition, the support tier and whether SSO is included. Ask DeployOpen for a fixed-scope written proposal that lists the hosting components, migration steps, hardening tasks, backup testing and handover documentation, because those items, not the license line, usually decide the total. Confirm current prices on the vendors' own pricing pages before the comparison goes to finance, since this page does not carry them.
Which cost components sit on each side
This table sets each cost component of staying on Notion against the components of running Docmost or XWiki yourself, and marks whether each one is one-time or recurring. Read it by asking who is paid for each line, then check which rows apply to your plan tier, identity setup and data volume. The main takeaway is that self-hosting removes the per-member subscription but moves hosting, upgrades and admin time onto your budget.
| Cost component | Notion (subscription) | Self-hosted Docmost or XWiki | One-time or recurring |
|---|---|---|---|
| Licence or subscription | Per-member plan paid to Notion; SAML SSO starts at Business and SCIM sits on Enterprise | No per-user licence for the open-source core: Docmost is AGPL-3.0, XWiki Standard is LGPL-2.1 | Recurring for Notion; none for the open-source core |
| Hosting and infrastructure | Included in the subscription; Notion hosts the data | Your cloud account, data centre or air-gapped network, plus database, storage and backups | Recurring |
| Paid edition or add-ons | Enterprise features such as SCIM are priced inside the plan | Docmost lists Confluence, DOCX and PDF importers as paid-edition features; XWiki Pro apps and connectors are paid extensions | Recurring if subscribed, confirm current terms with each vendor |
| Implementation and configuration | Mostly internal setup of workspaces, teams and permissions | Installation, SSO integration, permission model and backup design, by your team or a fixed-scope implementation partner | One-time |
| Migration of content | Export effort from Notion; workspace-wide export can take up to 30 hours (Notion help center) | Conversion from Notion exports, rebuilding databases, checking links and permissions; often the largest one-time item | One-time |
| Support and vendor help | Included in plan support channels; confirm response terms for your tier | Internal staff, community channels, or paid support from XWiki SAS or a partner; quotes follow the written scope | Recurring if retained, one-time if project-based |
| Upgrades and patching | Handled by Notion | Your team applies releases, tests them and rolls back when needed; maintain a staging copy | Recurring |
| Backups and disaster recovery | Notion's own infrastructure; your exports are a separate copy | Your responsibility: database, attachments and configuration backups, plus restore tests | Recurring |
| Internal admin and skills | Workspace admins and plan owners | Platform or IT staff who run containers or servers, databases, identity integration and security hardening | Recurring, the main driver of total effort |
What moves the Docmost and XWiki comparison
The cost of moving from Notion to a self-hosted wiki depends less on the software licence than on a few drivers: how many people edit, how much content and how many attachments move, which identity and import features are required, and who will run the platform. Each driver below changes the total in a predictable direction, so check them before comparing numbers.
User count and plan tier
Notion is priced per member, so its bill grows with every seat. XWiki Pro and support subscriptions are tiered by user band, from Starter (up to 25 users, XWiki Cloud only) through Basic, Business and Enterprise (unlimited users). Count named editors and readers separately before you pick a tier, because the band you land in drives the subscription cost more than the hosting does. Docmost's paid edition is priced separately, so confirm its user terms with the vendor.
Content volume and attachments
Storage and backup size grow with page history, attachments and exported files. Notion's full workspace export can take a long time to generate, so a large workspace adds elapsed effort before any import starts. Attachment-heavy wikis need more disk, a larger backup window and a clear decision on whether attachment history must survive the move, since some migration tools keep page history but not attachment history. Measure the export before you size the server.
SSO and SCIM requirements
Notion gates SAML SSO to its Business plan and SCIM provisioning to Enterprise, so a requirement for automated joiner and leaver handling changes the price point directly. In a self-hosted wiki, SSO is set up against your own identity provider, and XWiki Pro lists Active Directory and Azure Active Directory SSO applications. Confirm which protocol and provisioning model your identity provider supports, and whether the wiki edition you choose covers it without an extra extension.
Edition needed for importers
Import support is not uniform across editions. Docmost's documentation lists its Confluence, DOCX and PDF importers as paid-edition features, while its Notion import is part of the import dialog you can use to bring in an export. XWiki's Confluence migration relies on the paid Confluence Migrator Pro extension, priced from 2000 EUR, and its open-source Confluence XML filter stream is the component underneath it. Check which importer you need, which edition includes it, and whether the migration itself is in the quote.
Availability and backup targets
A self-hosted wiki becomes a system you must keep running. Decide the recovery point and recovery time you need before comparing hosting options, because they determine how many database and file-store copies you run, where they sit, and how often you restore-test them. Notion handles availability for you, so the self-hosted cost includes redundancy, monitoring and backup storage that you did not previously pay for explicitly. Ask any implementation partner to show the backup and restore procedure in writing.
Skills already in the team
The largest hidden cost is often staff time, not licences. A team that already runs PostgreSQL or MySQL, a Java application server and container platforms can absorb XWiki's deployment with less ramp-up. A team without those skills should budget for training or outside help, and XWiki SAS lists training and consulting as separate services with their own day rates. Count who will patch, upgrade and troubleshoot the platform each month, and whether that work sits inside an existing role.
How to build the cost model with your own numbers
This sequence turns a vague sense that Notion is expensive into a side-by-side model built from your own invoice, seat counts, feature needs and hosting quotes, so the comparison holds for your organization over a period you choose.
Count active seats and guests
Pull the member list from Notion's admin console and separate full members from guests, external collaborators and inactive accounts. Record the count for each group, along with the teamspaces or workspaces they use. Owners and finance should agree on the number before anyone prices anything, because seat count is the main driver of per-member cost. The step is done when you have one table with active members, guests and idle accounts, each with a date of last activity.
List the features you actually need
Write down which capabilities the organization depends on today: SAML SSO, SCIM provisioning, audit or export controls, guest access rules, and page-level permissions. Ask the security and compliance leads which of these are contractual or audit requirements and which are preferences. Mark each item as required, useful or not used. The output is a short feature list that tells you which Notion tier you truly need and which paid features on the self-hosted side, such as XWiki Pro applications or Docmost's paid edition, you would need to buy.
Price Notion from your own invoice
Take the current annual or monthly invoice and the plan it covers, then recalculate what the same seats would cost on the plan that includes your required features. Notion's public plan pages may change, so use the figures from your own billing contact or account manager and record the date you obtained them. Note any add-ons, Enterprise terms, and renewal uplift. The check is complete when you can state the recurring Notion cost per year for the current seat count and for the seat count you expect at the end of the period.
Size hosting in your own infrastructure
Work with your platform team to estimate the compute, storage, database, backup and networking needed for Docmost or XWiki in your cloud account or data center, including a staging environment if you plan one. Include the database engine, object or file storage for attachments, and the monitoring you already run. Ask the cloud or infrastructure team for a quote based on your own rate cards. Recurring hosting is paid to your cloud provider or hardware budget, and it scales with user count, attachment volume and availability targets. The output is a monthly and annual hosting line for each candidate tool.
Add migration and admin hours
Estimate the one-time work: exporting from Notion, cleaning up pages, rebuilding databases, moving permissions, and testing. Use Notion's export help center page to size the effort, because it documents limits on workspace-wide exports, the subpage option for PDF export that is limited to Business and Enterprise plans, and the admin settings that can disable exports on Enterprise workspaces. Also budget ongoing admin time for upgrades, backups, user lifecycle and support. Name who does each task, whether internal staff or a partner, and get hours or fixed-scope quotes in writing. The output is two lists: one-time migration effort and recurring administration effort.
Compare totals over a stated period
Build a single sheet with one column for Notion and one for each self-hosted option. Show one-time costs in year one, then recurring costs for each year of the period you choose, and include any paid extensions or support tiers. Run a second scenario with higher seat growth and one with lower seat growth to see which costs move. Label the sheet as your model, not a forecast. The check is that a finance reviewer and a security lead can each trace every line back to an invoice, a quote, a seat count or a documented Notion limit.
Ask for quotes that match the model
Before a decision, request written quotes that use the same scope, seat count and period as your model. Ask Notion for the price of the tier that includes your required features. Ask the self-hosted vendors or implementation partners for hosting assumptions, paid edition costs, support tiers, migration scope and what is excluded. Confirm current license terms and any paid features with the vendor, since editions and plan contents change. The step is complete when every line in the model has a source document and a named owner.
What migration adds to the first-year cost
Moving off Notion starts with an export, and the export is the first line in the migration budget. Notion exports pages and databases as PDF, HTML, or Markdown and CSV, and a workspace owner can export all workspace content, which Notion says can take up to 30 hours. Plan for that window in the calendar, confirm which export format your workspace plan and security settings allow, and check whether your Notion plan includes the Include subpages option for PDF export, which is limited to Business and Enterprise plans. Enterprise workspaces can also disable exports entirely, so ask the Notion admin to confirm that setting before the project is scoped.
Notion databases need separate handling in either tool. Their CSV exports carry rows and property values but not relations, rollups, linked views or formulas in a form the target can reuse, so someone has to rebuild those structures by hand in Docmost or in XWiki as structured data. Docmost's import dialog lists Notion among the sources it accepts, so pages and their Markdown or HTML content can be brought in directly, while the database rebuild remains a separate line item in your estimate. For XWiki, the paid Confluence Migrator Pro extension from XWiki SAS is priced from 2000 EUR, but it targets Confluence backups, not Notion. Notion content therefore moves through HTML or Markdown, and the cost of that path is internal or partner time, not a license fee.
When you request quotes, ask each provider to separate the export and import work, the database rebuild, the permission mapping and the link repair from the hosting work. Ask how attachments and internal page links will be handled, since those are the items most often lost or broken in a Notion move. A short pilot on a representative set of pages will show the real effort before you commit, and it will show which databases justify a dedicated migration rather than manual recreation.
Questions buyers ask before comparing Notion with self-hosting
Is self-hosting Docmost or XWiki cheaper than staying on Notion?
It can be, but the answer depends on your team and scope, so it is not a fixed saving. Notion costs are per member and recur every month. Self-hosting shifts the cost to infrastructure you run (servers or cloud resources, backups, storage), people time for installation, upgrades, monitoring and access management, and any paid features you need. Docmost's core is AGPL-3.0 and XWiki Standard is LGPL-2.1, so there is no per-seat license fee for the core software. Ask any vendor or partner to model the recurring infrastructure and staff time against your current Notion seat count, including growth over three years.
How long does a Notion to self-hosted wiki migration take?
The duration is set by content volume, structure and how much rework your pages need, so there is no standard timeline. Notion's workspace-wide export can take up to 30 hours according to Notion's help center, and the export link expires, so plan for waiting time before any import work starts. Docmost imports Notion exports directly, but Notion databases usually need separate handling. XWiki requires rebuilding databases as structured data, which adds effort. Ask for a timeline based on a page and database inventory of your own workspace.
What does the internal team need to provide during a migration?
The internal team supplies the people who know the content and the access model. Expect to name a content owner for each space, decide which pages are current and which can be archived, and confirm who may see which content after the move. Platform staff need to provide hosting accounts, network access, a DNS name, certificates, identity provider details and backup targets. Someone must also approve the cutover date and check that links, attachments and permissions behave correctly in the new system.
Can our own engineers run a Docmost or XWiki deployment without outside help?
Yes, many teams can, provided they have container and database skills, an operations process and time for upgrades. Official XWiki Docker images are maintained by the XWiki Core Dev Team and come in MySQL, PostgreSQL and MariaDB variants on Tomcat, and XWiki publishes stable and LTS lines. The harder parts are ongoing: patching, backup restore tests, access reviews and the migration itself. If the team lacks capacity, a fixed-scope engagement from DeployOpen can cover planning, implementation, hardening and documentation, with ongoing support available as a retainer.
When do Docmost or XWiki paid features become necessary?
Pay only for features your requirements cannot meet otherwise. In Docmost, the Confluence, DOCX and PDF importers are listed as paid-edition features, so check whether you need them before budgeting. XWiki Standard is free, while XWiki Pro adds business applications, connectors and XWiki SAS support, and its Confluence Migrator Pro is priced from 2000 EUR according to the XWiki Store. Consulting is listed at 1200 EUR per day and training at 1500 EUR per day, both per XWiki SAS pricing, and consulting requires a Business or Enterprise support plan.
How do we handle SSO and SCIM without paying for Notion Enterprise?
Notion gates SAML SSO to Business and SCIM provisioning to Enterprise, so self-hosting moves that decision to your identity stack. Connect Docmost or XWiki to your existing identity provider using the protocols each supports, and confirm the exact options for your version in its documentation. XWiki Pro lists Active Directory and Azure Active Directory SSO applications, and XWiki has an open-source OIDC extension in its contrib repository. Ask whether user provisioning and deprovisioning must be automated, because manual account handling is a common access risk when people leave.
What should we ask for in a fixed-scope quote for this work?
Ask for a written scope that names each deliverable, the source systems, the target platform, the spaces or workspaces included, and the acceptance criteria for each one. The quote should list hosting assumptions, backup and restore testing, identity integration, the handling of Notion databases, documentation and training, and what happens if the content inventory is larger than expected. Confirm which costs are one-time, which recur, who pays for licenses or paid extensions, and what support is included after go-live. DeployOpen does not publish a price list, and a quote follows from that written scope.
When Docmost or XWiki changes the total
Docmost is usually the lighter cost fit when the goal is to replace a Notion workspace used for team docs, handbooks and specifications. Its core is licensed AGPL-3.0, so the main cost lines are the server, storage, backups and the administrator's time for upgrades. The import dialog accepts Notion exports, which keeps the migration to a documented export and an import pass. The points to confirm before committing are which importers sit in the paid edition, since the Confluence, DOCX and PDF importers are listed there, and whether the Notion export of your workspace is large enough that its up-to-30-hour generation time changes your schedule. Confirm edition contents directly with Docmost before budgeting for any paid feature.
XWiki justifies more setup when the knowledge base has to behave like a structured system: many page types, permissioned spaces, and data that people query and report on, not only read. Its open-source core is LGPL-2.1 and the official Docker images make the base deployment repeatable, but the total cost moves with the add-ons. XWiki Pro bundles directory SSO applications and connectors, and support or consulting is sold in tiers that scale by user count, with consulting priced per day and requiring a Business or Enterprise support plan. Ask XWiki SAS to map each feature you need to a specific tier and to state which items are one-time versus recurring. Feature depth belongs in the Notion vs XWiki comparison, so this decision should rest on your structured-content requirements rather than on the sticker cost of the product.
How DeployOpen scopes a fixed-price Docmost or XWiki implementation
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For a Notion move to Docmost or XWiki, we start from a written scope so that hosting, migration and admin time are agreed before any work begins.
How we scope
- We confirm your Notion plan, member count and whether you need SAML SSO or SCIM provisioning before choosing Docmost or XWiki.
- We map which workspaces, pages, databases and attachments move, and which stay in Notion during a transition period.
- We agree the hosting target, data residency needs and admin roles in writing, since engagements are fixed-scope.
How we build
- We deploy Docmost or XWiki in your cloud account, data center or air-gapped network, with the database and storage you choose.
- We run test migrations from Notion HTML or Markdown exports and check page hierarchy, links, attachments and permissions.
- We configure identity integration, backups and access controls, then test them against the scope before go-live.
How we hand over
- We document the deployed architecture, backup and restore steps, upgrade procedure and admin tasks for your team.
- We provide a migration record listing what moved, what was rebuilt by hand and what remains open.
- We train the administrators and content owners who will run the wiki after handover.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- We can plan Docmost or XWiki version upgrades as a scheduled task, including checks on your backups first.
- Confirm with us in the quote which items are one-time work and which recur under a retainer.
