compare
Loopress, next to what you use today.
Most WordPress devs already have a way to move changes between sites. Here is where each one fits, and where Loopress does something different.
What it does
| Leaves the site layout as is | ACF field groups in Git | Menus and options in Git | Diff before you ship | Content stays untouched | No SSH | |
|---|---|---|---|---|---|---|
| Loopress | yes | yes | yes | yes, per file | always | yes |
| ACF Local JSONthe built-in option | yes | yes | no | in the theme's Git history | yes | yes |
| WP Staging and Duplicatorstaging and migration plugins | yes | no | no | no | only if you exclude tables | yes |
| WP Migratedatabase sync | yes | no | no | no | only if you exclude tables | yes |
| Roots Bedrocka project structure | no | no | no | code only | yes | Trellis needs it |
| VersionPressarchived | yes | yes | yes | yes | no, versioned too | yes |
What Loopress doesn't do
| Full site backups | Clone or move a whole site | Move content, posts and media | WordPress core version in code | |
|---|---|---|---|---|
| Loopress | no | no | no | no |
| ACF Local JSONthe built-in option | no | no | no | no |
| WP Staging and Duplicatorstaging and migration plugins | yes | yes | yes | no |
| WP Migratedatabase sync | database export | yes | yes | no |
| Roots Bedrocka project structure | no | no | no | yes, via Composer |
| VersionPressarchived | no | no | versioned in Git | no |
loopress moves configuration and code, nothing else. keep your backup and migration tools, they do a different job.
The short version
- ACF Local JSON: ACF can already save field groups as JSON in your theme. If field groups are all you need in Git, that may be enough. Loopress starts where it stops.
- WP Staging and Duplicator: Staging and migration plugins copy a whole site, database included. Loopress moves only the configuration and code you changed, and never the content.
- WP Migrate: WP Migrate pushes and pulls databases between environments, with find and replace on URLs. Loopress moves configuration as files, one resource at a time.
- Roots Bedrock: Bedrock restructures a WordPress project around Composer. Loopress leaves the site as it is and puts its configuration and code in Git.
- VersionPress: VersionPress tried to put the whole database in Git, content included. Loopress takes the opposite constraint.