Add to Preferred Sources
WordPress export content to another site is a built-in feature that generates a WXR (WordPress eXtended RSS) XML file containing your posts, pages, comments, categories, tags, and user records — everything you need to import into any WordPress installation in a few clicks. If you are also weighing whether to stay on WordPress or switch platforms, the South African website builders guide covers the full comparison before you commit to a migration path.
What the built-in exporter will not move is everything else: your active theme, installed plugins, actual uploaded image files, and some page-builder layout data. Using the wrong tool for your scenario is the most common reason an import lands broken.
This guide maps your exact situation — content-only move, full-site migration, WooCommerce store transfer, or platform switch — to the correct tool, so you finish the move without spending a weekend undoing it. If you're also navigating a host change at the same time, read our companion post on moving your website to a new host without downtime alongside this one.
WordPress powers 40.2% of all websites globally and holds 58.7% of the CMS market according to W3Techs data compiled by Colorlib (October 2026), which means the majority of SA business websites will face this process at some point — a redesign, a host switch, a business rebrand, or a site consolidation.
Quick Answer
The standard wordpress export content to another site process uses two admin screens: go to Tools → Export on the source site, choose what to export, and download the WXR XML file. Then at the destination, go to Tools → Import → WordPress, install the importer plugin if prompted, upload the file, and tick "Download and import file attachments" to retrieve your media from the original server.
This moves posts, pages, comments, categories, tags, and users — not your theme, plugins, or the actual image files themselves (unless you tick that media option and the original site is still live). For full-site migrations or WooCommerce stores, use a dedicated migration plugin instead.
In This Guide
What the Built-in Export Actually Includes
Step-by-Step: Export and Import Process
Which Method Fits Your Scenario
Common Problems and How to Fix Them
Not sure which migration approach fits your site?
Send us your current setup details and we will map the right path — built-in export, migration plugin, or a full professional rebuild — in a free review.
Get a Free Migration ReviewWhat the Built-in WordPress Export Actually Includes
The WordPress built-in exporter produces a WXR file — a structured XML format that carries your site's content records, not its design or infrastructure. Understanding exactly what transfers (and what stays behind) prevents the most common post-import surprises.
| Included in the WXR export file | NOT included — stays on the source site |
|---|---|
| Posts (all statuses, filterable by author, category, date, status) | Active theme and all theme customisations |
| Pages (filterable by author, date, status) | Installed plugins and their settings |
| Custom post types (including most plugin-registered types) | Actual uploaded image and media files |
| Comments and comment metadata | Widget settings and Customiser options |
| Categories, tags, and custom taxonomies | User passwords (users transfer but must reset passwords) |
| Custom fields (post meta) | Navigation menu assignments (menus export but may need reassigning) |
| User records (names, email addresses, roles) | Database tables outside wp_posts and related tables |
| URLs/references to media attachments | Page-builder proprietary layout data (varies by version — see below) |
One practical note on page builders: Elementor's layout data (__elementor_data) exports and imports correctly on sites running Elementor v3.0 or later on both the source and destination. If either site runs an older version, the JSON layout data gets mangled with escape characters on import and your pages render as unstyled content. Always confirm both sites are on a current Elementor version before relying on the WXR exporter for Elementor-built pages.
Key takeaway
The built-in WordPress export is a content export, not a site backup. It moves your writing, structure, and user records cleanly. It does not create a working copy of your site — for that, use a dedicated migration plugin.
WordPress Export Content to Another Site: Step-by-Step Guide
Knowing how to export WordPress content to the right destination starts with the two-phase process: export from the source, then import at the destination. Both phases use built-in WordPress admin tools and require no FTP access or database editing. You can also export WordPress posts to another site selectively — filtering by date, category, author, or status — if you only need a subset of your content rather than everything at once.
Phase 1 — Export from the source site
- Log in to your source WordPress admin dashboard.
- Go to Tools → Export.
- Choose what to export:
- All content — exports everything in the table above in one file.
- Posts — lets you filter by category, author, date range, and status.
- Pages — lets you filter by author, date range, and status.
- Other content types your plugins have registered may appear as separate options.
- Click Download Export File. WordPress generates the WXR XML file and your browser downloads it automatically. On WordPress.com-hosted sites, exports above 1,000 posts are delivered as a .zip archive containing multiple XML files — import each one separately. On self-hosted WordPress.org installations, the export always produces a single XML file; if your WXR file is very large, use the date-range and category filters to break it into smaller exports.
Phase 2 — Import at the destination site
- Log in to the destination WordPress admin dashboard.
- Go to Tools → Import.
- Click WordPress in the list of importers. If the importer plugin is not yet installed, WordPress will prompt you to install and activate it before proceeding.
- Click Run Importer, then upload your WXR XML file.
- Assign authors: map the imported content to existing users on the destination site, or create new users.
- Tick "Download and import file attachments" if you want WordPress to fetch the actual image and media files from the original server's URLs. This only works if the source site is still live and accessible — if the source has been taken down, download the media folder manually via FTP before deleting the original.
- Click Submit. The importer runs through the file; on shared hosting this can take several minutes for large sites.
SA hosting note: shared hosting upload limits
Many South African shared hosting accounts (including entry-level plans on xneelo and Afrihost) set the PHP upload limit well below what a large WXR file requires. If the import form rejects your file with an upload size error, the fix is to contact your host and ask them to increase upload_max_filesize, post_max_size, and memory_limit in your PHP configuration. Alternatively, break the export into smaller chunks using the date and category filters on the export screen.
Which Export Method Fits Your Scenario
The built-in WordPress exporter is the right tool for content transfers, but it is the wrong tool for full-site migrations or WooCommerce store moves. The table below maps your scenario to the correct approach.
| Your scenario | Built-in exporter moves | What's missing | Recommended tool |
|---|---|---|---|
| Moving posts and pages to a new WordPress install (content refresh or domain rebrand) | Posts, pages, comments, categories, tags, users, media references | Theme, plugins, actual image files | Built-in WordPress exporter (Tools → Export) |
| Moving your complete site — theme, plugins, settings, database — to a new host | Content records only — theme and plugins still need reinstalling | Theme files, plugin files, all database config tables | Duplicator (free, no size cap) or All-in-One WP Migration (free up to 256 MB) |
| Moving a WooCommerce store (products, variations, orders, customers) | Basic product post types, but complex order relationships and payment records may not transfer cleanly | Order history, payment metadata, subscription records, stock rules | Dedicated WooCommerce plugin: WP All Export + WP All Import, or WebToffee Import Export Suite |
| Moving content to a different CMS (Wix, Squarespace, Webflow) | Not applicable — the WXR format is WordPress-specific | The destination platform needs its own import format | Platform's native importer (if available) or manual content transfer; keep WordPress until content is live on the new platform |
Key takeaway
When you need to wordpress export content to another site, match the tool to the job: the built-in WXR exporter for content-only moves, Duplicator (no size cap on the free tier) or All-in-One WP Migration (free up to 256 MB) for full-site moves, and a WooCommerce-specific plugin such as WP All Export for store migrations. The wrong tool choice costs more time to undo than the original migration would have taken to do correctly.
Common WordPress Export and Import Problems — and How to Fix Them
Most WordPress export and import failures come from a small set of predictable causes. Here are the ones SA operators encounter most often, with the fix for each.
Problem: Import file exceeds the maximum upload size
Cause: Your hosting PHP configuration's upload_max_filesize or post_max_size is lower than your WXR file. This is common on shared hosting plans where the default limit is as low as 4 MB on some configurations.
Fix: Contact your host and ask them to increase upload_max_filesize, post_max_size, and memory_limit in your PHP settings. Alternatively, break your export into smaller files using the date-range or category filters in Tools → Export.
Problem: Images are missing after import
Cause: You didn't tick "Download and import file attachments" during import, OR the original source site was already taken offline so the importer couldn't fetch the files from their URLs.
Fix: Re-run the import with the checkbox ticked (if the source is still live). If the source is offline, download your wp-content/uploads folder via FTP from the source host and upload it to the same path on the destination before reimporting.
Problem: Multiple XML files in a zip (WordPress.com-hosted sites)
Cause: On WordPress.com-hosted sites, exports above 1,000 posts are delivered as a .zip archive containing multiple XML files. This is a WordPress.com platform behaviour — self-hosted WordPress.org installations produce a single WXR file regardless of post count.
Fix (WordPress.com): Unzip the archive and import each XML file separately, in sequence, through Tools → Import on the destination site. Fix (self-hosted): If your single WXR file is very large, use the date-range and category filters at export time to break it into smaller batches.
Problem: Import times out or stops partway through
Cause: On South African shared hosting, long-running PHP processes can be killed by server timeout rules — a real risk when importing large content sets, particularly if there's load-shedding interrupting connectivity mid-process.
Fix: For time-sensitive migrations during load-shedding periods, use a local UPS for your machine and consider switching to a migration plugin with chunked upload support (Duplicator handles this by default). Alternatively, import in smaller batches using the export filters to control file size.
Managing a site migration and not sure where the risks are?
Tell us your current setup — host, WordPress version, site size — and we'll give you a clear migration timeline and risk assessment at no cost.
Request a Migration AssessmentWhy South African Businesses Choose Growth Pulse Media for Site Migrations
Growth Pulse Media handles end-to-end WordPress site migrations for South African businesses — covering tool selection, media retrieval, redirect mapping, and a live QA pass before DNS cut-over, all executed in-house by a senior specialist. The wrong-tool scenarios are predictable: a full WooCommerce migration attempted with the built-in content exporter, an Elementor site moved to an older-version install, or a media folder deleted before images were rescued. In each case the operator's time cost to undo and redo far exceeded what the original migration would have taken done correctly from the start.
Our web design service covers the full migration workflow — from advising whether to wordpress export content to another site using the built-in XML export import or a dedicated migration plugin, through media retrieval, redirect mapping, and a live QA pass before DNS cut-over. Everything is executed in-house; no junior freelancers are handed the sensitive database access.
We work with a limited number of clients at any one time, which means the person who assesses your migration is the same person who executes it. If you're also evaluating page builder options for the rebuilt site, our comparison of Elementor vs Divi for South African sites and Elementor vs Gutenberg will help you choose a build environment that won't complicate future migrations.
Who This Is NOT For
The built-in WordPress exporter is a content tool with clear limits; these four situations require a different approach before you begin.
Not for: Operators moving a full WooCommerce store with order history
The built-in WordPress exporter is a content tool. If your WooCommerce store has substantial order history, active subscriptions, or complex product variations, you need a dedicated import/export plugin and a database-level review before you go live on the new site. A content-only export will leave your order history behind.
Not for: Operators using the WXR file as a full-site backup
A WXR file is not a backup. It doesn't capture your theme, plugins, configuration, or media files. If your primary goal is disaster recovery, use a backup plugin (like UpdraftPlus or Jetpack Backup) that captures the complete site state — database plus files.
Not for: Moving content to a non-WordPress platform without a plan
Wix, Squarespace, and Webflow cannot directly import a WordPress WXR file. If you're switching platforms, the WXR gets you the text content in XML format — you still need to paste or import that content through the destination platform's own tools, or hire someone to handle the conversion. Don't export first and assume the receiving platform will handle the rest.
Not for: Sites where the original host is already offline
The importer's "Download and import file attachments" checkbox retrieves media files by fetching them from the original server's URLs. If the original hosting is already cancelled and offline, that mechanism fails silently — your posts import but images appear broken. Secure your wp-content/uploads folder before you pull the plug on the old host.
Ready to migrate but want expert hands on the process?
Send us your current site URL and we'll review your structure and flag anything that needs handling before the export runs.
Get a Free Site ReviewFrequently Asked Questions
Does WordPress export include media files like images and videos?
The WXR export file includes references (URLs) to your media files, not the actual files themselves. To retrieve the actual image and video files during import, tick "Download and import file attachments" on the import screen — this instructs WordPress to fetch each file over HTTP from the original server. This only works while the source site is still live and publicly accessible. If the source site is offline, you need to download the wp-content/uploads folder via FTP first.
What is a WXR file in WordPress?
WXR stands for WordPress eXtended RSS. It is the XML file format generated by Tools → Export in WordPress and accepted by the WordPress Importer plugin at Tools → Import on any WordPress installation. It contains your content records — posts, pages, comments, categories, tags, custom taxonomies, custom fields, and users — in a structured, portable format that can be read by WordPress and some other website platforms.
How do I fix "The uploaded file exceeds the upload_max_filesize" error during WordPress import?
This error means your hosting PHP configuration's upload file size limit is lower than the WXR file you're trying to import. Contact your hosting provider and ask them to increase the upload_max_filesize, post_max_size, and memory_limit PHP directives — on SA shared hosting the default can be as low as 4 MB.
As an alternative, use the date-range and category filters in Tools → Export to break the export into smaller batches, each within the existing upload limit.
Can I export WordPress content to Wix or Squarespace?
Not directly. The WXR format is WordPress-specific; Wix, Squarespace, and Webflow each have their own content management structures and do not accept a WXR file as a native import. If you are switching platforms, keep your WordPress site live during the transition, use the destination platform's own migration or import tool, and redirect your domain only after all content is confirmed live and correct on the new platform.
Does the WordPress built-in export work with Elementor pages?
Yes, on sites running Elementor v3.0 or later on both the source and destination. An older bug caused the layout data to be incorrectly escaped during the WordPress XML export import process, breaking page layouts on the new site — that was resolved in Elementor v3.0. Check your Elementor version in Plugins before running the export, and confirm the destination site is also on a current version.
Need Professional Help With Your WordPress Migration?
Growth Pulse Media handles end-to-end WordPress site migrations for South African businesses — from audit through export, redirect mapping, QA, and DNS cut-over. All work is executed in-house, with senior attention on every step. No obligation — we'll get back to you within 24 hours.
Request a Free Migration Review