WPLLMT

WordPress Low Level Migration Tool

Fast SFTP sync + MySQL migration UI for server-to-server WordPress moves. Privacy-first by default with local-only per-window state and a built-in integrity checker.

One-way SFTP sync Full MySQL refresh Local-only state (per window) Integrity checker
Open-source on GitHub

Reliable sync control

Configure SFTP concurrency, monitor per-file progress, and keep a clear history of runs and synced files. Manual connect, refresh, and logout keep workflows precise.

Clean MySQL migrations

Full-refresh migrations drop destination tables, recreate the schema, then bulk-insert rows in batches. Batch size is adjustable so you can balance speed with safety.

Privacy-first UX

Credentials, paths, and UI state live in the browser only. The server holds only in-memory job state during a run and never persists logs or secrets.

How WPLLMT works

SFTP Sync

One-way sync (source → destination) with configurable concurrency and retry backoff. Skip logic checks path + file size to avoid re-transfers.

MySQL Migration

Full refresh: drop destination tables, recreate the schema, then bulk-insert rows. Batch size is configurable directly in the UI for large datasets.

Integrity Checker

Compare a remote SFTP path against a local folder using the browser’s folder picker (File System Access API; directory input fallback). Only file names and paths are read — never file contents.

Local State Controls

Each window has its own local state and can be reset individually or globally. History and reports are stored in IndexedDB for fast recall.

Interface preview

Clean, focused workflows for SFTP, MySQL, and integrity checks — built for fast, repeatable migrations.

Built for migration teams

WPLLMT is ideal for agencies, operators, and developers moving WordPress installations across servers. It keeps everything transparent: real-time counters, per-run history, and a no-surprises workflow you can trust.

No server-side persistence Per-window isolation Vercel-compatible deployment

Note: long-running sync jobs may exceed serverless timeouts on Vercel. For large migrations, use a long-lived Node host.