---
title: "WordPress migration: move or rescue a site safely"
description: "WordPress migration and rescue across local, staging and production without overwriting what the client edited: a plan first, production wins, and a way back."
url: https://lazarosantana.dev/en/services/wordpress-migration/
---

service · migration · local, staging and production

# WordPress migration *and site rescue*

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.

[Request a quote](https://lazarosantana.dev/en/contact/#form) [See ix-wp-envsync](https://lazarosantana.dev/en/projects/ix-wp-envsync/)

What I move

Database, plugins, themes and files

How

Three-way comparison with a baseline, and a plan before anything moves

If something fails

The remote keeps a previous copy and the rollback restores it

Mode

Remote from Havana

// what it solves

## What it solves

Concrete problems that already came up in a real project, not a list of promises.

01

### The client edited while you worked

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.

02

### Two copies of the same site

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.

03

### A push that gets interrupted

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.

04

### An existing site that needs sorting out

claude-wp-builder includes tools for existing sites, and its audit reviews a site across seven areas with every finding in a work list.

// proof

## Real proof

**3** versions compared in every diff: baseline, local and remote

**6** comparison cases, each with a clear outcome

**1** previous copy on the remote before every push

**7** audit areas in claude-wp-builder, for sites that already exist

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.

co-authored project · open source

### Sync WordPress without overwriting anyone

ix-wp-envsync keeps a site up to date across local, staging and production: it pushes only what the team changed and shows a plan before anything moves.

// how it works

## How it works

01 · what to move 02 · baseline 03 · plan 04 · push 05 · way back

01

### What to move

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.

- source and target
- existing site
- hosting

02

### Baseline

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.

- pull
- baseline
- three versions

03

### A plan before moving

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.

- diff
- conflicts by name
- plan

04

### Move

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.

- only your changes
- previous copy
- production wins

05

### Way back

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.

- rollback
- lock
- no losses

My site is local and the client keeps editing in production

Then I don’t copy everything: only what the team changed goes up

And what the client edited?

It is respected. I show you the plan first

example conversation

ix-wp-envsync

go up

kept

conflict

✓ plan approved plan · nothing moves until it is approved

local *→* staging *→* production

no SSH on production: the remote only needs the plugin and a token

every push has a way back

// questions

## Frequently asked

### 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.

### Can I see what will change before anything moves?

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.

### What if the push goes wrong?

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.

### What do you mean by rescue?

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.

// let’s talk

## Got something like this in mind?

Tell me what you sell, to whom and what has to happen. I reply within 24 h.

[Request a quote](https://lazarosantana.dev/en/contact/#form)
