Last updated: October 25, 2026

Quick Answer: how do you migrate an auto blog from one WordPress site to another? In most cases, you move the content, copy the media, restore the automation settings, and test the schedules; WordPress can export/import content, but plugin rules and cron jobs usually need separate attention. If the setup is complex, consult a WordPress professional or the plugin developer before moving live. For background, see the WordPress.org importer documentation and the WordPress Codex on moving sites.

Migrating an auto blog from one WordPress site to another means moving the posts, media, plugin settings, schedules, and source mappings without breaking the automation. If the site still needs to publish on a timetable after the move, the real job is not just export and import; it is preserving the publishing system itself.

Key takeaways

  • Move the content first, but treat the automation settings as separate assets; if the plugin is complex, consult a professional or the plugin developer before you migrate.
  • Use a staging site and a full database backup before you touch the live site.
  • WordPress XML exports handle posts and pages, but they do not reliably carry plugin schedules or source mappings.
  • Media often needs a second pass, because image references can break even when the post content imports cleanly.
  • Plan 301 redirects before launch so old URLs still resolve after the domain or permalink structure changes.
  • This process is not for someone trying to rebuild the whole auto blog from scratch; it is for preserving an existing setup during a site migration.

What you need before you move anything

You need admin access to both WordPress sites, a current database backup, and a staging site on the destination host or domain. You also need a clear inventory of what the auto blog uses: the content source plugin, any cron-based scheduler, the media library size, the current permalink structure, and whether the source site has custom post types or taxonomies. Without that list, you can move 200 posts and still lose the automation that republishes them.

Start by checking the source site in the dashboard. Note the active plugins, the time zone under Settings > General, and any scheduled jobs tied to WordPress cron. If the blog pulls from RSS feeds, APIs, or scraped content, record the exact source mappings now. A simple spreadsheet with source name, destination category, tag, author, and schedule is enough.

Make a database backup before exporting anything. A database backup matters because the automation logic often lives in plugin tables, not in the post content itself. If the move goes wrong, you want a rollback point that is 1 click away in your host panel or a known restore file.

If the destination site already has sample content, decide now whether to replace it or merge into it. Conflicts happen when both sites use the same category slugs, the same author names, or the same media filenames. The cleaner the target is, the less cleanup you will do later.

For a broader workflow view, this migration sits inside an automated blog publishing workflow, but the job here is narrower: move the site without breaking the automation chain.

How do you migrate an auto blog from one WordPress site to another?

You migrate it by exporting the content, importing it on the new site, copying the media, then restoring the automation settings and redirects in the right order. That order matters because WordPress can import a post in under a minute, while fixing broken schedules after the fact can take much longer.

  1. Export the source site content from WordPress.
    Go to Tools > Export and choose the content you need, usually posts, pages, and media-related content if the exporter offers it. The result should be an XML file, often called a WordPress eXtended RSS export. When this works, you have a file that the destination site can read through Tools > Import. See the WordPress export documentation for the current tool behavior.

  2. Back up the destination database before importing.
    Export the destination database or make a host-level backup. This protects the new site if the import creates duplicates, wrong authors, or category collisions. When this step is done correctly, you have a restore point that can be rolled back in minutes, not hours.

  3. Install the WordPress importer on the destination site.
    Under Tools > Import, run the WordPress importer and upload the XML file. Assign posts to the right user account and check the box to download and import file attachments if available. A successful import usually ends with a completion message and a post count that matches the source export closely.

  4. Move the media library separately if attachments do not come across cleanly.
    If images are missing, copy the /wp-content/uploads/ folder by SFTP or file manager and then use a media sync plugin or search-and-replace tool if needed. The visible sign of success is that the featured images and inline images render inside the imported posts, not as broken file icons.

  5. Restore plugin settings, especially schedules and source mappings.
    Recreate the automation plugin settings from your notes or an exported settings file if the plugin supports one. Re-enter feed URLs, API keys, category rules, author assignments, and run intervals. This is the step that preserves the auto blog’s behavior after the move, not just its archive.

  6. Rebuild scheduled jobs and confirm WordPress cron is firing.
    Check whether the plugin uses WP-Cron, a real server cron job, or both. If the destination host needs a cron entry, add it before launch. When it works, scheduled posts move from “pending” to “published” on time, and the plugin queue clears as expected.

  7. Run a URL check and create 301 redirects.
    Compare old and new permalink structures, then map changed URLs to their new paths with 301 redirects. This keeps search engines and returning visitors from landing on dead ends. Success looks like the old URL forwarding to the matching new page in one hop.

What usually breaks during an auto blog move

The automation layer breaks more often than the posts do. Content import is usually straightforward; plugin state is not. The most common failure is a site that looks complete in the editor but stops publishing because the scheduling engine or source rules did not transfer.

One problem is serialized plugin data. Some WordPress plugins store settings in a format that does not survive casual copy-and-paste edits. If you change the site URL, category IDs, or feed endpoints by hand inside the database, you can corrupt those values. Use the plugin’s own export/import feature when it exists, or edit with a tool that understands serialized data.

Another problem is image paths. Imported posts may reference images from the old domain or old uploads directory. That creates missing thumbnails even when the article text imports correctly. The fix is either to import attachments, copy the uploads folder, or run a controlled search-and-replace for the old base URL.

A third problem is timezone drift. If the source site used UTC+0 and the destination uses a local time zone, scheduled jobs may fire at the wrong hour. The fix is simple but easy to miss: confirm Settings > General and the cron system before you test the first scheduled post.

Do not assume plugin activation is enough. Some auto blog plugins need a license key re-entered, a remote callback allowed, or a queue refreshed after migration. If the plugin dashboard shows “connected” but nothing publishes for 24 hours, inspect the cron log before blaming the import.

How to preserve source mappings and plugin rules

You preserve source mappings by exporting them separately, documenting them manually, or rebuilding them from the original configuration screen. The source map is the part that tells the site which feed becomes which category, which author, and which schedule slot.

If the plugin has an export file, use it. That is the cleanest option because it keeps the mapping logic in the format the plugin expects. If there is no export option, take screenshots of every rule page before the move: feed URL, keyword filters, category assignment, tag templates, featured image rule, and publish delay. A 5-minute screenshot set can save an hour of guesswork.

Pay attention to IDs, not just labels. WordPress categories and tags are often matched by internal IDs, while the screen may show only names. If “News” exists on both sites but maps to different category IDs, the import can place posts in the wrong archive. Recreate the categories on the destination first, then map by the right target IDs.

For scheduled jobs, identify whether the plugin uses WP-Cron or a server cron that calls wp-cron.php on a fixed interval. If it uses server cron, copy the schedule entry to the new host as part of the migration. If it uses WP-Cron, make sure the destination site is reachable and not blocked by maintenance mode or aggressive caching.

The hardest cases are plugin-dependent custom post types. If the auto blog stores items in a custom table, a plain XML export will not capture everything. In that case, the plugin’s own migration tool or a full database transfer may be the only complete path.

How to handle redirects, URLs, and SEO fallout

You handle redirects by mapping old URLs to new ones before the switch goes live. A migration without 301 redirects is a clean content move with a messy search result history.

Start by comparing the old permalink structure to the new one. If the source used /2024/03/post-name/ and the destination uses /post-name/, every post has a new URL. That is fine if you redirect them one by one or with a pattern-based rule in the web server or a redirect plugin. The point is to make the old address land on the new page with a 301 status, not a 302.

Check the media URLs too. If image hotlinks still point at the old domain, the page may load slowly or show mixed content problems when one site is HTTP and the other is HTTPS. Updating the base URL in the content and in the uploads path usually fixes this.

After launch, crawl a sample of old and new URLs and look for three things: the redirect status, the final destination, and the page title. If the redirect lands on the homepage instead of the matching post, the mapping is wrong even if the server returns a 301. That mistake hurts both users and search engines.

If the auto blog has thousands of posts, avoid hand-built redirects for every URL unless the URL pattern is irregular. Pattern rules are cleaner for large archives, but they must match the old structure exactly. A single bad rule can redirect a whole category to the wrong place.

What to check after the move

You check publishing, media, and queue behavior after the move, then leave the site in staging long enough to catch the next scheduled event. A 15-minute smoke test is not enough if the blog publishes every few hours.

Open several imported posts and confirm the title, content, featured image, author, category, and tags. Then open the plugin dashboard and watch for the next scheduled run. If the queue is empty but no new post appears, the cron system is likely the issue. If posts appear but source data is stale, the feed or API mapping is wrong.

Test one manual publish and one scheduled publish. The manual test confirms the editor and media library work. The scheduled test confirms cron, time zone, and plugin scheduling all agree. Both need to pass.

Also check the search console and analytics side if the site changed domains. A migration often creates a temporary dip in indexing while redirects settle. That is normal; broken redirects are not.

The move is finished when the destination site can publish on its own without depending on the old site. If the old site still has to stay online just to keep the automation alive, the migration is incomplete.

What to do when the migration is not worth forcing

Do not force a full migration if the auto blog depends on a plugin that cannot export its settings, a custom database schema you cannot recreate, or an old host that blocks cron jobs. In those cases, the content move may be easy while the automation is fragile.

A partial migration can be the better choice. Move the archive, rebuild the automation on the new site, and keep the old site frozen as a reference until the new pipeline proves stable. That is slower up front, but it avoids a broken publishing loop on launch day.

This is also the wrong project if the goal is to redesign the auto blog from scratch or to swap content sources at the same time. Those are separate jobs. One changes the site location; the other changes the system design. Mixing them turns a 1-day migration into a debugging week.

For the technical details on source acquisition and publishing setup, another page in the automated blog publishing workflow covers the upstream steps. This page stays focused on moving what already exists.

Can automated posts be moved to a new site?

Yes, the posts can be moved, but the automation may not move with them. The XML export usually carries the post content, dates, categories, and authors, while schedules, feed rules, and plugin-specific queues may need to be rebuilt. If the plugin stores settings in its own tables, export those too or recreate them manually.

How do you keep source mappings during migration?

You keep source mappings by exporting the plugin settings if that feature exists, then recreating the same categories, tags, and author rules on the new site. If there is no export option, save screenshots or a spreadsheet of each feed-to-destination rule before the move. IDs must match as well as names.

What needs to be reconfigured after moving wordpress?

You usually need to reconfigure cron jobs, plugin licenses or connections, permalink rules, redirects, media paths, and the site time zone. The XML import alone rarely preserves those pieces. After the move, confirm that scheduled posts fire, images load from the new media library, and old URLs forward with 301 redirects.

Drafted with AI; not yet reviewed by a person.