Only fields traced through the actual export, the destination's supported import mapping and the resulting product record have verified coverage. WooCommerce's built-in exporter offers optional custom metadata, but unrecognized columns are not imported. Inventory the real field keys and their purpose, inspect the exported values, and name how each will be handled at the destination. A completed product import or a matching product count does not establish that custom fields survived.
For: A research-only merchant checking whether a WooCommerce catalog move preserves the product fields its staff and storefront actually use.
Start with the product editor, the current public product page and the customization records for the store. For each merchant-specific field, record its visible label, actual stored key, owning extension or customization, and where its value is used. A label on the screen is not enough to identify the data that needs to move.
Mark which fields are needed for product identification, public representations or an operating handoff. Use the real catalog to identify which products and variations carry them. An empty field on one product does not establish that the field is unused throughout the catalog. If the storage location or owner is unknown, mark that gap before declaring the export complete.
Check export inclusion and import recognition separately
WooCommerce's CSV documentation describes exporting products with selected columns, product types and categories, and an option to include custom metadata. Record the selections used for the actual file. Then inspect its header and the values for the products identified in your inventory. Optional metadata cannot be assumed present simply because ordinary product names and prices are present.
At the destination, compare each source column with the supported import mapping. WooCommerce says unrecognized columns are not imported. A column can therefore exist in the CSV without becoming usable destination data. Record an explicit destination field or a separately agreed handling route for every required source field; a supplier-specific heading does not establish a supported mapping.
If an extension owns a field, require evidence for that extension's destination handling before marking coverage verified. The built-in product CSV documentation does not establish support for every extension's storage format or behavior. Keep the unresolved field, its business purpose and the responsible implementer visible rather than silently dropping it from the migration scope.
Verify meaning as well as presence
Compare the actual source value, exported value and resulting destination value for the required field. Check that the correct product or variation owns it, that all needed parts of the value remain intact, and that the intended editor or storefront use still has the data it requires. A value stored somewhere at the destination is weaker evidence than a value associated with the right product and read by the intended feature.
Do not use the old numerical post ID as proof of identity for newly imported products. WooCommerce's importer cannot assign a specified post ID to a new product. Preserve an explicit product association in the migration records before deciding a custom value belongs to the correct destination item. The separate product-ID mapping guide addresses that dependency in more detail.
A custom field containing an image or evidence URL also needs its own interpretation. A URL string arriving in a field does not prove the linked resource arrived. Where the built-in importer is importing images, WooCommerce requires a directly accessible image URL or an existing media-library file. Do not extend that image rule into a promise that arbitrary linked documents are transferred.
Make missing coverage an explicit acceptance decision
Classify every required field as verified at the destination, absent from the export, unmapped at import, or present with unresolved behavior. Record any merchant-approved exclusion with its consequence for the real catalog. Do not accept a silent omission merely because the import completed. If the destination has not yet been imported, the map can establish planned handling, but destination coverage remains unverified.
Use the completed map to scope a Prism checkout-review consultation when catalog data affects the website or checkout question. Describe the website, research-only products and the affected field's purpose without uploading customer records or credentials. Confirm any migration investigation or implementation work, responsibilities, fees and terms before work begins. The inquiry receives email follow-up and does not buy a migration or submit a processing application.
Custom-field migration map
Repeat this sheet for each real custom field. Enter the source key and product association, then trace that field through the file and destination. Mark planned, verified or unresolved explicitly; a blank destination check is not verified coverage.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Custom-field migration map. The last column is for temporary notes.
Mapping entry
Record to inspect
Coverage decision
Your field evidence
Source field
Record to inspectActual stored key, visible label, owning extension or customization, and affected product or variation.
Coverage decisionIf only the label is known, the source schema is still unresolved.
Business purpose
Record to inspectWhere the real storefront or staff workflow reads the field.
Coverage decisionState what would be lost if it were omitted; identify whether the merchant requires it for acceptance.
Export column
Record to inspectActual CSV header and field values, together with selected export options.
Coverage decisionConfirm inclusion of optional custom metadata and the relevant products; do not infer it from product counts.
Destination handling
Record to inspectRecognized importer mapping or documented, agreed handling by the field's owning extension.
Coverage decisionAn unrecognized column needs explicit handling before it can be counted as covered.
Product association
Record to inspectSource-to-destination mapping for the actual product or variation.
Coverage decisionDo not assume a newly imported product retains its original numerical post ID.
Verified coverage
Record to inspectComparison of original value, exported value, resulting destination record and required visible use.
Coverage decisionRecord what was checked and when; distinguish stored data from a working field-dependent feature.
Unresolved field owner
Record to inspectNamed implementer, missing evidence and any merchant-approved exclusion.
Coverage decisionKeep required omissions open until handled; preserve the source value and original export.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
These CSV facts concern WooCommerce's built-in product tools. Other importers and extension-specific formats require their own documented support.
A product CSV does not establish transfer of orders, user accounts or payment credentials. Catalog acceptance does not establish provider approval.
Use product-field evidence only. Do not place customer records, payment data, private tokens or passwords in the worksheet or consultation form.
WooCommerce product CSV exporter — checked 2026-09-21. The built-in product exporter offers selected columns and optional custom metadata. Unrecognized columns are not imported, new products cannot be assigned specified post IDs, and imported images need directly accessible URLs or media-library files. This does not establish coverage for every custom extension.
Prism solutions — checked 2026-09-21. Published support includes storefront review, processing preparation and provider website questions; requested scope, fees and terms are confirmed before work.
Prism contact — checked 2026-09-21. The form asks for the website, products and question and excludes payment details, passwords and customer records. Email follow-up does not make the request an appointment, service purchase or processing application.