Want to move a few posts, pages or categories to another site without moving the theme, plugins or all the settings? WordPress’s built‑in tool does exactly that. It creates an XML content file, also known as a WXR file, which you can import into another WordPress installation.
This method is suitable for reusing a blog section, consolidating editorial pages or starting a new site with a selection of existing content. However, it does not replace a full migration. If you also need to move files, the database, the theme and settings, see instead the method for migrating a complete WordPress site.
What the WordPress export actually transfers
In the source site’s admin, open Tools > Export. WordPress lets you export all content, or limit the file to posts or pages. The WXR file can include posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies and users associated with the content. The official documentation for Tools > Export describes the included items and available filters.
For posts, you can filter by category, author, date range and status. So you can export only the items from a section, the posts by a particular person or those published during a specific period. For pages, WordPress offers filters by author, date range and status.
However, the transfer does not recreate the full configuration of the target site. The active theme, plugins, their options, general settings, widgets and the technical infrastructure are not part of a targeted export. Thus, blocks or fields created by a plugin may appear incomplete if that plugin is not also present on the destination site.
Preparing a partial transfer
Define the scope before downloading
Start with a simple list: which content should go to the new site, and which should remain on the source site? Also note related items, including featured images, documents, authors, comments and categories.
Next, check your editorial structure. A category imported into an already organized site can create an unnecessary archive or a duplicate taxonomy. Before transferring, review organizing WordPress categories and tags to harmonize names, slugs and intended usage.
Protect the target site and test first
Even if you only import content, the operation adds posts, terms and sometimes files to the target site. So make a recoverable backup before you start. A test environment is also useful when the target site already contains public content.
On a staging site, you can spot duplicates, missing images and blocks that depend on a missing plugin. This avoids fixing those issues directly on the site your readers visit.
Export only the posts or pages you need
- Log in to the source site with an account that can access the admin tools.
- Open Tools > Export.
- Choose Posts or Pages, rather than All content.
- Apply the necessary filters. For posts, select a category, an author, a date range and a status as needed.
- Double-check the selected scope.
- Click the download button to save the XML file to your computer.
Keep this file in a private, easy-to-recognize location. It contains editorial data but isn’t a full copy of the site. Also avoid editing it by hand unless you understand its format, and keep an intact copy.
Import the file into the target site
On the destination site, go to Tools > Import. Install the importer if WordPress prompts you, then run it. Next, upload the WXR file from the source site.
During the process, WordPress will ask how to assign the file’s authors. You can map them to existing accounts or create users. Choose an assignment that fits your editorial organization, especially if multiple people publish on the target site.
The importer also offers the option «Download and import file attachments». Enable it if you want to retrieve attachments that are accessible from the source site. The official content import guide explains author assignment, attachment import and precautions to take for large files.
Check media after import
Media needs special attention. Importing attachments depends on their availability on the source site during the process. Do not delete old files, shut down the source site or block its access before you’ve completed your checks.
After import, open a few representative posts. Check featured images, inline images, documents and links to files. Also check the target site’s media library. A content export is not a full synchronization of all files.
Key checks after transfer
- Compare the number of posts or pages imported with your original selection.
- Open content that contains images, galleries or documents.
- Check the author, date, status and category of several posts.
- Spot any links that still point to the source domain.
- Confirm the display of blocks and custom fields.
- Delete drafts, duplicates or categories added by mistake before publishing.
If the file is very large, the import may fail when the server runs out of resources. In that case, ask your host to adjust the settings or split the file into smaller batches. A stopped import may already have created some content. Check the results before retrying to avoid duplicates.
When to choose another tool
The native exporter is a good first choice for moving a selection of standard posts or pages. It’s built-in, lightweight, and doesn’t require a plugin for a one-off operation.
Choose a specialized tool instead if you need to map CSV columns, import a large volume of records, update existing content according to a rule, or move complex data created by a plugin. Always test compatibility with your content types and fields before working on the live site.
Finally, don’t confuse importing with duplicating. To create a variant of a single piece of content on the same site, duplicate a WordPress post will usually be faster. To transfer a selection to another site, the WXR file and the WordPress importer provide a more suitable method.









