Documentation v2.4

Migration Guides

Comprehensive instructions for transferring your data, communities, and integrations to ConnectHub securely and efficiently.

🔍

Overview

ConnectHub's migration toolkit supports one-click transfers from major platforms, bulk CSV/JSON imports, and full API-driven synchronization. Whether you're moving a single creator account or an entire enterprise community, our guides ensure zero data loss and minimal downtime.

ℹī¸
Recommended: Always export a backup of your source data before initiating migration. ConnectHub provides a validation step to preview mappings before finalizing transfers.

Quick Start

Get up and running with the official ConnectHub Migration CLI in under 5 minutes:

bash 
# Install the CLI globally
npm install -g @connechub/migration-cli

# Authenticate with your API key
ch-migrate auth --key CH_sk_...

# Initialize a new migration project
ch-migrate init --source discord --target communities

Discord → ConnectHub Communities

Transfer servers, channels, roles, and message history to ConnectHub's native community system. Roles map to permissions, and threaded conversations convert to topic groups.

  1. Export Discord Data

    Use the Discord Data Export Tool to download your server data in ZIP format. Ensure you include channels, members, and message history.

  2. Map Roles & Permissions

    ConnectHub automatically maps standard Discord roles (@Admin, @Moderator, @Member). Custom roles can be defined in the role_mapping.json file.

  3. Run the Migration

    bash
    ch-migrate run discord:\\./backup.zip \
  --community "my-new-community" \
  --map-roles \
  --preserve-threads

  4. Verify & Activate

    Review the generated migration_report.html for skipped messages or permission mismatches. Click Activate in the dashboard to go live.

⚠ī¸
Note: Voice channel recordings and custom server boosts cannot be transferred. They will be converted to community milestones or removed per your preference.

API & Migration Tools

Advanced users and developers can leverage the ConnectHub Migration API for custom pipelines, scheduled syncs, and enterprise data transformation.

Endpoint Method Description
/api/v2/migrations POST Initialize a new migration job
/api/v2/migrations/:id/status GET Track progress & validation results
/api/v2/migrations/:id/rollback POST Revert to pre-migration state
/api/v2/formats GET List supported input schemas

Frequently Asked Questions

How long does a typical migration take?

For accounts under 10,000 posts, migration usually completes in 2-5 minutes. Large communities or enterprises may take 30-90 minutes depending on media assets. You can track real-time progress in the dashboard.

Can I migrate multiple times?

Yes. ConnectHub supports incremental migrations. New data from your source platform will be appended without overwriting existing records. Use the --incremental flag with the CLI.

What happens to my original data?

Nothing. ConnectHub performs read-only exports. Your original platform data remains untouched. We strongly recommend keeping backups until you've verified everything on ConnectHub.

Are there any limits on media migration?

Free accounts support up to 5GB of media transfer per month. Pro and Enterprise plans offer 100GB and unlimited storage respectively. Unsupported formats are automatically converted to WebP/MP4.

Troubleshooting

✅
Stuck? Check our Support Portal or join the #migration-help channel in our official ConnectHub community.
Error: "Validation failed: Mismatched user IDs"

This occurs when source emails/IDs don't match ConnectHub's verification format. Run ch-migrate validate --fix-ids to automatically standardize identifiers before re-running.

Error: "Rate limit exceeded during media upload"

ConnectHub throttles bulk uploads to protect infrastructure. Add --batch-size 50 and --delay 1000 to your CLI command, or schedule the migration during off-peak hours.