A product import may not preserve the old product ID

Separate product identity from its database number

The business can continue selling the same catalog item while the destination store gives its record a different identifier. WooCommerce documents product CSV import and export as a way to move product data, with a specific limit: a newly created product cannot be assigned a chosen post ID. An old ID in your working file is therefore evidence about the source store, not a promise about the destination.

Record the source store alongside its ID. Then identify the destination product from its actual catalog details and record the ID found there. A SKU can help you find the item if your records establish that it identifies the same product. Do not let a shared name or an assumed SKU match settle an ambiguous mapping. If two destination records could be the intended product, keep the mapping open until the catalog owner resolves it.

Find the references that actually use the old ID

Inspect the systems your business already uses. Look for the source product reference in configured integrations, maintained exports, catalog links and custom fields. For each match, record the owning system and the field that holds it. An inventory connection may use a SKU, a custom integration may store a numeric ID, and a public link may use a URL. These are places to investigate, not assumptions about what your store has installed.

The important question is what the consumer expects to receive. A reference that explicitly names the old store and its product belongs in a different mapping from one that is supposed to address the destination. Merely finding the same digits in a file is insufficient: establish that the field refers to this product before proposing a change.

WooCommerce's exporter offers optional custom meta, and the importer does not import unrecognized columns. If a dependency lives in a custom field, confirm whether the export included it and whether the destination received a usable value. A copied old ID still needs interpretation; copying the field does not demonstrate that it now targets the new product.

Close a mapping with evidence from both ends

Keep the old reference, the destination record and the dependent system together in one internal mapping. Preserve the original value before an authorized maintainer changes it. After the change, inspect the dependent system's actual product association or existing operational record to establish which destination item it resolves to. A completed import alone cannot supply that evidence.

Use a clear outcome for each dependency: confirmed against the destination, deliberately retained as a historical source reference, or unresolved. Historical records should remain understandable in the context of the old store; do not overwrite an old reference simply to make its number resemble the new catalog. This worksheet maps identifiers and does not migrate order history.

An unresolved dependency has a concrete next action. An ambiguous destination needs a catalog decision. A missing custom field needs an export/import coverage check. A dependent system still pointing at the old record needs a scoped change by its owner. None requires guessing or forcing a post ID.

Use the unresolved dependency to scope the consultation

For a Prism checkout-review consultation, describe the store move, the affected product-reference mechanism and what still points to the old catalog. Summarize the mapping outcome without uploading internal exports. The consultation can establish the requested scope, responsibilities, fees and terms; migration or integration work needs that explicit scope.

Include the website, research-only product types and the specific question in the inquiry. Follow-up is by email. Sending the form does not purchase a migration, book an appointment or submit a processing application. The provider separately decides eligibility and account terms.

Product identifier migration map

Repeat this sheet for each real product and dependent system. Keep exact internal identifiers in your controlled migration record; use non-sensitive references or match results here. A mapping is confirmed only when the destination product and its consumer agree. Blank evidence leaves the dependency unresolved.

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.

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.