Is anything the client edited lost?
If the team and the client changed the same row, the production version stays and the local edit is not applied. Every conflict is listed by name. What only the client changed is left alone.
I move WordPress sites between local, staging and production, or to a fresh install, without overwriting what the client edited in the meantime. Every move starts with a plan that shows what changes, production wins on conflict and every push has a way back.
Database, plugins, themes and files
Three-way comparison with a baseline, and a plan before anything moves
The remote keeps a previous copy and the rollback restores it
Remote from Havana
Concrete problems that already came up in a real project, not a list of promises.
If everything is copied from local to production, the client’s changes are lost. Here only what the team changed goes up, and what the client changed is respected.
Comparing only two sides does not say who changed a row. Every pull stores a baseline, and every diff compares three versions: the baseline, local and the remote.
If a push dies halfway, one command releases the lock without undoing anything. And before every push the remote keeps a previous copy for the rollback.
claude-wp-builder includes tools for existing sites, and its audit reviews a site across seven areas with every finding in a work list.
The plugin has been used with mixed hosting (Hostinger, IONOS, Plesk and Coolify), with no SSH on production: the remote only needs the plugin and a token.
You tell me from where to where: local, staging, production or a fresh install, and what the client has changed in the meantime. If the site already exists and is a mess, we start from there.
I run a pull and store a baseline. That way every diff compares three versions, the baseline, the local one and the remote’s, and knows who changed each row.
The diff only reads and counts: how many rows go up, how many are kept and which are in conflict. It saves the plan and nothing moves until you approve it.
With the plan approved I run the push and only what the team changed goes up. Before that, the remote keeps a previous copy; if there is a conflict, production wins.
If the push goes wrong, the rollback restores the previous copy without losing what the client changed. If it is interrupted, one command releases the lock without undoing anything.
If the team and the client changed the same row, the production version stays and the local edit is not applied. Every conflict is listed by name. What only the client changed is left alone.
Yes. The diff command only reads and counts: how many rows go up, how many are kept and which ones conflict. It saves the plan and nothing moves until it is approved.
The remote keeps a previous copy before every push and the rollback restores it without losing what the client changed. If a push is interrupted, one command releases the lock without undoing anything.
A site that exists and needs sorting out: two copies that drifted apart, an environment with no staging or a theme with faults. There is no published malware-cleanup case here, so I do not offer it.
Tell me what you sell, to whom and what has to happen. I reply within 24 h.