Easy Staging Migration by Gami

Descripció

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.

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.

Captures

Instal·lació

  1. Install “Easy Staging Migration by Gami” from the WordPress plugin directory, or upload the plugin ZIP in the WordPress admin.
  2. Activate the plugin.
  3. Open Easy Staging Migration by Gami from the WordPress admin menu.
  4. Review the staging URL, staging path, database mode, and table prefix.
  5. Click Get: Production -> Staging and confirm the staging update.
  6. To migrate work from a development or local site, import the backup into staging and review the result there.
  7. Review the staging site.
  8. Use release previews before publishing staging changes to production.

PMF

Does the plugin require an account?

No. The WordPress.org plugin works without an account or external service registration.

What is included in the WordPress.org plugin?

You can create and refresh staging, migrate a development or local backup into staging, protect the staging site, create complete backups, schedule backups, import backups, restore backups, run release dry-runs, and publish reviewed staging changes to production.

Does the plugin overwrite production?

Only when an administrator explicitly runs a live release. Release actions are previews by default, and live production writes require confirmation checkboxes and a typed phrase.

Can I review content differences before an overwrite?

Yes. Before GET refreshes and publishing workflows, the plugin can list posts, pages, categories, tags, and terms that changed on the target since the last sync. For each item, choose whether to keep the production version or the staging version.

Is staging-to-production publishing included?

Yes. Administrators can review post, page, and taxonomy differences before publishing staging changes to production. Advanced release presets still require previews and live-release confirmations.

What can I do on a site created as staging?

GET and PUSH stay visible but cannot run. Migration import and export, backup creation and history, scheduled backups, restore and delete, and support diagnostics remain available.

Can visitors or search engines access staging sites?

Staging directories are protected by Basic Auth by default on Apache-compatible servers and receive noindex headers and robots.txt rules. Servers that do not honor .htaccess may need matching server-level rules.

Does this replace host-level backups?

No. The plugin creates managed local backups for rollback support, but host-level or off-server backups are still recommended before important production releases.

Does the plugin send telemetry?

No telemetry is sent by default. Support reports are sent only when an administrator sends one manually or explicitly enables automatic error reports. Reports are designed to exclude passwords, salts, API keys, database passwords, Basic Auth passwords, user lists, and table contents.

Ressenyes

No hi ha ressenyes per a este complement.

Col·laboradors i desenvolupadors

«Easy Staging Migration by Gami» és programari de codi obert. La següent gent ha col·laborat en este complement.

Col·laboradors

Registre de canvis

0.8.17

  • Hardens migrations between root, WordPress-subdirectory, and full-subdirectory installations by rewriting URLs and filesystem paths with source-aware boundaries.
  • Preserves PHPDoc, CSS comments, and Gutenberg block markup while rewriting root-relative URLs, including escaped, percent-encoded, serialized, base64, and CRLF forms.
  • Improves resumable imports and history restores with owner- and context-bound state, cross-operation locking, chunk fingerprints, and reliable cleanup.
  • Preserves database charset and emoji data, normalizes Windows-to-POSIX paths, and keeps staging-only files and runtime plugin aliases out of production restores.
  • Rejects destructive multisite operations early and expands regression coverage for large archives, interrupted operations, and cross-topology restores.

Older release notes are kept in changelog.txt.