steviemathew

SM Easy Post Migrator helps you move your WordPress content from one site to another. Use it to migrate posts, pages, images, and other media files between WordPress sites without losing your content or breaking links.
What You Can Do:
<ul>
<li>
Migrate Posts and Pages: Copy your blog posts, pages, and content from your old site to your new site. All your text, formatting, and content structure is preserved.
</li>
<li>
Move Images and Media: Automatically download and import all images, videos, and media files from your source site. The plugin checks for duplicates so you don’t end up with multiple copies of the same file.
</li>
<li>
Fix Internal Links: When you move content, all the links between your posts and pages are automatically updated to work on your new site. No broken links!
</li>
<li>
Choose What to Migrate: Browse your source site and pick exactly which posts, pages, or media files you want to move. You’re in control.
</li>
<li>
Track Your Progress: See detailed logs of what was migrated, what succeeded, and what had issues. Export these logs to CSV if you need to review them later.
</li>
<li>
Easy to Use: Connect to your source site using your WordPress username and application password, then select what you want to migrate. The plugin handles the rest.
</li>
</ul>
Perfect for moving your blog to a new domain, consolidating multiple sites, or backing up your content to a new location.
<h3>License</h3>
This plugin is licensed under the GPL v2 or later.
<h3>Support</h3>
For support, feature requests, or bug reports, visit <a href="https://wordpress.org/support/plugin/sm-easy-post-migrator/" rel="ugc">https://wordpress.org/support/plugin/sm-easy-post-migrator/</a>
<h3>Contributors & Developers</h3>
“SM Easy Post Migrator” is open source software. The following people have contributed to this plugin.

SM Easy Post Migrator

Migrate posts, pages, media, and internal links between WordPress sites without breaking links or losing images.

sprise

Migrate posts across WordPress installs. Optionally, limit your import to certain categories of your site.
Your posts will be imported along with:
<ul>
<li>Images (added to your Media Library and src tags will be corrected)</li>
<li>Authors</li>
<li>Tags</li>
<li>Categories</li>
<li>
Comments
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>

SPR Posts Import

Move your blog posts to a new site with one click.

SM Easy Post Migrator vs SPR Posts Import