Read Website Export Files: WXR, Code ZIP and CMS CSV

By Dave TanguayPublished Updated Editorial draft

Quick Answer

Read an export by tracing one item through its files. A WordPress WXR record can identify content and an attachment URL, a code ZIP can contain page assets, and a CMS CSV can contain field values and relationship references. Those artifacts are not interchangeable, and a reference to something does not prove the thing itself is included.

The exercise below uses an invented article, image and category. It explains how to interpret an export package, rather than providing an export to download or claiming a completed transfer.

Define one item to trace

Imagine an article called Service Planning with an image at https://example.com/media/service.jpg and a relationship to a category called Planning. The inspection question is where each piece is represented, not whether the filenames look familiar.

Illustrative artifact What the evidence means
WXR item and attachment record An item identifier, attachment parent and attachment URL describe records and a source location. The URL is not the image’s binary file.
Code ZIP with an image file The package contains that asset. Inspect the actual page reference and distinguish static presentation from any hosted content service.
CMS CSV with a category reference A value identifies a related item under the platform’s mapping rules. It does not prove that the receiving system has resolved the relationship.

Read the WXR record and media reference

WordPress’s export function documentation shows fields such as wp:post_id, wp:post_parent and wp:attachment_url. In the relevant source, an attachment URL is emitted for an attachment record.

For an illustrative article identifier of 42, inspect which attachment record names that parent and which source URL it supplies. Keep those original identifiers in the reading notes. They are not an assurance that a destination will retain the same IDs.

The WordPress export and import lesson treats downloading and importing attachments as a separate import step. A URL in XML therefore needs different evidence from an image file present in a retained package. The lesson also distinguishes content transfer from transferring themes, plugins and site design.

Read the code package as a different artifact

Webflow’s code-export guide describes HTML, CSS, JavaScript and assets. It excludes CMS content and functionality, and says exported Collection lists and bound Collection-page content will be empty. Hosted forms, search and password protection also do not continue as working exported features.

For the invented example, locate the actual image file and inspect the page’s reference to it. A matching image does not establish that an editable article record or its category relationship is present. Keep the package’s observed contents separate from the original site’s behavior.

Interpret CMS fields and relationships

Webflow’s CMS transfer guidance separates Collection CSV data from code export. Its field rules describe image URLs and reference values; custom slugs can matter when matching referenced items.

Read the header, the article’s row and the referenced category’s identity together. Record whether the image cell contains a URL and whether the corresponding file was obtained separately. Keep a custom category slug distinct from a display label instead of silently treating both as the same key.

Write an artifact-level conclusion

A useful finding names the inspected record, field or file, then states what remains unresolved. For example: the article row contains a category slug, while its destination mapping has not been checked. Avoid upgrading that observation to a successful import.

No export or import was run for this guide. Our portfolio portability guide covers the broader inventory and destination proof. The editing exercise concerns maintenance, and the migration checklist covers operational transfers.

Key Takeaways

  • Trace one item through actual records and files.
  • Distinguish media references from retained assets.
  • Read relationship keys under the applicable mapping rules.
  • Keep an observed artifact separate from a successful transfer.

Frequently Asked Questions

Does an image URL mean the export contains the image?

No. Inspect whether the file is actually present or must be retrieved separately through an authorized process.

Does a category label prove the relationship will import?

No. The destination may require a specific identifier or slug and a matching related record. Verify the actual mapping rather than relying on the visible label.

Archives