Your new website is taking shape, but years of articles still live in the old one. Downloading an export feels like the handoff is finished. The receiving team still needs to know what belongs in that file and what must travel separately.
Agree on the content, test its arrival and keep the original available until the move is checked. For a Scottsdale business using WordPress, this turns a file download into a useful publishing handoff.
This guide covers moving editorial content into another WordPress site. A complete hosting move, store migration or recovery job needs its own scope. Our backup guide covers the separate question of restoring a working website.
Decide what should move
Imagine a Scottsdale design studio moving its articles and project notes into a rebuilt website. It wants current advice and approved project stories, while older drafts need an editorial decision.
Make a short inventory with the person who owns the writing. Include the source address, title, current status and intended destination. Mark material that needs updating before it becomes public again.
Do not delete content just to make the move easier. Keep an agreed record of anything left behind and why. An old article may still answer a customer question or receive visits through a saved link.
WordPress’s Tools → Export screen creates an XML file, also called WXR. It supports content such as posts, pages, comments, categories and tags. The Posts option offers filters including category, author, date range and status. Read the export options.
Choose those settings against your inventory. A published-only selection will not express a plan to move unfinished drafts too. Record the actual choices with the downloaded file so the receiving person can check them.
- Bring across
- Approved articles, pages and their intended status.
- Resolve first
- Outdated details, uncertain credit and unfinished drafts.
- Record separately
- Design, media transfer and connected features.
Plan the parts outside the export
Treat the content file as one part of the handoff. WordPress.com explains that its export contains media references, not the actual image files, and excludes themes, design customizations and plugins. Check what its export includes.
For the imagined studio, the project story and its photographs need separate attention from the layout that presents them. Ask the receiving developer which pieces the destination can use directly and which need rebuilding.
Have them review custom blocks, forms, downloads and other special content before the main import. Choose a representative page containing those features. A plain paragraph arriving successfully does not establish that a more complex project page will work.
Keep a separate full recovery copy before substantial changes. The export checklist should name the person handling that copy without describing the XML file as a complete backup.
Agree how changes made during the move will be tracked. If an editor corrects a telephone number after the export, the receiving team needs that correction too. Give the final content handoff a clear time and owner.
Keep the original media reachable
Do not cancel the old hosting simply because the export downloaded. WordPress.com’s documented transfer uses the original media addresses to copy files into the destination. Those files must remain accessible during that process. Read its media-transfer guidance.
Ask the developer to confirm the access method for your setup. If the source contains private material, agree on an appropriate transfer method instead of exposing it to make an importer work.
For each representative article, check the main image, an image within the text and any linked download. Open them from the destination and confirm where the files are served from. A picture still loading from the old website can hide an unfinished move.
Our media-library guide helps identify files and their uses. Keep that record beside the content inventory so the team can trace a missing image to its source.

Test the import before repeating it
Have the receiving developer use a controlled test site first. Agree who can access it and prevent it from sending unintended customer messages or accepting live transactions.
Use the destination’s WordPress importer with the exported file. Its workflow includes assigning imported content to authors and an option to download file attachments. Review those choices with the developer rather than accepting them without checking. See WordPress’s import instructions.
Keep credit truthful. If an article was written by a particular team member, mapping it to the site administrator merely for convenience can change what readers understand. Our article-author guide covers that editorial decision.
If an import stops, save the error and inspect what arrived before trying again. WordPress warns that a failed import may still create content, and a retry can produce duplicates. Read its preparation guidance.
Ask the developer to reconcile the partial result with the inventory. Do not judge success solely by a completed progress message or a matching total. The right pages, statuses and relationships need to be present.
Title · author · status
Images · links · purpose
Open the page.
Follow its next step.
Keep each discrepancy with its page address and owner.
Review the pages before retiring the source
Open the imported content in the destination’s actual design. On a phone and a larger screen, read the headings, image captions and links. Check both a simple article and the more complex page selected earlier.
For the imagined studio, follow a project story to its enquiry route. Confirm that old workshop references still make sense and that draft material has not become an unintended public page.
Compare selected entries with the source inventory: title, date, author, category and intended publication status. Record missing media and formatting problems with a specific page address and a named owner.
Then review old addresses separately. Importing content is not a substitute for an agreed redirect plan. Our URL-change guide explains how to preserve useful routes into the rebuilt site.
Retire the source only after the content owner and developer have agreed that the transfer, remaining dependencies and address plan are complete. Keep the export, inventory and review notes in the handover, with any outstanding work clearly assigned.
Your Scottsdale business website should carry useful content forward without leaving its photographs or customer routes behind. Our content management service can help plan that move. Talk to Brandon about transferring your website content.
