=== IDEI Move – WordPress Migration, Backup & Restore ===
Contributors: ideidev, ideiweb
Tags: backup, migration, restore, export, import
Requires at least: 6.5
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 2.2.1
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Free WordPress migration and backup plugin. Move a site to a new host or domain, restore verified backups, and add Google Drive or SFTP.

== Description ==

**IDEI Move is a free WordPress migration, backup and restore plugin built around a verified .ideimove file.** Move a WordPress site to a new domain or hosting provider, clone it to staging, or keep a recoverable local backup. Export your database, media, plugins, themes and translations; download the package; then import it into another WordPress installation or restore it on the same server.

**[Visit IDEI Move](https://ideimove.com/plugins-wordpress/) to see all available extensions, upcoming connections and purchase options.** The free plugin remains fully usable without buying an extension.

IDEI Move is developed by **IDEIWEB, IDEIDEV and IDEI Hosting**. The interface includes **English, Spanish, French, German and Italian** and follows your WordPress profile language, falling back to the site language.

= Why choose IDEI Move for WordPress migration? =

IDEI Move is designed for people who want to understand what will happen before a WordPress site is replaced. The source creates a verified backup, the destination validates it, and the restore screen shows the source URL, destination URL and selected components before asking for confirmation.

* **Free migration, backup and restore:** local export, download, import, URL replacement and restore do not require a paid license.
* **Verified backup format:** indexes, sizes and checksums are checked before a package can be restored.
* **Resumable work:** exports retain checkpoints and browser uploads resume from the last byte confirmed by the server.
* **Visible migration progress:** follow the current stage, files, rows and transferred bytes instead of waiting behind an indefinite spinner.
* **Recovery controls:** save a private recovery code and retain previous files and tables while a restore can still be rolled back.
* **Honest hosting limits:** there is no paid file-size unlock. The real limits are the server, disk, filesystem, database and browser.
* **Optional remote storage:** add Google Drive or SFTP only when your workflow needs an off-site destination.

= How to migrate a WordPress site to another host =

1. Install IDEI Move on the current WordPress site and create a backup containing the database and the files you need.
2. Download the verified `.ideimove` file and keep the original hosting account available until the new site has been checked.
3. Install a fresh WordPress and IDEI Move on the destination hosting account, then upload and validate the backup.
4. Review the source and destination addresses, save the recovery code, confirm replacement and restore.
5. Sign in with an administrator from the source site, check pages, forms, media, caching and permalinks, then complete DNS and HTTPS changes outside the plugin.

The workflow can be used when moving between hosting providers, shared hosting, a VPS or a managed WordPress platform, provided both installations meet the documented server requirements. IDEI Move transfers the site through a downloaded backup file; it does not open a direct server-to-server connection.

= WordPress backup and restore =

Use IDEI Move before updates, redesigns, hosting changes or other work that may need a recovery point. A local backup can include the WordPress database, media library, plugins, themes and translations. Completed backups can be downloaded, restored on the same site or imported into another WordPress installation.

For a safer backup strategy, keep at least one verified copy outside the server that created it. Optional Google Drive and SFTP extensions can send a completed local backup to remote storage. A remote connector is not required to use the free local backup and restore functions.

= Common WordPress migration use cases =

* Move WordPress to a new hosting provider or server.
* Change a WordPress domain while updating serialized URLs and JSON values.
* Clone a site into a separate staging installation for testing.
* Create a manual recovery point before updating themes or plugins.
* Restore a downloaded backup after a hosting or configuration problem.
* Schedule daily local backups and optionally send verified copies to Google Drive or SFTP.
* Manage migration and backup workflows for several client URLs with an optional IDEI Move license.

= For developers, agencies and hosting teams =

The package format records component paths, raw sizes and checksums. Jobs expose stages and checkpoints, while server diagnostics report the environment before work begins. The restore flow rejects unsafe paths, symbolic links, unsupported archive metadata and database structures that cannot be migrated safely by the current engine.

IDEI Move deliberately documents exclusions instead of hiding them. WordPress core, `wp-config.php`, root files, MU-plugins and drop-ins are not copied. Multisite and direct server-to-server migration are not currently supported. Review the detailed guides and test important production sites in staging first.

= What is included in the free WordPress plugin? =

The plugin published on WordPress.org is the complete free local migration and backup engine. It does not require an IDEI Move license or a paid account.

* Export the database, media, plugins, themes and translations you select.
* Create and verify a portable .ideimove backup.
* Download local backups and upload them to another WordPress installation.
* Resume interrupted uploads and continue jobs from saved checkpoints.
* Review source and destination URLs before replacing serialized data and JSON.
* Restore locally with maintenance mode, retained recovery material and rollback controls.
* Schedule daily local backups with WordPress cron.

Remote cloud or server storage is optional. It is supplied by separate paid WordPress plugins and does not remove any local feature from this free plugin.

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

Daily scheduled backups are available under IDEI Move > Settings. Choose one or more local times, components and either local storage or an installed remote destination such as SFTP or Google Drive. Scheduled exports advance through bounded WP-Cron tasks; on low-traffic sites, configure a server cron for punctual execution.

= Migrate to a new domain or hosting account =

1. Export and download a .ideimove backup on the source site.
2. Install WordPress and IDEI Move on the destination.
3. Upload your backup, wait for verification and review the source and destination.
4. 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.

= IDEI Move extensions =

The main migration plugin remains free and does not require a license for local export, import, backup or restore. Optional paid plugins add remote storage and use one shared IDEI Move license per WordPress URL.

* **IDEI Move Google Drive** adds OAuth authorization, resumable transfers, remote verification and recovery from Google Drive.
* **IDEI Move SFTP** adds resumable transfers over SSH, server fingerprint verification and remote recovery for a server, VPS or NAS. The current release is SFTP over SSH; it is not plain FTP or FTPS.

See every extension and its current status at **[IDEI Move Extensions](https://ideimove.com/plugins-wordpress/)**, or **[compare plans and buy directly at IDEI Move](https://ideimove.com/precios/)**.

Dropbox, Microsoft OneDrive, Amazon S3, Amazon Glacier and S3-compatible storage for Wasabi, MinIO and Cloudflare R2 are in development and are not sold as finished connectors yet. The public roadmap also includes Google Cloud Storage, Microsoft Azure Storage, Backblaze B2, DigitalOcean Spaces, Box, MEGA, pCloud and WebDAV.

Paid add-ons installed on the same WordPress URL share one site activation. During a migration, the source and destination are two different WordPress sites and therefore use two activations.

= 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 for local backups, migration or restore. Optional paid remote extensions require their own service account and an IDEI Move add-on license; they transfer a locally verified backup only when selected. Manual jobs advance while their tab is open; scheduled jobs use WP-Cron.

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 replaced the previous engine under the same WordPress.org listing. **The current engine imports .ideimove packages only. It does not import legacy ZIP or .wpress packages or include Wasabi storage.** Daily scheduling was reintroduced in 2.2.0.

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 ==

1. In WordPress, open Plugins > Add New Plugin and search for IDEI Move, or upload the release ZIP.
2. Activate IDEI Move and open its dashboard.
3. Check server diagnostics, then use Export to create your first backup.
4. 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 guides in English, Spanish, French, German and Italian under docs/. No Composer or Node installation is needed on your server.

== Frequently Asked Questions ==

= What is the difference between migration, export, import and backup? =

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.

= Does it change the domain automatically? =

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.

= Which login do I use after restoring a 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.

= Can I keep editing the site while exporting? =

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.

= Is there an artificial file size limit? =

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.

= What happens if the connection is interrupted? =

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.

= Which content is excluded? =

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 and direct server-to-server migration are not included. Google Drive and SFTP storage require their separate add-ons.

= Is the WordPress migration plugin free? =

Yes. Local backup, export, import, URL replacement and restore remain available in the free main plugin. Only optional remote connectors such as Google Drive and FTP/SFTP require a paid add-on license. Compare site limits and connector access at [ideimove.com/precios](https://ideimove.com/precios/).

= Can I migrate WordPress to a different hosting provider? =

Yes, when the source and destination meet the requirements listed below. Export on the old host, download the `.ideimove` backup, install WordPress and IDEI Move on the new host, and import there. Keep the old hosting account available until you have checked the restored site and completed DNS and HTTPS configuration.

= Can I migrate to a new domain or keep the same domain? =

Both workflows are possible. When the database is included, IDEI Move uses the destination WordPress addresses and replaces matching source URLs and filesystem paths, including serialized values and JSON. Keeping the same domain normally requires changing DNS after the destination has been tested. Moving to a new domain may also require external 301 redirects, analytics changes and search-engine tools that are outside the plugin.

= Will a WordPress migration protect my Google rankings? =

The plugin preserves post GUIDs and can adapt matching URLs inside the database, but no migration plugin can guarantee search rankings. For a hosting change on the same domain, keep the URL structure and minimize downtime. For a domain change, prepare one-to-one 301 redirects, update canonical and sitemap settings, verify the new property in Google Search Console and monitor crawl errors. DNS, redirects and Search Console are not configured by IDEI Move.

= Can I migrate a WooCommerce site? =

IDEI Move can include WooCommerce plugin files and compatible WordPress database tables, but the export is not a transactionally consistent snapshot of an active store. Pause orders, subscriptions, stock changes and other writers while creating the final backup. Test the restore in staging, then verify payment credentials, webhooks, scheduled actions, emails, taxes and checkout before reopening the destination. Custom tables using unsupported database structures are rejected rather than silently altered.

= Can I clone WordPress to a staging site? =

Yes. Create a backup on production, install a separate single-site WordPress for staging, import the package and review the source-to-destination URL change. Protect staging from public access and search indexing, and do not overwrite production with later staging data unless you have planned how to preserve new live content.

= Does IDEI Move support large WordPress sites? =

The engine writes the archive incrementally and browser uploads use 1 MiB chunks, so the entire package is not loaded into memory at once. There is no paid size unlock in the free plugin. Actual capacity still depends on available disk space, 64-bit PHP, filesystem behavior, database rows, web-server rules and browser download support. Test your real site; a synthetic archive test is not a promise for every hosting environment.

= Can I automate WordPress backups? =

Yes. Daily schedules are available in IDEI Move > Settings. Choose up to twelve WordPress-local times, components and a destination. WP-Cron runs when the site receives traffic; configure a real server cron calling `wp-cron.php` when punctual unattended execution matters. Google Drive or SFTP scheduling requires the corresponding extension and license, while scheduled local backups remain part of the free plugin.

= How do Google Drive and SFTP extensions work? =

The free plugin creates and verifies the local backup first. An installed extension then transfers that package to the configured remote destination. Google Drive uses OAuth and resumable uploads. The current server connector uses SFTP over SSH with server-fingerprint verification; it is not unencrypted FTP or FTPS. See [all IDEI Move extensions](https://ideimove.com/plugins-wordpress/) and [compare plans](https://ideimove.com/precios/).

= Does the plugin work with cPanel, Plesk or CyberPanel? =

IDEI Move does not depend on a particular hosting control panel. It runs inside WordPress and needs the documented PHP, filesystem, database and private-storage capabilities. Control-panel upload limits, web-server configuration and account permissions can still affect a migration, so review Diagnostics on both sites before starting.

= What should I check after restoring WordPress? =

Sign in with a source administrator and check the home page, important URLs, media, forms, users, scheduled tasks and any ecommerce flow. Clear caches, save permalinks if rewrite rules need refreshing, confirm HTTPS and update DNS only after the destination works. Keep the original server and backup until the new site has operated correctly.

= Which database structures are supported? =

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.

= How do I change the language? =

Choose English, Spanish, French, German or Italian in Users > Profile > Language, or use the site default from Settings > General. Regional variants use the matching bundled language when no exact language pack is available. This changes the plugin interface, not your site's content.

= Where can I get help? =

Use the [WordPress.org support forum](https://wordpress.org/support/plugin/ideiweb-site-migrator-backup/). Include WordPress/PHP versions, the current job stage and the error text. Never post backups, passwords, recovery codes or private database content.

== Screenshots ==

1. IDEI Move dashboard with server diagnostics and official product identity.
2. Export components and a verified backup ready to download.
3. Import workflow with source and destination URLs before confirmation.
4. Multilingual interface and WordPress language settings.

== Changelog ==

= 2.2.1 =
* Clarify what the free WordPress.org plugin includes and separate it from optional licensed extensions.
* Document the available Google Drive and SFTP plugins, their shared site activation and direct purchase pages.
* Add direct IDEI Move extension links and bundled German and Italian interfaces alongside English, Spanish and French.
* Improve product wording and search context without changing the backup, archive, import or restore engine.

= 2.2.0 =
* Schedule daily local backups at selected WordPress-local times, optionally queueing a verified copy for an installed remote provider.
* Add bounded WP-Cron export progress and a short atomic checkpoint retry for transient Windows file sharing.
* Compatible with licensed IDEI Move Google Drive 1.1.0 and SFTP 1.1.0 add-ons.

= 2.1.1 =
* Keep the import validation and confirmation panel available when opening an SFTP download from Settings.
* Place extension settings before diagnostic cards so storage configuration stays easy to find.
* Verified together with the SFTP add-on across repeated transfer and UI regression tests.

= 2.1.0 =
* Add namespaced remote destination registration and compatible add-on hooks.
* Keep the local archive, import validation, restore confirmation and recovery unchanged.

= 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; German and Italian were added in 2.2.1.
* Preserved the published plugin identifier for upgrades and retained legacy backup files.
* Retired the previous ZIP/.wpress engine, scheduling and Wasabi integration.

== Upgrade Notice ==

= 2.2.1 =
This update improves the WordPress.org description and explains free features, paid connectors and direct purchase options. The migration and restore engine is unchanged.

= 2.2.0 =
Daily backup schedules are available in Settings. Remote Drive/SFTP destinations require separate add-ons. Finish in-progress jobs and retain your existing backups when upgrading.
