Migration Guide

Overview

Migrating to Aevum Encyclopedia ensures your knowledge assets benefit from AI-enhanced search, semantic linking, multilingual support, and expert-verified content pipelines. This guide supports migration from:

• MediaWiki / WordPress / Drupal
• Confluence / Notion / Obsidian
• Custom JSON/Markdown/SQL exports
• Plain XML or CSV datasets

Prerequisites

Before beginning, ensure you have the following ready:

1. Admin Access to your current platform's database or export tool
2. Aevum API Key (generate from Dashboard → Settings)
3. Backup of all source content and media assets
4. Migration Endpoint configured (available under Projects → Migrations)

Step 1: Prepare Source Data

Export your content using one of our supported formats. We recommend JSON for structured data or Markdown for prose-heavy archives.

Ensure all files are compressed into a single .zip archive before proceeding.

Step 2: Configure Migration Endpoint

Generate a secure upload endpoint from your Aevum dashboard. This creates a temporary, encrypted pipeline for your data.

curl -X POST https://api.aevum.ai/v3/migrations/init \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "source_type": "confluence",
    "estimated_records": 15000,
    "preserve_metadata": true,
    "auto_map_taxonomy": true
  }'

Save the returned migration_id and upload_url. The endpoint expires after 48 hours.

Step 3: Run Import Wizard

Upload your archive using the provided URL. Aevum's pipeline will parse, normalize, and queue your content for indexing.

curl -X PUT UPLOAD_URL \
  -F "file=@/path/to/export.zip" \
  -H "Authorization: Bearer YOUR_API_KEY"

Step 4: Map Taxonomies

Aevum's AI will propose category mappings based on your source metadata. Review and adjust before finalizing.

1. Navigate to Projects → Migrations → [Your ID] → Taxonomy Map
2. Review AI-suggested category alignments
3. Override mappings for specialized domains (e.g., medical, legal, engineering)
4. Confirm tag inheritance rules

Incorrect mappings can be corrected post-migration, but accurate initial mapping reduces AI retraining overhead.

Step 5: Verify & Index

Trigger the final indexing pipeline. Aevum will validate schema compliance, resolve internal links, and activate semantic search.

curl -X POST https://api.aevum.ai/v3/migrations/MIGRATION_ID/verify \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{"skip_validation": false}'

Monitor progress via the Migration Tracker. Once status shows ✅ Indexed, your content is live and searchable.

Troubleshooting

Still stuck? View our advanced diagnostics guide or contact engineering.

Support & Resources

Migration assistance is available for all tier accounts:

• 📧 migration@aevum.ai (48h SLA)
• 💬 Community Forum
• 📖 API Reference
• 🔧 Schema Validator Tool