π οΈ Migration Tools
Migration Planner
β ReadyAnalyse your Azure DevOps Wiki structure and estimate migration complexity
Content Previewer
β ReadyPreview how your content will convert before running the migration
Azure DevOps Migrator
β ReadyMain migration tool for Azure DevOps Wiki to MediaWiki content transfer
Validation Tool
π§ In ProgressValidate migrated content for accuracy and completeness
π Current Status
π Quick Start Guide
Get up and running with MediaWiki Migration Tools in 5 simple steps
- Python 3.8 or higher
- Azure DevOps access token
- MediaWiki admin credentials
- Git (for cloning the repository)
pip install -r requirements.txt
python setup_config.py --azure-token YOUR_TOKEN --mediawiki-url YOUR_URL
python migration_planner.py --wiki "YourWikiName"
python content_previewer.py --page "YourPageName"
python azure_devops_migrator.py --wiki "YourWikiName"
- Always backup your data before migration
- Test with a small wiki first
- Review converted content manually
- Images require manual upload process
π οΈ Available Tools
Comprehensive toolkit for Azure DevOps to MediaWiki migration
Analyze your Azure DevOps Wiki structure and plan migration strategy
migration_planner.py
- Content complexity analysis
- Migration time estimation
- Risk assessment report
- Dependency mapping
Preview content conversion before migration
content_previewer.py
- Side-by-side comparison
- Syntax highlighting
- Interactive preview
- Export to HTML
Main migration tool for Azure DevOps Wiki to MediaWiki
azure_devops_migrator.py
- Batch processing
- Error recovery
- Progress tracking
- Rollback support
Import and manage MediaWiki templates
mediawiki_import.py
- Template detection
- Infobox conversion
- Custom template mapping
- Batch import support
π§ Available Utility Tools
getting_started.py
- Interactive setup and environment configurationvalidation_tool.py
- Validate migrated content accuracymediawiki_import.py
- Basic MediaWiki template import
backup_manager.py
- Automated backup managementlink_validator.py
- Comprehensive link validationmigration_analytics.py
- Advanced reporting dashboardperformance_monitor.py
- Real-time migration monitoring
These tools are in development. Check our planned features section for progress updates.
--help
to see available options and usage examples. View the complete tools reference for detailed documentation.π Comprehensive Guides
Step-by-step guides for successful migration
Get up and running in 15 minutes
- Environment setup
- Basic configuration
- First migration test
- Validation process
Comprehensive migration workflow
- Pre-migration planning
- Content analysis & mapping
- Execution strategies
- Post-migration validation
π Specialised Documentation
π‘ Examples & Use Cases
Real-world examples and success stories
Before/after examples with manual fix guidance
- Basic markdown conversion
- Complex tables and lists
- Code blocks and syntax highlighting
- Images and media handling
- Links and cross-references
- Templates and macros
- Common formatting issues
- Table alignment problems
- Link reference updates
- Template parameter mapping
See how the tools analyse different content types
π οΈ Getting Started Examples
Real command examples you can copy and use
- Plan your migration strategy
- Preview content conversion
- Run dry-run tests first
- Validate results afterwards
Typical workflows and best practices
Run migration_planner.py to understand your content
Use content_previewer.py for sample pages
Execute migration with validation checks
π Code Samples
# Basic usage example - Command line tools # 1. Analyse your Azure DevOps Wiki python migration/migration_planner.py --wiki "YourWikiName" # 2. Preview content conversion python migration/content_previewer.py --page "YourPageName" # 3. Run migration with dry-run first python migration/azure_devops_migrator.py --wiki "YourWikiName" --dry-run # 4. Execute actual migration python migration/azure_devops_migrator.py --wiki "YourWikiName"
π Getting Started Script
The interactive setup script that guides you through environment configuration and tool selection
- Environment Detection: Automatically detects your OS, Python version, and shell
- Setup Configuration: Creates .toolkit_env file with optimised settings
- Interactive Menu: Provides guided access to all migration tools
- Dependency Checks: Verifies required packages and provides installation guidance
- Platform Optimisation: Adapts to Git Bash, PowerShell, macOS, and Linux environments
Complete migration workflow setup
Run migration_planner.py with guidance
Preview content conversion before migration
Start Docker-based development environment
Access toolkit documentation
Troubleshooting and support information
π§ Technical Details
Creates a .toolkit_env file with:
- Python executable path
- Shell and OS detection
- Docker Compose command preference
- Git Bash compatibility settings
- Toolkit directory paths
Optimised for:
- Windows: Git Bash, PowerShell, Command Prompt
- macOS: Terminal, iTerm2, Zsh, Bash
- Linux: All major distributions and shells
- Docker: Both Compose v1 and v2
python getting_started.py
first when setting up the toolkit in a new environment. It will detect your system configuration and set up optimal defaults for your platform.π― Planned Features
Future enhancements and tools currently in development
Automated backup and restore functionality for MediaWiki instances
Comprehensive link validation and automatic fixing
Clean up temporary files, logs, and migration artifacts
System health monitoring and performance checks
Detailed migration reports and success metrics
Deep content analysis and pattern recognition
Real-time migration performance monitoring
Automated content quality assessment
Advanced template conversion and management
Comprehensive migration validation tests
Browser-based migration management interface
Support for Confluence, Notion, and other wikis
π Development Roadmap
β Enhanced error handling and logging
β Documentation improvements
π§ link_validator.py implementation
π§ Enhanced template management
π Performance monitoring tools
π Quality assessment framework
π Multi-source support research
π§ͺ Automated testing framework
π€ Get Support
We're here to help you with your migration
Q: How long does a typical migration take?
A: Migration time depends on the size and complexity of your wiki. Small wikis (10-50 pages) typically take 15-30 minutes, whilst larger wikis (500+ pages) may require several hours.
Q: What if my content doesn't convert correctly?
A: Our tools achieve 95%+ accuracy for standard content. Use the content previewer to identify issues before migration. Complex tables or custom formatting may require manual adjustment.
Q: Can I customise the migration process?
A: Yes, all tools support configuration files, command-line parameters, and can be integrated into custom scripts for advanced workflows.
Q: Do I need to migrate all content at once?
A: No, you can migrate in batches. Use the --page
or --folder
options to migrate specific content subsets.
Q: What about images and attachments?
A: Images and attachments require manual upload to MediaWiki. The migrator identifies all media files and provides instructions for bulk upload.
Authentication Failed
Check your Azure DevOps PAT has Wiki read permissions. Verify MediaWiki bot credentials are correct.
Content Formatting Issues
Use content_previewer.py
to preview conversions. Complex tables may need manual adjustment.
Migration Timeout
For large wikis, use --batch-size 10
to process in smaller chunks. Consider running overnight.
Missing Dependencies
Run pip install -r requirements.txt
in the migration folder to install all dependencies.
Report bugs and request features on our GitHub repository.
Join the conversation in GitHub Discussions.
Contribute to docs via pull requests.