Easy Staging Migration by Gami

Easy Staging Migration by Gami gives WordPress sites a practical staging and backup workflow:

1. Create a staging copy from production.
2. Migrate a development or local WordPress backup into staging when the work starts outside production.
3. Review updates, design changes, plugin changes, or content edits on staging.
4. Keep backups available before important work.
5. Use release previews to understand what would change, then publish reviewed staging changes when ready.

The plugin runs without an account or remote service. It handles production-to-staging sync, development-to-staging migration, backups, scheduled backups, imports, exports, dry-runs, staging-to-production publishing, and safety checks.

View screenshots: https://wp-simple-staging.gami.jp/en#screenshots

Watch a short walkthrough video: https://wp-simple-staging.gami.jp/en#demo

Included features

• One-button production-to-staging sync.
• Development, local, or test-site backup import into staging.
• Protected staging directories with Basic Auth, noindex rules, robots.txt, and staging-only safety guards.
• Complete manual backups before important work.
• Scheduled backups through WP-Cron.
• Backup restore, download, delete, and keep actions.
• Separate Migration menu for backup import and export workflows.
• Migration export that creates a backup-compatible file and starts its download automatically when ready.
• PUSH menu for plugin, core, and full-site release presets.
• Dry-runs and live release operations for files, database tables, plugins, core files, and full-site release scope.
• A simple difference review that lets you keep the production or staging version of each changed post, page, category, tag, or term before a target is replaced.
• Advanced mode for scoped file and database previews or releases.
• Progress indicators for long-running Get and release actions.
• Operation locks and preflight checks.
• WP-CLI commands for large jobs.
• Support diagnostics that are sent only when an administrator chooses to send them or enables automatic error reports.

Advanced mode

Most sites can use GET, PUSH, Migration, and Backup. Advanced settings provide selected file and database table previews, high-risk table warnings, and operation locks for long-running jobs. Release actions are previews by default. Live production releases require a backup confirmation, a confirmation checkbox, and a typed phrase.

Difference review

Before a GET refresh or production publishing workflow overwrites a target, the plugin can show posts, pages, categories, tags, and terms that changed on the target since the last sync.

The review is intentionally simple. Each changed item gets one choice: keep the production version or keep the staging version. There are no separate choices for individual fields. Metadata-only changes, such as a post’s sticky state, are detected as part of the same item-level choice.

Full-table and plugin-specific data can still be broad in scope, so keep backups available before release work.

Staging-created sites

On a site created as staging, GET and PUSH stay visible but cannot be run. Run those operations from the production WordPress admin. Migration import and export, backup creation and history, scheduled backups, restore and delete, and support diagnostics remain available on staging.

Backups

Create complete backups before important work, restore or download them, protect selected backups from retention cleanup, and configure scheduled backups. Use Migration to move backup files between environments. Managed backups are local and do not replace host-level or off-server backups.

Full Site PUSH safety

• Release safety database backups are rolling per-table backups. Each table is copied and verified individually; this is not a single point-in-time snapshot of the entire database.
• Each production table is switched with an atomic RENAME, and the table that existed immediately before that switch is retained as a rollback table.
• Full Site PUSH is destructive. Pause orders, form submissions, post updates, and other writes, then run it during a maintenance window. A concurrent write can be overwritten by staging data and may exist only in the retained rollback table; zero-downtime and zero data loss are not guaranteed.

Privacy

Easy Staging Migration by Gami stores plugin settings, operation history, and managed backup metadata locally in WordPress. Managed backups are stored on the server and can contain site files and database tables selected by an administrator.

Support reports are not sent by default. When an administrator sends a report or enables automatic error reports, safe diagnostics can be sent to the configured support recipient. The plugin is designed to exclude secrets and table contents from those diagnostics.