IDEI Move – Backup, Migration & Restore
IDEI Move – Backup, Migration & Restore
Description
IDEI Move helps you back up and migrate a WordPress site using a verified .ideimove file. Export your database, media, plugins, themes and translations; download a copy; then import it into another WordPress installation or restore it on the same server.
Developed by IDEIWEB and IDEIDEV. The interface includes English, Spanish and French and follows your WordPress profile language, falling back to the site language.
Back up your WordPress site
Choose the components you need and start an export. IDEI Move creates a local backup and checks its integrity before offering the download. Keep a downloaded copy outside your hosting account for recovery if that server becomes unavailable.
- Select database, media uploads, plugins, themes and translations.
- See the current stage, processed entries, database rows and transferred bytes.
- Pause and resume a job from its saved checkpoint.
- Download, restore or delete completed backups from the backup list.
Migrate to a new domain or hosting account
- Export and download a .ideimove backup on the source site.
- Install WordPress and IDEI Move on the destination.
- Upload your backup, wait for verification and review the source and destination.
- Save the recovery code, confirm the replacement and restore.
When the backup includes the database, IDEI Move adapts source site URLs and filesystem paths to the destination, including serialized values and JSON. The destination keeps its configured WordPress and site addresses. Post GUIDs are preserved. DNS records, HTTPS certificates and URLs hardcoded in theme or plugin files need separate configuration.
Follow upload, download and restore progress
AJAX uploads send 1 MiB chunks and resume from the last chunk acknowledged by the server. The progress display distinguishes bytes sent from bytes saved.
Downloads use 1 MiB HTTP ranges with a progress bar. For files above 64 MiB, writing directly to disk requires a desktop browser that supports the file picker, such as Chrome or Edge, in a secure context. Other browsers can use Download with the browser and its download manager.
Progress percentages refer to the named stage. When the total is unknown, the display shows activity and processed entries. Time remaining appears only when it can be estimated from observed transfer speed.
Restore with a recovery path
Before replacement, the package is checked and its files are staged in private storage. You review the operation before confirming. During replacement, the site enters maintenance and previous files and tables are retained for rollback.
Save the job’s recovery code before restoring. Its dedicated recovery page can control that job without a WordPress login while the key remains valid. Recovery keys expire after 24 hours and can be renewed by opening the job in the administrator.
Privacy and operation
No external account, paid license, cloud connection or telemetry is required by IDEI Move. Your backups stay on your server until you download or delete them. Keep the job tab open so work can advance.
Backups may contain personal data and credentials from your site. Store downloads and recovery codes privately. Uninstalling version 2.0 preserves backup files and plugin data.
Upgrading from Migrator & Backup by IDEIWEB 1.x
IDEI Move 2.0 replaces the previous engine under the same WordPress.org listing. Version 2.0 imports .ideimove packages only. It does not import legacy ZIP or .wpress packages and does not include scheduled backups or Wasabi storage.
Before upgrading, download legacy backups you need and finish any running legacy job. Update the existing plugin; do not uninstall version 1.x first. The update retains its backup files and settings and retires its scheduled tasks. Legacy backups are not listed by the new engine. Create a new .ideimove backup after updating. See the included upgrading guide for recovery options.
Installation
- In WordPress, open Plugins > Add New Plugin and search for IDEI Move, or upload the release ZIP.
- Activate IDEI Move and open its dashboard.
- Check server diagnostics, then use Export to create your first backup.
- For migration, install the plugin on the destination and use Import there.
Requires single-site WordPress 6.5 or newer, 64-bit PHP 7.4 or newer with zlib, writable storage and sufficient disk space. Database restoration requires permissions to create, write, alter, rename and drop tables.
Restore preparation needs a private directory outside the public web root on the same filesystem as the destination files. If automatic selection cannot find one, define IDEI_MOVE_PRIVATE_DIR in wp-config.php with an existing suitable directory. IDEI_MOVE_STORAGE_DIR optionally changes backup storage.
The plugin ZIP includes detailed English, Spanish and French guides in docs/. No Composer or Node installation is needed on your server.
Screenshots
Faq
How to migrate explains the workflow. Export creates a backup of the current site. Import uploads and restores a backup into the site you are currently using. Backups lists files kept on that server. To move a backup elsewhere, download it and import it on the other site.
If the database is included, source home/site URLs and paths are replaced with the destination values, including serialized data and JSON. Review both addresses before confirming. File-only restores do not rewrite the database.
Use an administrator account from the source site. Imported users replace the corresponding destination users. Save the recovery code before starting; the plugin does not create a hidden account.
Pause orders, editorial changes and other database writers while exporting. The export spans multiple requests and is not a transactionally consistent snapshot of the entire live site.
There is no paid size unlock. Real limits depend on hosting, free disk space, filesystem support, timeouts and browser download support. A database row record is limited to 16 MiB. A synthetic 20 GiB archive engine test does not certify every 20 GiB site or a full browser migration at that size.
Reopen the job and choose Resume. For an interrupted upload, select the same file again. Restart an interrupted download. If a restore has already changed files or tables, use its recovery page to resume or roll back. Deleting a job removes its retained recovery material.
WordPress core, wp-config.php, root files, MU-plugins, drop-ins, IDEI Move itself and its backup storage are excluded. Files absent from the package remain at the destination. Symlinks and nonportable paths are rejected. Multisite, direct server connections, scheduling and remote cloud storage are not included.
Standard WordPress tables and compatible plugin tables are supported. Views, foreign keys, generated columns, CHECK constraints and unsupported SQL definitions are rejected explicitly. Test a restore in staging when your site uses custom database structures.
Choose English, Spanish or French in Users > Profile > Language, or use the site default from Settings > General. Regional Spanish and French locales use the bundled translation when no exact language pack is available. This changes the plugin interface, not your site’s content.
Use the WordPress.org support forum. Include WordPress/PHP versions, the current job stage and the error text. Never post backups, passwords, recovery codes or private database content.
Reviews
Changelog
2.0.2
- Fix open_basedir failures on restricted hosting while retaining symlink and junction checks.
2.0.1
- Fix export startup after job-list failures.
- Add authenticated export fallback when the direct worker is blocked.
- Show stopped processing, HTTP errors and response timing.
- Speed up database export with resumable batches.
2.0.0
- Rebuilt as IDEI Move with verified .ideimove export, import and local backup restoration.
- Added resumable uploads, AJAX download progress, phase progress and restore recovery.
- Added destination URL replacement for serialized values and JSON.
- Included English, Spanish and French across the interface, errors and recovery page.
- Preserved the published plugin identifier for upgrades and retained legacy backup files.
- Retired the previous ZIP/.wpress engine, scheduling and Wasabi integration.



