<p>Tutorial on how to use the ezMigrate plugin: <a href="http://techblog.triptic.nl/moving-wordpress-using-the-ezmigrate-plugin/" rel="nofollow ugc">Moving wordpress using the ezmigrate plugin</a></p>
<p>This plugin makes it easy to use and migrate your blog across different locations by detecting the current location and<br />
replacing all absolute paths on the fly.<br />
While there are ways to move your blog around by replacing the locations within the database manually or through scripts,<br />
they are very error prone and not very easy to do.<br />
Once enabled, this plugin doesn’t require you to do anything other than move your code and database to a new location<br />
when you want to. You can even access your blog through multiple urls at the same time when you need to.</p>
<p>This plugin is useful when:</p>
<ul>
<li>You want to make your blog available through different urls</li>
<li>You want to move your blog around</li>
<li>You’re staging the development of a blog with development, test and production environments which all have their own urls.</li>
<li>You’re using a Version Control System on a development server and developers have their own checkouts and urls to access a blog using a single database.</li>
</ul>
<p>The ezMigrate plugin does the following things:</p>
<ul>
<li>It determines the root url of the blog.</li>
<li>It replaces the options “siteurl”, “home”, “upload_path” and “fileupload_url” to the correct values, independent of their values stored inside the database.</li>
<li>When not already set in wp-config.php it sets the constants WP_CONTENT_URL, COOKIEPATH and SITECOOKIEPATH to the correct values.</li>
<li>When a post is saved into the database it replaces all root urls in href and src attributes with a placeholder. (This is also done for all posts when the plugin is activated).</li>
<li>When a post is retrieved from the database it replaces all placeholders with the current calculated root url. (This is also done for all posts when the plugin is deactivated).</li>
</ul>
<p>This way you don’t need to do anything when you migrate your blog and you can even make your blog accessible through multiple urls. It made life for me and the other developers at triptic a lot easier when we need to develop blogs using wordpress.</p>
<p>What this plugin doesn’t do (but might do in the future):</p>
<ul>
<li>Put a  in the header of your template. You can easily do this yourself by placing <base href=”<?php echo ezMigrate_getFullUrl();?>/” /> right after the <head> tag in the header.php file of your theme.</li>
<li>Replace urls outside of the four mentioned options or outside of href and src attributes in posts.</li>
<li>Make changes that might be necessary in the .htaccess file.</li>
</ul>
<p>Known plugins that won’t work on multiple locations without modification:</p>
<ul>
<li>cforms II, http://www.deliciousdays.com/cforms-plugin<br />
won’t work because of absolute paths in abspath.php and js/cforms.js</li>
</ul>


ezMigrate

Enables you to move your blog across locations, or even make it available through multiple…

migrate

nick843

<p><strong>Try it out on your free dummy site: Click here => <a href="https://tastewp.com/plugins/wp-clone-by-wp-academy" rel="nofollow ugc">https://tastewp.com/plugins/wp-clone-by-wp-academy</a>.</strong><br />
(this trick works for all plugins in the WP repo – just replace “wordpress” with “tastewp” in the URL)</p>
<p>WP Clone is a great way to backup, migrate or clone a WordPress site to another domain or hosting server.</p>
<p>You can also use it to backup, migrate or clone your site to/from local server hosting, to create backup of your site for development or testing purposes, and to install pre-configured backups of WordPress.</p>
<p>WP Clone is a superior to other backup & migrate plugins for the following reasons:</p>
<ul>
<li>It does not require FTP access to backup files you migrate or clone, neither the source or destination site; just install a new WordPress on the destination site, install our backup plugin, and follow the prompts to migrate or clone your site.</li>
<li>It does not backup or restore the WordPress system files (it just creates user content and database backups); reducing upload time for migration and improving security of your site</li>
<li>It fetches the site backup via your host’s direct http connection, which saves you from having to upload large backup files, making it easier to migrate.</li>
</ul>
<h4>What are today’s limitations?</h4>
<p>Today:</p>
<ul>
<li>90% of cases: Backups & migrations work flawlessly (we fixed some key bugs in the most recent version)</li>
<li>9% of cases: Backups or migrations fail due to your hoster’s configurations (most likely limits in up- and downloads) which is typically the case when you backup or migrate very large sites. However, there’s a workaround: simply do a “Database Only” backup (use “Advanced Settings”), transfer the wp-content directory over with FTP, and then restore new site. Then backup and migration also works.</li>
<li>1% of cases: Your site/hosting is abnormal (pardon our French) and backup or migration doesn’t work. However: that’s what we’ll now be working on, so that eventually backups and migrations will work in all cases.</li>
</ul>
<p>The 1% case means:</p>
<ul>
<li>Basic rule: DO NOT use it as your only backup solution! Only use it for migrations (so that if something fails, you still have the files on your old site as backup).</li>
<li>If you want to use it as backup, test it by restoring the backup file on a new site. If that works fine you should be safe.</li>
<li>In any case, we cannot take any responsibility if backup or migration fails.</li>
</ul>
<p>Note:<br />
* There is never an issue in damaging the source installation (i.e. on the site where you create the backup). So backup sites at your pleasure. If your backup succeeds then chances are good that the migration (i.e. restore on another site) will also succeed. But don’t take any chances.<br />
* If backup or migration (restore) fails, just try it again. Often it works on second attempt.</p>
<h4>Other tips how to backup and migrate</h4>
<ul>
<li>NEVER overwrite an installation for which you do not have an alternate backup source (e.g. a cPanel backup). Normally you would restore the backup onto a fresh WP installation on another host or on a subdomain. If the restore fails your destination site might become unusable, so be prepared to enter cPanel and then destroy / recreate the new installation if necessary.</li>
<li>DO NOT use our backup plugin on WP Engine or any hosting system with proprietary operating system. Instead, use their built-in backup tools.</li>
<li>Large sites (>2GB) might take as long as an hour to backup and migrate. Sites of 250 MB or less should take no more than a minute or two to backup, depending on your server.</li>
<li>We recommend you deactivate and delete page caching, security and maybe redirection plugins before you migrate, and re-install them on the new site, if necessary. In general, delete all unnecessary plugins and data from your site before you backup. You can also use the “Exclude directories” option if you have large media files, which you can then copy back to the new site with FTP.</li>
<li>How to copy from local server to your hosted website: Create a backup of the local site in the usual way, then save the backup file (right-click > Save) to your local disk. Upload this file to the root directory of your destination website and then use this url in the “Restore” dialog of the new site: http://yourdomain.com/.</li>
</ul>
<h4>Help Video</h4>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/xN5Ffhyn4Ao?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h4>Credits</h4>
<p>WP Clone uses functions from the “Safe Search and Replace on Database with Serialized Data” script first written by David Coveney of Interconnect IT Ltd (UK) http://www.davidcoveney.com or http://www.interconnectit.com and released under the WTFPL http://sam.zoy.org/wtfpl/. Partial script with full changelog is placed inside ‘lib/files’ directory.</p>
<p>This plugin is part of the Inisev product family – <a href="https://inisev.com" rel="nofollow ugc">check out our other products</a>.</p>


ezMigrate vs Clone