co-authored project · open source

Sync your
WordPress
without
overwriting
anyone

ix-wp-envsync keeps a WordPress site in step across local, staging and production. It pushes only what the team changed, keeps what the client changed and shows a plan before anything moves.

wp envsync diff prod
Plan
  • push local
  • respect the remote
  • remote wins
Nothing moves until you approve the plan
What it is

A WordPress plugin that syncs local, staging and production with a three-way compare

Authorship

Co-authored with Yojahny Chavez, maintained by two since September 2026

Who it is for

Freelance work on mixed hosting (Hostinger, IONOS, Plesk, Coolify), no SSH on production

License

Open source on GitHub, GPL-2.0 or later, version 0.9.22

// how it thinks

Three versions, one decision

Comparing just two sites cannot say who changed what. So every pull stores a baseline, a fingerprint of the site at that moment, and every diff compares three versions: the baseline, local and the remote (staging or production).

01

Pull before push

Without a baseline only two sides can be compared, and the plugin says so instead of guessing.

02

Prod wins

If the team and the client changed the same row, production's version is kept and the local edit is not applied.

03

Conflicts in plain sight

Each conflicting row or file is listed by name, to review before every push.

04

Files like rows

An edited theme file goes up. A plugin that auto-updated on production stays as it is.

// try a case

Pick what happened to one row on local and on the remote, and the plan shows which version survives. They are the same rules as the list, one by one.

  1. 01You changed a row, production did notPushed
  2. 02Production changed a row, you did notKept, not touched
  3. 03You both changed the same rowProduction wins, reported as a conflict
  4. 04You created a rowInserted
  5. 05You deleted a row, production did not touch itDeleted
  6. 06Production deleted or changed it, you deleted itKept
// which site is which

One laptop, one client

The site the commands run from is the hub and needs WP-CLI. Every remote, usually production or staging, needs only the plugin and a token. Requests are signed and the token never travels.

diagram · hub and remote
Tools → EnvSync
The Tools, EnvSync screen of the WordPress dashboard, showing the site token, the environments, the last pushes and the sync excludes, with example data
  • Site tokenThe one copied into the hub to register this site as a remote.
  • EnvironmentsName, label, URL and baseline of each registered remote.
  • Last pushesWhen each environment was pushed to, and how many rows and files.
  • Sync excludesTicked folders (here cache and backups) are skipped by pull, diff and push.
// a working day

Five commands, no surprises

  1. 01

    Status

    Says where each site stands and which command comes next

  2. 02

    Pull

    A fresh copy of production, and the baseline is recorded

  3. 03

    Diff

    A preview of what would change. It only reads and counts, nothing moves

  4. 04

    Push

    Shows the plan and asks to confirm. The remote keeps a pre-push copy; --dry-run writes nothing

  5. 05

    Rollback

    If something looks wrong, restore the pre-push copy. What the client changed is kept

If a push dies half-way, unlock releases the lock without undoing anything.

On a fresh WordPress install, status recommends push --force --dry-run before sending anything.

// reading a diff

One row, one column

The diff reads and counts, it changes nothing. Each row lands in one column only. The terminal below is the plugin’s real output, with example data; it is selectable and copyable. Hovering a column, or tapping a note, highlights what it counts.

wp envsync diff prod · real output, example data
$ wp envsync diff prod

prod  ←  local
  baseline: 2026-09-08 02:06
  512 files · 38.4 MB · 131 rows

DATABASE
                                                                
+-------------+------+--------+--------+-------------+-------------+-------+
| table       | push | insert | delete | remote-wins | kept-remote | same  |
+-------------+------+--------+--------+-------------+-------------+-------+
| wp_posts    |   12 |      3 |      1 |           2 |          39 |   611 |
| wp_postmeta |   87 |     19 |      4 |           0 |         310 |  8904 |
+-------------+------+--------+--------+-------------+-------------+-------+

PLUGINS 
+-----------------------+-------+--------+-----------------+----------+
| plugin                | files | size   | version         | active   |
+-----------------------+-------+--------+-----------------+----------+
| polylang              |   535 | 9.8 MB | 3.6.1 → 3.7.0   | stays on |
| wp-mail-smtp          |   875 | 7.2 MB | — → 4.4.0       | turns on |
+-----------------------+-------+--------+-----------------+----------+

THEMES
+--------------+-------+--------+---------+--------+
| theme        | files | size   | version | active |
+--------------+-------+--------+---------+--------+
| mk-adventure |    14 | 0.3 MB | 1.4     | active |
+--------------+-------+--------+---------+--------+

OTHER FILES
+---------------+-------+---------+
| folder        | files | size    |
+---------------+-------+---------+
| uploads/2026/ |    88 | 21.1 MB |
+---------------+-------+---------+

CONFLICTS (prod wins) 
  wp_posts             #2231  Services

plan saved: …/plans/plan-prod-20260908-020644.json
manifest: …/plans/diff-prod-latest.json
// try it

Install in 3 steps

It installs as one more plugin on each site and runs from WP-CLI.

  1. Plugin on every site

    Upload the plugin zip in Plugins → Add New → Upload and activate it, on the local site and on every remote.

  2. The remote’s token

    On each remote, open Tools → EnvSync and copy the token shown there.

  3. Register and check

    On the local site (the hub), register the remote and check the connection. status says whether it works and which command comes next.

terminal · on the hub
# register the remote# check the connection

Start with a staging site. The first diff changes nothing.

← all toolsco-authored project
// your project

Got a project in mind?

Tell me what you need. I reply within 24 hours and, if it is a fit, you get a fixed written proposal.