---
title: "How to Copy Only New Posts from Staging to Production (Without Touching Orders and Users)"
url: "https://wpimportexport.com/how-to-copy-only-new-posts-from-staging-to-production/"
description: "Copy only new posts from WordPress staging to production. Orders, customers and users stay untouched. Two free methods, tested step by step."
type: post
published: 2026-11-03T07:03:45+00:00
modified: 2026-11-14T10:40:13+00:00
categories: ["Content Sync"]
tags: ["Abilities API", "AI Agents", "Content Sync", "Import Export by RockStarLab", "staging to production", "WordPress staging"]
docs_topics: ["Sync and migration"]
---

# How to Copy Only New Posts from Staging to Production (Without Touching Orders and Users)

A staging site rarely sits still while it is being worked on. On a shop, production keeps taking orders, customers register, and an editor may publish something urgent straight on the live site. When the new blog posts on staging are finally ready, copying the whole staging database back would wipe all of that out.

With [Import Export by RockStarLab](https://wordpress.org/plugins/import-export-by-rockstarlab/) you can move only the new posts from staging to production, and the check afterwards shows that orders, customers and user accounts on production stayed as they were. There are two free methods: a direct push with Content Sync, and an export file imported on production when the two sites cannot talk to each other. At the end, the same transfer is done through an AI agent.

## Short Answer

On staging, filter the Posts list by month, tick the new posts (not the drafts), click **Sync Content** → **Push to Site** and confirm the mapping with every row on **Create New Post**. If the sites cannot reach each other, export the posts with a date filter and import the file on production with **Check for Existing Items by Field: Slug** and **If Match Found: Skip**. Both methods only add posts; orders, customers and users stay as they were.

## What Moves and What Stays

Both methods work with posts, not with the database. What goes to production:

- the selected posts, with their status (published or scheduled), date and slug;
- categories and tags, created on production if they do not exist yet;
- the featured image and images used in the post text, with links rewritten to the production address.

What does not go to production: WooCommerce orders, customers, products, user accounts, settings, and posts that were not selected. No user account is created during the transfer, even when a post was written by someone who exists only on staging.

The test setup was a WooCommerce shop on production, cloned to staging. On staging, three posts were written: two published and one scheduled for later in the month, plus one draft that was not ready. One of the posts was written by Lena Hart, an author account. In the meantime, production received two new orders and a new customer account.

| Item | Production before | Production after | Staging |
| --- | --- | --- | --- |
| Published posts | 66 | 68 | 68 |
| Scheduled posts | 1 | 2 | 2 |
| Drafts | 1 | 1 | 2 |
| WooCommerce orders | 8 | 8 | 6 |
| Customers | 6 | 6 | 5 |
| User accounts | 10 | 10 | 9 |
| Media files | 95 | 97 | 97 |

Both methods produced the same “after” column. Note that staging had fewer orders and customers than production: copying the staging database back would have deleted two real orders and a customer account.

## What You Need

- Import Export by RockStarLab (Free) on both sites. The [installation guide](https://wpimportexport.com/how-to-install-import-export-by-rockstarlab-a-wordpress-import-export-plugin/) covers the first setup.
- For Method 1: a Content Sync connection from staging to production. Setting it up, including the two leftovers a cloned staging site brings along, is described in [How to Push WordPress Staging to Live Without Overwriting the Database](https://wpimportexport.com/how-to-push-wordpress-staging-to-live-without-overwriting-the-database/).
- For Method 2: nothing extra, only an administrator account on both sites.

Posts are part of the free version. Moving WooCommerce products, menus or custom post types needs the PRO addon.

The screenshots were taken with plugin version 2.1.1 on two local test sites. Hostnames are replaced in the images.

## Method 1: Push New Posts with Content Sync (Free)

### Find the new posts on staging

The Posts list already has the filter that helps here. Choose the month in the **All dates** dropdown and click **Filter**. The list then shows everything dated that month, drafts included, so tick only the posts that are ready.

![Staging Posts list filtered by November 2026 with three new posts ticked and a draft left unticked](https://wpimportexport.com/wp-content/uploads/2026/11/01-staging-posts-filtered-by-month.webp)

_Filter the Posts list by month and tick only the posts that are ready. The draft stays unticked._

The month filter goes by the post date, not by the last edit. An older post that was edited on staging during the same weeks does not appear here, which is exactly what is wanted when only new posts should go out. The test staging site had such an edit on an older post, and it stayed on staging.

### Push and check the mapping

Click **Sync Content** above the list, choose the production site and click **Push to Site**.

![Sync Content dialog with three selected posts and the Production site chosen, with Push to Site and Pull from Site buttons](https://wpimportexport.com/wp-content/uploads/2026/11/02-sync-content-push-to-production.webp)

_Choose the production site and click Push to Site._

The mapping dialog decides what happens on production for each post. Click **Auto-match by Title** and wait until the button shows its label again; with three posts it took about eight seconds. For new posts, every row should end on **Create New Post**.

![Map Posts for Sync dialog after Auto-match by Title with all three posts set to Create New Post](https://wpimportexport.com/wp-content/uploads/2026/11/03-map-posts-all-create-new.webp)

_After Auto-match by Title, new posts should all stay on Create New Post._

This dialog is the safety check. If a row shows **Update** with a production post instead, a post with the same title already exists on production and confirming would overwrite it. That happens, for example, when the same article was published on both sites by hand. Set such a row to **Create New Post** or remove the post from the selection.

**Confirm & Sync** sends the posts. The dialog reports how many were pushed.

![Sync Content dialog with the message Successfully pushed 3 post(s) to remote site](https://wpimportexport.com/wp-content/uploads/2026/11/04-push-completed.webp)

_The push reports how many posts were written to production._

### Check production

The three posts arrived on production with new IDs, their categories and tags, the featured images and the scheduled date of the third post. The image inside the text of the boots guide was copied to the production Media Library and its link now points to production.

![Production Posts list for November 2026 with the three pushed posts, one by Lena Hart and one scheduled](https://wpimportexport.com/wp-content/uploads/2026/11/05-production-new-posts-with-authors.webp)

_On production, the posts arrived with their authors, categories, tags and the scheduled date._

The IDs are worth a remark. On staging, the running shoes post had ID 1907; on production, 1907 belonged to one of the new orders. The push does not try to keep IDs, so there was no conflict: the post simply received the next free ID on production.

The orders list on production still shows all eight orders, including the two placed while staging was being edited.

![WooCommerce Orders list on production with eight orders, including two processing orders placed during the staging cycle](https://wpimportexport.com/wp-content/uploads/2026/11/06-production-orders-untouched.webp)

_All eight orders are still on production, including the two placed while staging was being edited._

The user list has the same ten accounts as before the push. Lena Hart’s post count went from 0 to 1, because her post found her account on production.

![Production Users list with ten accounts and Lena Hart showing one post](https://wpimportexport.com/wp-content/uploads/2026/11/07-production-users-unchanged.webp)

_No accounts were added or changed. Lena Hart's post found her production account by email._

On the front end, the post shows the right author, date, category and featured image.

![Front end of the pushed post with author Lena Hart, date, category Guides and the featured image](https://wpimportexport.com/wp-content/uploads/2026/11/08-production-post-front-end.webp)

_The pushed post on the production front end with its author and featured image._

### How authors are matched

User IDs are different on every site: Lena Hart was user 9 on staging and user 10 on production, and on production ID 9 belonged to a customer. Content Sync therefore does not rely on the ID. It sends the author’s email address and username with each post and looks for the same account on production (plugin version 2.1.1 and later).

- An account with the same email (or, failing that, the same username) that can write posts becomes the author.
- If there is no such account, a new post is assigned to the production administrator the connection runs as. No account is created.
- Accounts that cannot write posts, such as customers and subscribers, are never used as authors.
- When a push updates an existing post and no matching author is found, the post keeps its current author on production.

So if guest authors write on staging, creating their accounts on production before the push keeps the bylines right. Otherwise the author can be changed afterwards with **Quick Edit**.

## Method 2: Export the New Posts and Import Them (Free)

Content Sync needs staging to reach production over the network. When staging runs behind HTTP authentication, on a private network or on a laptop, an export file does the same job. One limitation applies: images are downloaded from the addresses in the file during the import, so production has to be able to open the staging URLs at that moment. If it cannot, the posts arrive without their images.

### Export with a date filter

On staging, open **Import Export by RockStarLab → Export**, choose **Blog Posts** and add two filters: **Date** → **Greater or Equal** with the first day the new posts were written, and **Status** → **Not Equals** → `draft`. The counter at the top updates a moment after each change.

![Export Filter Data step with Date Greater or Equal 01/11/2026 and Status Not Equals draft, showing 4 items](https://wpimportexport.com/wp-content/uploads/2026/11/09-export-filter-new-posts-only.webp)

_Two filters select posts dated from November 1 that are not drafts._

The filter returned four posts, not three. The fourth was an old test post called “Scheduled”, dated 2030 and already present on production. Any scheduled post with a date in the future passes a “date from” filter, which is why the import below checks for existing posts. The [export filter examples](https://wpimportexport.com/wordpress-export-data-filters-examples-how-to-use-them-effectively/) show more combinations.

In **Fields**, **Add all** keeps everything the import needs, including the author email, featured image URL, categories and tags. JSON or CSV both work; the test used JSON. The export of four posts with 28 columns took three seconds and produced a 6.2 KB file.

![Export Complete screen with 4 items exported, file size 6.2 KB and duration 3 seconds](https://wpimportexport.com/wp-content/uploads/2026/11/10-export-complete-three-posts.webp)

_The export file is ready to download._

### Import on production, skipping what already exists

On production, open **Import Export by RockStarLab → Import**, choose **Blog Posts**, confirm the backup reminder, upload the file and click **Auto Map** on the mapping step. All 28 columns were matched. The important settings are on the options step:

- **Check for Existing Items by Field**: **Slug**.
- **If Match Found**: **Skip**. The default is **Update**, which would overwrite any production post with the same slug. In this test it would have replaced the existing “Scheduled” post with the staging copy.
- **If No Match Found**: **Create**.
- **Automatically Import Media Files**: on, so featured images and images in the text are downloaded.
- **Replace links**: from the staging address to the production address.

![Import Options step with Check for Existing Items by Field set to Slug, If Match Found set to Skip and If No Match Found set to Create](https://wpimportexport.com/wp-content/uploads/2026/11/11-import-options-skip-existing-slugs.webp)

_Check by slug and switch If Match Found from the default Update to Skip._

The import created three posts and skipped one in six seconds. Authors were matched by the email address in the file, so the running shoes post again landed under Lena Hart. More detail on the matching options is in [updating posts without creating duplicates](https://wpimportexport.com/how-to-bulk-update-existing-wordpress-posts-without-creating-duplicates/).

![Import result with 3 created, 1 skipped, 0 failed and a duration of 6 seconds](https://wpimportexport.com/wp-content/uploads/2026/11/12-import-result-created-and-skipped.webp)

_The import created the three new posts and skipped the one that already existed._

Running the same import a second time is harmless with these settings: it reported 0 created and 4 skipped. That makes the method safe to repeat when it is not clear whether a file was already imported.

## Which Method to Use

|  | Content Sync (Free) | Export and import (Free) |
| --- | --- | --- |
| Sites must reach each other | Staging must reach production | Production must reach staging for images only |
| Selecting posts | Tick them in the Posts list | Export filters (date, status, category, author and more) |
| Protection against duplicates | Mapping dialog before the push | Slug check with **If Match Found: Skip** |
| Record of the transfer | Jobs Log | Jobs Log and the export file |

For a handful of posts on two connected sites, Content Sync is quicker. For many posts, a specific date range or sites that cannot see each other, the file is the more practical route.

## Copy New Posts With an AI Agent

All steps above are also available as WordPress Abilities. With the Abilities API (WordPress 6.9 and later) and the MCP Adapter plugin, an AI agent such as Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI can do the transfer from a prompt. The setup is described in the [Abilities API guide](https://wpimportexport.com/how-to-use-the-wordpress-abilities-api-with-ai-agents-exports-imports-content-sync-and-backups/): enable **Enable Abilities API** under **Plugin Options → AI Agent Connection** on staging, install the MCP Adapter and connect the agent to staging. The Content Sync connection to production from Method 1 is reused, so the agent needs no access to production of its own.

The prompts below were run by an AI agent (Claude, connected to the staging site through the MCP Adapter) on the same test sites, starting from the same state as the screenshots. The agent chose `rsl-ie/export-preview`, `rsl-ie/sync-auto-map` and `rsl-ie/sync-push` by itself.

**1. List the new posts**

```
On this staging site, list the blog posts dated November 1, 2026 or later that are
published or scheduled. Leave out drafts. Show ID, title, status, date and author.
```

The agent used the same filters as the export screen and returned the same four posts, the old “Scheduled” post included.

**2. Check production without writing anything**

```
Check which of these posts already exist on the "Production" site, matching by title.
Do not change anything on either site.
```

Result: the three new posts had no match, and “Scheduled” matched the existing production post with the same ID.

**3. Push only the missing posts**

```
Push only the posts that do not exist on "Production" yet, as new posts.
Do not update any existing production post. Report how many were created and their production IDs.
```

The agent pushed three posts with the mapping set to “create new” for each, and reported 3 created, 0 updated, 2 images transferred, with the new production IDs. Production ended with the same counts as in the table above, and the existing “Scheduled” post kept its original date and author.

One limit showed up: from staging, the agent can list production posts by title, status and date, but not by author. Checking the bylines after the push is a job for the production Posts list. The step that writes, `rsl-ie/sync-push`, is marked as destructive in the Abilities API, which is the signal MCP clients use to ask for confirmation before running it.

## Common Problems and Fixes

### A row in the mapping dialog says Update instead of Create New Post

A production post has the same title. Unless that post really is the same article, switch the row to **Create New Post**. Otherwise the push replaces the production text with the staging one.

### The date filter also catches scheduled or old posts

A “date from” filter includes every scheduled post with a future date, even if it was created years ago. Add **Status** filters or check the list before pushing. In the import, **If Match Found: Skip** keeps such posts from being overwritten.

### A post shows the administrator as author on production

The author’s account does not exist on production, or it has a role that cannot write posts. Create the account (with the same email address) before the next transfer, or change the author with Quick Edit.

### Imported posts have no images

Production could not download them from staging. Check that the staging URLs open from production, and that **Automatically Import Media Files** was switched on. Content Sync sends the files directly, so it is the better choice when staging is not public.

### “This connection is already in use. Try again later.”

Another sync over the same connection is still running. Wait for it to finish in the [Jobs Log](https://wpimportexport.com/how-to-use-jobs-log-and-schedule-wp-import-and-export-jobs/) and push again.

## FAQ

### Will this delete WooCommerce orders that arrived after the staging copy?

No. Neither method touches orders. In the test, two orders placed on production during the staging cycle were still there afterwards, with the same IDs and statuses.

### Are users or customers copied from staging?

No. Posts are linked to existing production accounts by email address, but no account is created, changed or deleted. Copying user accounts on purpose is a separate PRO feature, described in [syncing users between sites](https://wpimportexport.com/how-to-sync-wordpress-users-between-sites/).

### Do scheduled posts stay scheduled?

Yes. The scheduled post arrived on production with status Scheduled and the same publication date and time.

### Can pages be copied the same way?

Yes. The Pages list has the same **Sync Content** button, and the export and import screens offer **Pages** as a content type.

### Is a backup of production needed?

Adding posts is low risk, but a backup before the first transfer costs little. The [backup and restore guide](https://wpimportexport.com/how-to-create-a-wordpress-website-backup-and-restore-it/) shows how to make one with the same plugin.

## Related Guides

- [WooCommerce Staging to Live Without Losing Orders](https://wpimportexport.com/woocommerce-staging-to-live-without-losing-orders/)
- [How to push WordPress staging to live without overwriting the database](https://wpimportexport.com/how-to-push-wordpress-staging-to-live-without-overwriting-the-database/)
- [How to sync WordPress posts and pages between multiple sites](https://wpimportexport.com/how-to-sync-wordpress-posts-and-pages-between-multiple-sites-without-import-and-export/)
- [How to import WordPress blog posts from CSV or Excel](https://wpimportexport.com/import-wordpress-blog-posts-from-csv-excel/)
- [How to migrate WooCommerce store data to another site](https://wpimportexport.com/how-to-migrate-woocommerce-store-data-to-another-site/)
- [How to use the WordPress Abilities API with AI agents](https://wpimportexport.com/how-to-use-the-wordpress-abilities-api-with-ai-agents-exports-imports-content-sync-and-backups/)

Import Export by RockStarLab is free on [WordPress.org](https://wordpress.org/plugins/import-export-by-rockstarlab/).
