Convert MediaWiki to Wiki

Why Convert MediaWiki to Wiki?

Converting MediaWiki markup to a generic Wiki format is essential when migrating content from MediaWiki-powered platforms (Wikipedia, Fandom, corporate MediaWiki installations) to other wiki engines such as DokuWiki, Confluence, TWiki, or Foswiki. Each wiki platform uses its own markup dialect, and MediaWiki-specific syntax like templates, parser functions, and complex table formatting needs to be translated into a more portable wiki notation.

MediaWiki markup is one of the most feature-rich wiki syntaxes available, but this richness comes with platform lock-in. Features like template transclusion, magic words, parser functions, and MediaWiki-specific extension tags only work within the MediaWiki ecosystem. Converting to a generic Wiki format strips away these platform-specific elements while preserving the core content structure: headings, formatting, lists, links, tables, and text flow.

Organizations often need to migrate wiki platforms for various reasons: moving from a self-hosted MediaWiki to a cloud-based solution like Confluence, consolidating multiple wiki systems, or adopting a lighter-weight wiki engine like DokuWiki that requires less server resources. The conversion ensures that years of accumulated knowledge and documentation can transition smoothly to the new platform without losing structural integrity.

The generic Wiki output uses a simplified syntax that represents the common denominator across major wiki engines. Headings use the universal == syntax, links use [[ ]] notation, and tables use pipe-based formatting. This intermediate format can then be fine-tuned for the specific target wiki engine, or used directly on platforms that accept standard wiki notation. The conversion handles MediaWiki-specific constructs by either simplifying them to their portable equivalents or extracting their visible content.

Key Benefits of Converting MediaWiki to Wiki:

• Platform Migration: Move content from MediaWiki to DokuWiki, Confluence, or other wiki engines
• Portability: Create platform-independent wiki content that works across multiple engines
• Simplification: Remove MediaWiki-specific complexity while keeping core content
• Interoperability: Share wiki content between different wiki platforms
• Reduced Lock-in: Free content from MediaWiki-specific template and extension dependencies
• Easier Maintenance: Simpler wiki markup is easier to edit and maintain
• Multi-Platform Publishing: Publish the same content across different wiki systems

Practical Examples

Example 1: Article with Templates and Links

Input MediaWiki file (article.mediawiki):

{{Infobox software
| name = MyApp
| developer = Acme Corp
}}
== Overview ==
'''MyApp''' is a [[software application]] developed by
[[Acme Corp]] for [[project management]].

=== Features ===
* Real-time [[collaboration]]
* Built-in [[Gantt chart|Gantt charts]]
* {{abbr|API|Application Programming Interface}} access

[[Category:Software]]
[[Category:Project Management]]

Output Wiki file (article.wiki):

== Overview ==
**MyApp** is a [[software application]] developed by
[[Acme Corp]] for [[project management]].

=== Features ===
  * Real-time [[collaboration]]
  * Built-in [[Gantt charts]]
  * API (Application Programming Interface) access

Example 2: Technical Documentation with Tables

Input MediaWiki file (api_docs.mediawiki):

= API Reference =

== Endpoints ==

{| class="wikitable mw-collapsible"
|-
! Method !! Endpoint !! Description
|-
| GET || /api/users || List all users
|-
| POST || /api/users || Create new user
|-
| DELETE || /api/users/{{id}} || Delete user
|}

== Authentication ==
Use [[OAuth 2.0]] with '''Bearer''' tokens.
See {{main|Authentication Guide}} for details.

Output Wiki file (api_docs.wiki):

= API Reference =

== Endpoints ==

| Method | Endpoint | Description |
| GET | /api/users | List all users |
| POST | /api/users | Create new user |
| DELETE | /api/users/{id} | Delete user |

== Authentication ==
Use [[OAuth 2.0]] with **Bearer** tokens.
See [[Authentication Guide]] for details.

Example 3: Formatted Content Migration

Input MediaWiki file (procedures.mediawiki):

== Deployment Procedure ==

{{Warning|Always back up the database before deploying.}}

# Stop the application server
# Run database migrations
#: python manage.py migrate
# Deploy the new code
# Restart services
#* Web server
#* Background workers
#* Cache server

''Last reviewed: {{CURRENTMONTHNAME}} {{CURRENTYEAR}}''

Output Wiki file (procedures.wiki):

== Deployment Procedure ==

**Warning:** Always back up the database before deploying.

  - Stop the application server
  - Run database migrations
    ''python manage.py migrate''
  - Deploy the new code
  - Restart services
    * Web server
    * Background workers
    * Cache server

//Last reviewed: March 2026//

Frequently Asked Questions (FAQ)

Q: What is the difference between MediaWiki and generic Wiki format?

A: MediaWiki is a specific markup language created for the MediaWiki software (Wikipedia's engine) with features like templates, parser functions, magic words, and complex table syntax. Generic Wiki format uses the common subset of wiki syntax shared across many wiki engines (DokuWiki, Confluence, TWiki), with simpler, more portable notation for headings, links, lists, and basic formatting.

Q: What happens to MediaWiki templates during conversion?

A: MediaWiki templates are platform-specific and cannot be directly represented in generic wiki format. During conversion, templates are either expanded to their text content, converted to plain text equivalents, or omitted. Infobox templates may be converted to simple tables, warning/note templates become formatted text blocks, and navigation templates are typically removed.

Q: Can I use the output directly in DokuWiki?

A: The generic wiki output provides an excellent starting point for DokuWiki migration. Core elements like headings, lists, links, and basic formatting will work with minimal adjustment. DokuWiki has some unique syntax (e.g., === headings === use reverse depth), so minor tweaks may be needed for full compatibility with DokuWiki's specific dialect.

Q: How are MediaWiki categories handled?

A: MediaWiki categories ([[Category:Name]]) are platform-specific organizational tags. During conversion, they may be converted to keyword tags, preserved as metadata comments, or listed at the end of the document as plain text labels. The specific handling depends on whether the target wiki platform supports a similar categorization system.

Q: Will complex MediaWiki tables convert properly?

A: Basic tables with rows, columns, and headers convert cleanly to generic wiki table format. However, advanced MediaWiki table features like CSS classes, sortable columns, collapsible sections, colspan, rowspan, and nested tables may be simplified. The converter preserves all cell content while streamlining the table structure for portability.

Q: How are parser functions and magic words handled?

A: MediaWiki parser functions (like #if, #switch, #expr) and magic words (like CURRENTYEAR, PAGENAME) are MediaWiki-specific features. During conversion, parser functions are evaluated to their most likely output value, and magic words are replaced with their current values or descriptive text. These dynamic elements become static content in the wiki output.

Q: Is this useful for Confluence migration?

A: Yes! Converting MediaWiki to generic wiki format is a common intermediate step in Confluence migration. While Confluence uses its own storage format (XHTML-based), its wiki markup mode accepts many standard wiki syntax elements. The converted output provides a clean base that can be further adapted to Confluence's specific requirements.

Q: Can I convert multiple MediaWiki pages to Wiki format at once?

A: Yes! Upload multiple MediaWiki files simultaneously and each will be independently converted to generic wiki format. This is essential for large-scale wiki migrations where hundreds or thousands of pages need to be moved from MediaWiki to another wiki platform.