How to Migrate from KVS to TubePress

Moving an established tube site to a new CMS feels risky — but the two things operators worry about most, losing their library and losing their Google rankings, are both very manageable. This guide walks through migrating from KVS (Kernel Video Sharing) to the free, self-hosted TubePress CMS without dropping either.

The short version: export your catalogue from KVS, bulk-import it into TubePress with column mapping, preserve your URL structure (or set clean 301 redirects), let TubePress regenerate your sitemaps and structured data, then re-point DNS once you have verified everything on a staging URL. For a side-by-side of the two platforms first, see the TubePress vs KVS comparison.

Why migrate from KVS in the first place?

KVS is a capable, mature product, so migrating only makes sense if its trade-offs are costing you. The usual reasons operators switch:

• Cost. KVS is a paid commercial license (roughly $99–$499 one-time per domain, or about $49/month rental). TubePress is free, on unlimited sites you own, with free updates forever.
• Encoded code. KVS ships ionCube-encoded by default, so you cannot read or freely modify the core. TubePress is plain, editable PHP with no ionCube — you own and can audit every line.
• Per-domain lock-in. Running a network of sites multiplies KVS license costs; with TubePress the same build runs everywhere for $0.

If none of those hurt you, there may be no reason to move. If they do, the rest of this guide is the practical path out.

Before you start: what you will need

• Access to your current KVS admin and database (to export your video metadata).
• A server that meets the TubePress requirements (PHP 8.2+, MySQL/MariaDB, Nginx or Apache).
• A fresh TubePress install on a staging URL or subdomain — never migrate directly onto your live domain. Download it from the download page and run the 5-minute installer.
• A backup of your KVS database and files. Always migrate from a copy, never the only copy.

Step 1 — Export your library from KVS

TubePress imports from CSV or JSON, so the goal of this step is a clean export file with one row per video. Export your catalogue from the KVS admin (or directly from its database) and include the fields you want to keep: title, description, tags, categories, performers/models, duration, thumbnail URL, video file URL or storage path, upload date, and view count.

You do not have to migrate everything at once. Many operators export in chunks (by category or date range) and import them as separate batches, which keeps each pass small and easy to verify.

Step 2 — Map your KVS fields to TubePress

TubePress’s importer lets you map your columns onto its own fields, so your KVS export does not have to match a fixed template. Line up each source column (for example video_title → Title, cat → Category, models → Performer) once, and the mapping applies to the whole file.

This is also the moment to tidy taxonomy: collapse duplicate categories, normalise tag casing, and split comma-separated performer fields so your new site starts clean rather than inheriting years of drift.

Step 3 — Bulk-import into TubePress

Run the import on your staging site. The TubePress importer streams CSV/JSON files of any size in resumable batches, with duplicate detection and batch category/tag assignment, and there is no fixed row limit. If a batch is interrupted, it resumes rather than starting over or creating duplicates.

For large libraries, import a few thousand rows first and confirm the result — titles, thumbnails, categories and players all rendering correctly — before running the full catalogue. The step-by-step bulk import guide covers the importer in detail.

Step 4 — Preserve your URLs and protect your SEO

This is the step that decides whether you keep your traffic. Search engines have indexed your KVS URLs for years; if those URLs change and nothing tells Google where they went, you lose the rankings attached to them.

You have two safe options:

• Keep the same URL structure. If you can match your existing video, category and performer URL patterns in TubePress, most links keep working as-is.
• 301-redirect old URLs to the new ones. Where patterns differ, map old → new with permanent redirects so equity transfers. A simple Nginx example:

location ~ ^/video/(\d+)/ {
    return 301 /watch/$1;
}

TubePress then does the ongoing SEO work for you: it emits one clean canonical per page, regenerates XML sitemaps, and outputs hreflang, Open Graph and JSON-LD (VideoObject, BreadcrumbList) automatically. Submit the new sitemap in Google Search Console right after launch so the new URLs are recrawled quickly. The adult tube site SEO guide goes deeper on this.

Step 5 — Handle thumbnails, media and your CDN

Your video files and thumbnails are usually the largest part of a migration, and you often do not need to move them at all. TubePress supports multiple storage backends (local, S3, FTP/SFTP, WebDAV), so you can point it at your existing storage or CDN and keep serving the same files. If you are also changing hosts, move the media separately from the metadata import and verify a sample of URLs resolve before going live.

Step 6 — Verify on staging, then re-point DNS

Before any DNS change, walk the staging site: spot-check video playback, category and performer pages, search, the member area, and a handful of redirected old URLs. Confirm the sitemap builds and that pages return clean canonicals. Only when staging is solid do you re-point your domain — the cutover is then just a DNS change, and your visitors never see a half-migrated site.

Common migration pitfalls to avoid

• Changing URLs with no redirects. The fastest way to lose rankings. Map every old pattern to a new one.
• Importing duplicates. Use the importer’s duplicate detection and import in clean batches rather than re-running overlapping files.
• Migrating onto the live domain. Always stage first; never experiment on the URL that is earning traffic.
• Forgetting the sitemap. Resubmit it in Search Console on launch day so the move is discovered in days, not weeks.

Done in this order, a KVS migration is methodical rather than risky — and at the end you are running a free, fully editable CMS with no per-domain license. When you are ready, download TubePress and set up your staging site.