📄️ Migration Overview
Vidra is fully compatible with PeerTube's REST API (v8.1.0), which means your existing PeerTube clients, embeds, and federation peers continue to work after migration. This guide walks you through the complete process of importing your PeerTube instance into Vidra.
📄️ Planning Your Migration
A successful PeerTube-to-Vidra migration starts with careful planning. This page helps you inventory your existing data, choose a migration strategy, and prepare both environments.
📄️ API-Driven Migration
Vidra includes a built-in Migration ETL API that connects directly to your PeerTube PostgreSQL database, extracts data, transforms it to Vidra's schema, and loads it — all through a set of admin API endpoints. This is the recommended migration path for most operators.
📄️ Manual Migration
This guide walks you through manually exporting data from PeerTube and importing it into Vidra. Use this approach when you can't connect Vidra directly to the PeerTube database, need to transform data before import, or want full control over every step.
📄️ Storage Migration
After importing database records, you need to copy the actual media files — video files, HLS streaming playlists, thumbnails, previews, avatars, and captions — from PeerTube's storage to Vidra's storage backend.
📄️ Cutover & Validation
This is the final step — switching traffic from PeerTube to Vidra and confirming everything works. A well-planned cutover minimizes downtime and provides a clear rollback path.
📄️ Troubleshooting
Common issues encountered during PeerTube-to-Vidra migration and how to resolve them.