WordPress development Product · WordPressGPL-3.0-or-later

Octarine-owned product

Move WordPress
in manageable stages.

A pull-based WordPress plugin for staged, resumable migrations of database tables, media, active themes, and plugins.

View Site Migrator on GitHub
The problem

WordPress migrations can turn into a fight with export sizes, browser waits, PHP limits, proxy limits, and hosting timeouts.

The product

Move the work
in smaller steps.

Pull from the target site

Stage before replacing

Resume interrupted work

Why it exists

Less waiting.
More visibility.

Site Migrator moves the work into smaller authenticated requests, stages it on the target, and gives the administrator visible progress instead of one opaque “please wait”. That reduces timeout pressure. It does not make hosting limits disappear; if a limit is reached, the failure stays tied to a smaller stage.

How it worksConnect · Stage · Apply
01

Connect, then verify.

Install Site Migrator on both WordPress sites. The source shares its site URL and generated authentication code; the target checks the connection before anything moves.

The source pull endpoint is explicitly enabled from Tools → Site Migrator. The verification response includes the WordPress version, site, multisite state, and current blog context.

02

Download into staging.

The target reads a manifest, then pulls database tables, media, the active theme, and active plugins in smaller steps instead of building one oversized export.

Rows are paged, files are handled individually, and the target writes the download to wp-content/migrator-staging/. WordPress.org plugins can be installed from WordPress.org instead of copied.

03

Review, then apply.

Nothing is replaced during the download. The target shows what is ready, with a separate confirmation before the destructive apply step.

Apply creates temporary database tables, imports staged rows, copies files in batches, can update the target URLs, and then cleans up the staging area.

04

Resume when real life happens.

A reload, an interrupted request, or a long migration does not have to mean starting from zero.

Progress is persisted. Completed staging can be detected and applied later; cancellation removes the staging data for a clean restart.

MultisiteA specific, useful path

A subsite
can move.

Site Migrator supports pulling a correctly selected WordPress multisite subsite into a single-site target when the migration is started from that subsite’s admin context. The source reports its current blog context and uses that site’s tables and uploads.

It is not a full multisite-network-to-multisite migration tool. Network-wide user tables may be included, so review the source and target before applying the migration.

Know the edgesUseful because it is honest

A migration tool
with boundaries.

  • No incremental sync between sites that have already been migrated.
  • No rollback after apply; the final apply replaces target content and files.
  • Only active themes and plugins are included. mu-plugins are out of scope.
  • Individual files over 25 MB are not transferred.
  • Premium plugin licensing is not handled automatically.
  • Full multisite-network-to-multisite migration is outside the primary flow.
  • Source and target require WordPress 6.0+, PHP 7.4+, and administrator access.
Site Migrator

Planning a
WordPress migration?

hello@octarinestudio.ukRead the source and documentation on GitHub